Testing TLS/SSL encryption anywhere on any port. https://testssl.sh/
Go to file
Dirk Wetter 7741d99cc8 Update Readme.md 2015-05-12 13:42:42 +02:00
openssl-bins Update Readme.md 2015-05-12 10:21:31 +02:00
utils Merge branch 'master' of github.com:drwetter/testssl.sh 2015-02-05 09:54:24 +01:00
CHANGELOG.txt 2014-07-16 19:06:26 +02:00
CREDITS.md - 2015-04-09 21:45:22 +02:00
LICENSE Initial commit 2014-07-01 13:55:26 +02:00
Readme.md Update Readme.md 2015-05-12 13:42:42 +02:00
mapping-rfc.txt - stripping of leading 0 in testssl.sh needed to be reflected by this file 2014-11-18 11:04:57 +01:00
openssl-rfc.mappping.html typo 2015-04-21 08:14:36 +02:00
testssl.sh - Workarounds for IIS6 #99 : some places where openssl 1.0.2 cannot connect (as opposed 2015-05-12 13:37:39 +02:00

Readme.md

Intro

Gitter

testssl.sh is a free command line tool which checks a server's service on any port for the support of TLS/SSL ciphers, protocols as well as some cryptographic flaws. It's designed to provide clear output for your "is this good or bad" decision.

It is working on every Linux distribution out of the box with some limitations of disabled features from the openssl client -- some workarounds are done with bash-socket-based checks. It also works on BSD and other Unices out of the box, supposed they have /bin/bash and standard tools like sed and awk installed. MacOS X and Windows (using MSYS2) work too. OpenSSL version >= 1 is highly recommended.

On github you will find in the master branch the development version of the software -- with new features and maybe some bugs. For the stable version and a more thorough description of the software please see testssl.sh.

New features in the upcoming stable release 2.4 are:

  • "only one cmd line option at a time": completely gone
  • several tuning parameters on the cmd line (only available through environment variables b4): --assuming-http, --ssl-native, --sneaky, --warnings, --color, -- debug, --long
  • certificate information: done,
  • more HTTP header infos (cookies+security headers): done.
  • protocol check via bash sockets, SSLv2+v3: done
  • cipher check via bash sockets: for now only with development option -q
  • debug file handling: done so far
  • BEAST: done, maybe needs long output as option (-->pushed to 2.5/6)
  • FREAK: done
  • Secure Client-Initiated Renegotiation: done
  • cosmetic code cleanups: done
  • bugfixing: WIP

Bottom line: Expect no further big features now. Plan is to stabilize, bug fix and publish a 2.4 release before the next bigger development stage.

Contributions, feedback, also bug reports are welcome. For contributions please note: One patch per feature -- bug fix/improvement. Please file bug reports @ https://github.com/drwetter/testssl.sh/issues .

Update notification here or @ twitter.