@drwetter drwetter released this Oct 9, 2018 · 7 commits to 2.9dev since this release

Assets 2

This is a release of the second release candidate of testssl.sh 3.0 to reflect he recent changes. All distributors and others who use it also for production-like environment are encouraged to switch to this branch as 2.9.5 won't be supported anymore once 3.0 has been released.

Changes, TL;DR:

  • Partly addressing TCP fragmentation
  • Name check for XMPP servers
  • Support for STARTTLS LMTP
  • TLS 1.3 fixes
  • OpenSSL 1.1.1 fixes

Changes, logs: 3.0rc1...2.9dev

@drwetter drwetter released this Sep 7, 2018 · 2 commits to 2.9.5 since this release

Assets 2

This update contains a few bugfixes only. (Changelog: v2.9.5-5...2.9.5) . It is likely the last release of the 2.9.5 branch. This replaces 2.9.5-6 which was accidentally pointing to the wrong branch.

In general it is highly recommended to switch to 3.0rcX now (see tag in the 2.9dev branch). Besides another leap forward in features (bigger ones: TLS 1.3 and ROBOT check) 3.0rcX is also working with OpenSSL 1.1.1. There are a few known bugs in the 3.0 branch which need to be resolved, they also appear in 2.9.5. Not sure whether the fixes will be backported.

@drwetter drwetter released this Sep 16, 2018 · 57 commits to 2.9dev since this release

Assets 2

This is a release of the first release candidate of testssl.sh 3.0.

It comes with numerous new features like ROBOT check, proper TLS 1.3 detection in every check and last but not least it provides good compatibility to the freshly released OpenSSL 1.1.1 version.

All distributors and others who use it also for production-like environment are encouraged to switch to this branch as 2.9.5 won't be supported anymore once 3.0 has been released.

Sep 5, 2018
Avoid conflicts of OpenSSL 1.1.1 config file
This addresses a bug where openssl s_client connects hiccuped
because of newer config files which our openssl 1.0.2 couldn't
swallow.

It appeared first on Debian.

FIX #1117

FIX #1098

@drwetter drwetter released this Apr 14, 2018 · 10 commits to 2.9.5 since this release

Assets 2

This update contains a bugfix (and a clarification in help/documentation) only. It does not contain any new features.

The bug fix is for Mac OS X only. The was an error where MacOS X' date hiccuped when a timezone conversion was requested but not supplied.

For a description of testssl.sh in general please see 2.9.5-1.

Please note this release still carries -4 as a minor version. Due to an "user error" v2.9.5-4 (deleted) was pointing to 2.9dev instead of 2.9.5.

@drwetter drwetter released this Mar 24, 2018 · 13 commits to 2.9.5 since this release

Assets 2

This update contains several bugfixes as opposed to 2.9.5-2. It does not contain any new features.
More details about all fixes please see https://github.com/drwetter/testssl.sh/commits/2.9.5/testssl.sh (March 24, 2018 to February 19, 2018).

For a description of testssl.sh in general please see 2.9.5-1.

@drwetter drwetter released this Feb 23, 2018 · 20 commits to 2.9.5 since this release

Assets 2

This update contains several bugfixes as opposed to 2.9.5-1. It does not contain new features.

More details about all fixes please see https://github.com/drwetter/testssl.sh/commits/2.9.5/testssl.sh (Feb 19, 2018 to Sep 20, 2017). For a description of testssl.sh in general please see 2.9.5-1.

@drwetter drwetter released this Sep 20, 2017 · 33 commits to 2.9.5 since this release

Assets 2

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)

Compatibility

testssl.sh is working on every Linux/BSD distribution out of the box. In 2.9.5 most of the limitations of disabled features from the openssl client are gone due to bash-socket-based checks. testssl.sh also works on other unixoid system out of the box, supposed they have /bin/bash and standard tools like sed and awk installed. System V needs to have GNU versions of grep installed. MacOS X and Windows (using MSYS2 or cygwin) work too. OpenSSL version >= 1.0.2 is recommended, you will get further with earlier openssl versions in
this interim release though as most of the checks in 2.9 are done via sockets.

Status

2.9.5 is an interim release snapshot from the current 2.9dev version. It has reached a point which is considered to be mature enough for day-to-day usage before taking the next step in the development of this project.

2.9.5 has less bugs and has evolved considerably since 2.8.

Features implemented in 2.9.5

  • TLS 1.2 protocol check via socket in production
  • Way better coverage of ciphers as most checks are done via sockets, using bash sockets where ever possible
  • Further tests via TLS sockets and improvements (handshake parsing, completeness, robustness)
  • Testing 359 default ciphers (testssl.sh -e/-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
  • Non-flat JSON output support
  • File output (CSV, JSON flat, JSON non-flat) supports a minimum severity level (only above supplied level there will be output)
  • Native HTML support instead going through 'aha'
  • LUCKY13 and SWEET32 checks
  • Ticketbleed check
  • LOGJAM: now checking also for known DH parameters
  • Support of supplying timeout value for openssl connect -- useful for batch/mass scanning
  • Check for CAA RR
  • Check for OCSP must staple
  • Check for Certificate Transparency
  • Check for session resumption (Ticket, ID)
  • Better formatting of output (indentation)
  • Choice showing the RFC naming scheme only
  • Parallel mass testing
  • File input for mass testing can be also in nmap grep(p)able (-oG) format
  • Postgres und MySQL STARTTLS support
  • Man page
Sep 19, 2017
changed for 2.9.5

@drwetter drwetter released this May 10, 2017

Assets 2

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

This is the stable version 2.8 of the software, it supersedes 2.6. 2.9dev is the new
development branch For 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.

Features in 2.8 stable

  • Trust chain check against certificate stores from Apple (OS), Linux (OS),
    Microsoft (OS), Mozilla (Firefox Browser), works for openssl >=1.0.1
  • IPv6 (status: 80% working, details see
    #11
  • works now on servers requiring a x509 certificate for authentication
  • extensive CN+SAN <--> hostname check
  • SSL Session ID check
  • Avahi/mDNS based name resolution
  • HTTP2/ALPN protocol check
  • Logging to a file / dir
  • Logging to (flat) JSON + CSV
  • HPKP checks now also for Root, intermediate SPKIs
  • Check for multiple server certificates
  • Browser cipher simulation: what client will connect with which cipher + protocol
  • GOST cipher+certificate improvements
  • Assistance for color-blind users
  • Even more compatibility improvements for FreeBSD, NetBSD, Gentoo, RH-ish, F5 and Cisco systems
  • Considerable speed improvements for each cipher runs (-e/-E)
  • More robust SSLv2 + TLS socket interface
  • separate check for curves
  • OpenSSL 1.1.0 compliant
  • check for DROWN
  • Whole number of bugs squashed

Contributions

Contributions, feedback, bug reports are welcome! For contributions please
note: One patch per feature -- bug fix/improvement. Please test your
changes thoroughly 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