Testing TLS/SSL encryption anywhere on any port. https://testssl.sh/
Go to file
David Cooper ca29015e9c Use OpenSSL for determine_optimal_proto()
This PR reverts determine_optimal_proto() to use OpenSSL again rather than tls_sockets().

The primary reason for this is that the primary purpose of determine_optimal_proto() is to set OPTIMAL_PROTO, which is only used with $OPENSSL s_client. So, the best way to determine what works best on the $OPENSSL s_client command line is to use $OPENSSL s_client.

In most cases, determine_optimal_proto_sockets_helper() would set OPTIMAL_PROTO to an acceptable value, but it might not always do so. For example, suppose that a server
* supports different cipher suites with different protocols, 
* supports TLSv1.2, but only with cipher suites not supported by $OPENSSL, but
* supports TLSv1.1 with at least one cipher suite supported by $OPENSSL.

In the above case, determine_optimal_proto_sockets_helper() would set OPTIMAL_PROTO to "-tls1_2", but testing using $OPENSSL would result in OPTIMAL_PROTO being set to "-tls1_1".

Using $OPENSSL for determine_optimal_proto() also allows for edge cases to be detected earlier:
* If the server only supports TLSv1.3, and $OPENSSL does not support TLSv1.3, then the code in this PR will detect that (rather than waiting until run_protocols() is executed).
* The code in this PR can also detect if the server only supports SSLv3 (and possibly also SSLv2), but $OPENSSL does not support SSLv3.
* This code can also detect the (rare) case in which connections using $OPENSSL succeed, but connections using tls_sockets() fail.

[Note also that in the current code, if $all_failed is true, then a message may be printed that $OPENSSL is not IPv6 aware, even if testing was performed using tls_sockets() rather than $OPENSSL.]
2019-10-02 13:08:52 -04:00
.github fix numbering 2019-04-02 09:29:13 +02:00
bin name is openssl.Linux.x86_64.krb now 2019-02-28 19:38:25 +01:00
doc Formatting fixed 2019-05-05 15:07:55 +02:00
etc Allow TLS12_CIPHER to be changed 2019-09-23 15:54:44 -04:00
t swap ldap server as previous one wasn't reachable anymore 2019-09-25 09:36:16 +02:00
utils 0-RTT dockerfile script for nginx 2019-10-02 17:52:34 +02:00
.gitignore update 2016-11-07 21:05:21 +01:00
.travis.yml Fixes for travis 2019-08-12 12:25:54 +02:00
CHANGELOG.md Add SNI/STARTTLS, pwnedkeys 2019-06-12 15:41:07 +02:00
CONTRIBUTING.md Add CONTRIBUTING.md, docker changes in Readme.md 2019-08-08 18:34:14 +02:00
CREDITS.md Test for vulnerability to Bleichenbacher attack 2017-12-12 09:51:48 -05:00
Dockerfile Add idn support 2019-09-19 07:12:59 +00:00
Dockerfile.md Resort and polish 2019-09-13 10:54:18 +02:00
LICENSE Initial commit 2014-07-01 13:55:26 +02:00
openssl-iana.mapping.html RFC --> IANA 2018-11-08 20:38:28 +01:00
Readme.md Fix stale links 2019-08-08 21:10:07 +02:00
testssl.sh Use OpenSSL for determine_optimal_proto() 2019-10-02 13:08:52 -04:00

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.
  • Machine readable output.
  • No installation needed: Linux, OSX/Darwin, FreeBSD, NetBSD, MSYS2/Cygwin, WSL work out of the box. Only OpenBSD needs bash. No need to install or to configure something. No gems, CPAN, pip or the like.
  • A Dockerfile is provided, there's also an offical container @ dockerhub.
  • Flexibility: You can test any SSL/TLS enabled and STARTTLS service, not only web servers at port 443.
  • Toolbox: Several command line options help you to run your test and configure your output.
  • Reliability: features are tested thoroughly.
  • 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.
  • The development is open (github) and participation is welcome.

License

This software is free. You can use it under the terms of GPLv2, see LICENSE. In addition starting from version 3.0rc1 if you're offering a scanner based on testssl.sh as a public and / or paid service in the internet you need to mention to your audience that you're using this program and where to get this program from.

Compatibility

testssl.sh is working on every Linux/BSD distribution out of the box. Latest by 2.9dev most of the limitations of disabled features from the openssl client are gone due to bash-socket-based checks. As a result you can also use e.g. LibreSSL or OpenSSL 1.1.1 . testssl.sh also works on other unixoid system out of the box, supposed they have /bin/bash >= version 3.2 and standard tools like sed and awk installed. An implicit (silent) check for binaries is done when you start testssl.sh . System V needs probably to have GNU grep installed. MacOS X and Windows (using MSYS2, Cygwin or WSL) work too.

Update notification here or @ twitter.

Installation

You can download testssl.sh by cloning this git repository:

git clone --depth 1 https://github.com/drwetter/testssl.sh.git

Or help yourself downloading the ZIP archive https://github.com/drwetter/testssl.sh/archive/3.0.zip. Just cd to the directory created (=INSTALLDIR) and run it off there.

Docker

Testssl.sh has minimal requirements. As stated you don't have to install or build anything. You can just run it from the pulled/cloned directory. Still if you don't want to pull the github repo to your directory of choice you can pull a container from dockerhub and run it:

docker run -ti drwetter/testssl.sh <your_cmd_line>

Or if you have cloned this repo you also can just cd to the INSTALLDIR and run

docker build .

followed by docker exec -ti <ID> <your_cmd_line> where ID is the identifier in the last line from the build command like

 ---> 889fa2f99933
Successfully built 889fa2f99933

Status

We're currently in the late release candidate phase. That means you can and should use it for production and let us know if you encounter any additional bugs. Features implemented in 3.0 are listed in the Changelog.

Support for 2.9.5 has been dropped.

Documentation

  • .. it is there for reading. Please do so :-) -- at least before asking questions. See man page in groff, html and markdown format in ~/doc/.
  • https://testssl.sh/ will help to get you started.
  • Will Hunt provides a longer, good description for the (older) version 2.8, including useful background info.

Contributing

Contributions are welcome! See CONTRIBUTING.md for details.

Bug reports

Bug reports are important. It makes this project more robust.

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

You can also debug yourself, see here.


External/related projects

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

Cool web frontend

Mass scanner w parallel scans and elastic searching the results

Another ready-to-go docker image is at:

Privacy checker using testssl.sh

Brew package

Daemon for batch execution of testssl.sh command files

Daemon for batch processing of testssl.sh JSON result files for sending Slack alerts, reactive copying etc