Git/testssl.sh
1
0
Fork 0
mirror of https://github.com/drwetter/testssl.sh.git synced 2024-12-28 12:29:44 +01:00
Code Issues Packages Projects Releases Wiki Activity
Testing TLS/SSL encryption anywhere on any port. https://testssl.sh/
671 Commits 14 Branches 30 Tags 211 MiB
Shell 91.4%
HTML 4.4%
Perl 3.9%
Java 0.2%
Dockerfile 0.1%
a1ef935903
Go to file
Dirk a1ef935903 20 CCM cipher added
2016-01-20 14:17:38 +01:00
bin Update Readme.md 2015-10-05 09:22:02 +02:00
etc - remove duplicates 2016-01-15 15:15:29 +01:00
utils Added client simulations based on @ivanr s list on ssllabs 2016-01-13 10:21:01 +01:00
CHANGELOG.stable-releases.txt Rename old.CHANGELOG.txt to CHANGELOG.stable-releases.txt 2015-09-03 15:15:36 +02:00
CREDITS.md - mentioning where the client data comes from 2016-01-15 17:05:43 +01:00
LICENSE Initial commit 2014-07-01 13:55:26 +02:00
openssl-rfc.mappping.html 20 CCM cipher added 2016-01-20 14:17:38 +01:00
Readme.md Update Readme.md 2015-12-24 23:13:20 +01:00
testssl.sh added --mapping=no-rfc 2016-01-19 21:55:06 +01: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.

####Key features

  • Clear output: you can tell easily whether anything is good or bad
  • Ease of installation: It works for Linux, Darwin, FreeBSD and MSYS2/Cygwin out of the box: no need to install or configure something, no gems, CPAN, pip or the like.
  • Flexibility: You can test any SSL/TLS enabled and STARTTLS service, not only webservers at port 443
  • Toolbox: Several command line options help you to run YOUR test and configure YOUR output
  • Reliability: features are tested thoroughly
  • Verbosity: If a particular check cannot be performed because of a missing capability on your client side, you'll get a warning
  • Privacy: It's only you who sees the result, not a third party
  • Freedom: It's 100% open source. You can look at the code, see what's going on and you can change it.
  • Heck, even the development is open (github)

####General

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

testssl.sh is working on every Linux/BSD 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 other unixoid system out of the box, supposed they have /bin/bash and standard tools like sed and awk installed. MacOS X and Windows (using MSYS2 or cygwin) work too. OpenSSL version >= 1 is a must. OpenSSL version >= 1.0.2 is needed for better LOGJAM checks and to display bit strengths for key exchanges.

####Current Development

Planned features in the release 2.7dev/2.8 are:

https://github.com/drwetter/testssl.sh/milestones/2.7dev%20%282.8%29

Done so far:

  • Trust chain check against certificate stores from java, linux (system), microsoft, mozilla (works for openssl >=1.0.2)
  • IPv6 (status: 80% working, details see https://github.com/drwetter/testssl.sh/issues/11
  • works on servers requiring a x509 certificate for authentication
  • SSL Session ID check
  • avahi/mDNS based name resolution
  • HTTP2/ALPN protocol check
  • Logging to a file / dir
  • Even more compatibilty improvements for FreeBSD, RH-ish and F5 systems

Contributions, feedback, also bug reports are welcome! For contributions please note: One patch per feature -- bug fix/improvement. Please test your changes thouroughly as reliability is important for this project.

Please file bug reports @ https://github.com/drwetter/testssl.sh/issues .

Update notification here or @ twitter.

External contributions

Please address questions not specifically to the code of testssl.sh to the respective projects

Docker images are available at:

brew package