Git
/
testssl.sh
mirror of https://github.com/drwetter/testssl.sh.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Testing TLS/SSL encryption anywhere on any port. https://testssl.sh/
1,592 Commits 14 Branches 30 Tags 204 MiB
Shell 91.4%
HTML 4.4%
Perl 3.9%
Java 0.2%
Dockerfile 0.1%
Go to file
David Cooper e7c7e7ba19 Update fix to 587 
In the revised code that was created to address #587, nothing is printed after "OCSP URI" if there is neither an OCSP URI nor a CRL URI. Instead, "--" should be printed.

I still believe that there is an inconsistency in the reporting of the output, however. At the moment, the "Certificate Revocation List" and "OCSP URI" lines indicate it is acceptable as long as the certificate contains either a CRL URI or an OCSP URI. However, the "OCSP stapling" line reports a minor finding if an OCSP response was not included in the server's reply. Shouldn't we just assume that if the certificate doesn't include an OCSP URI, then it wouldn't be possible for the server to obtain an OCSP response to staple to its reply? If so, then it seems that no OCSP stapling should only be considered a finding if an OCSP URI is present.
 		2017-02-02 15:52:32 -05:00
bin Update Readme.md 2016-09-27 00:08:01 +02:00
etc - add crypotsense prefined DH groups 2017-01-20 18:14:48 +01:00
t Merge remote-tracking branch 'drwetter/2.9dev' into 2.9dev 2016-11-04 02:54:56 +01:00
utils Generate list of all DHE ciphers 2017-01-18 15:16:13 -05:00
.gitignore update 2016-11-07 21:05:21 +01:00
.travis.yml Be more verbose in your error testing 2016-06-29 00:15:32 +02:00
CHANGELOG.stable-releases.txt Rename old.CHANGELOG.txt to CHANGELOG.stable-releases.txt 2015-09-03 15:15:36 +02:00
CREDITS.md Update CREDITS.md 2016-11-21 09:06:21 +01:00
LICENSE Initial commit 2014-07-01 13:55:26 +02:00
Readme.md Update Readme.md 2016-11-21 08:57:50 +01:00
openssl-rfc.mappping.html typo 2016-02-06 16:18:46 +01:00
testssl.sh Update fix to 587 2017-02-02 15:52:32 -05:00

Readme.md

Intro

Build Status 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, NetBSD 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)

Status

Here in the 2.9dev 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 or https://github.com/drwetter/testssl.sh/wiki/Usage-Documentation.

Compatibility

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.

Update notification here or @ twitter.

Features implemented in 2.9dev

  • Support of supplying timeout value for openssl connect -- useful for batch/mass scanning
  • TLS 1.2 protocol check via socket
  • Further TLS socket improvements (handshake parsing, completeness, robustness)
  • non-flat JSON support
  • in file output (CSV, JSON flat, JSON non-flat) support of a minimum severity level (only above supplied level there will be output)
  • testing 359 default ciphers (testssl.sh -e) with a mixture of sockets and openssl. Same speed as with openssl only but addtional ciphers such as post-quantum ciphers, new CHAHA20/POLY1305, CamelliaGCM etc.
  • finding more TLS extensions via sockets
  • TLS Supported Groups Registry (RFC 7919), key shares extension

Features planned in 2.9dev

https://github.com/drwetter/testssl.sh/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.9dev

Contributions

Contributions, feedback, 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.

There's coding guideline.

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

Documentation

For a start see the wiki. Help is needed here.

Bug reports

Please file bugs in the issue tracker. Do not forget to provide detailed information, see https://github.com/drwetter/testssl.sh/wiki/Bug-reporting. (Nobody can read your thoughts -- yet. And only agencies your screen) ;-)

External/related projects

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

Cool web frontend

mass scanner w parallel scans and elastic searching the results

Ready-to-go docker images are available at:

Brew package