Merge pull request #1309 from drwetter/unittest_json
remove -p from json unit test
|2 days ago|
|.github||4 months ago|
|bin||5 months ago|
|doc||3 months ago|
|etc||3 months ago|
|t||1 week ago|
|utils||1 month ago|
|.gitignore||2 years ago|
|.travis.yml||1 week ago|
|CHANGELOG.md||2 months ago|
|CONTRIBUTING.md||1 week ago|
|CREDITS.md||1 year ago|
|Dockerfile||4 months ago|
|Dockerfile.md||3 months ago|
|LICENSE||5 years ago|
|Readme.md||1 week ago|
|openssl-iana.mapping.html||9 months ago|
|testssl.sh||2 days ago|
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
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.
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.
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.
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 .
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
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.
Contributions are welcome! See CONTRIBUTING.md for details.
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.
Please address questions not specifically to the code of testssl.sh to the respective projects below.