Update Readme.md

This commit is contained in:
Dirk Wetter 2015-05-12 13:42:42 +02:00
parent 7614ac6f87
commit 7741d99cc8
1 changed files with 5 additions and 5 deletions

View File

@ -5,7 +5,7 @@
`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. It's designed to provide clear output for your "is this good or bad" decision.
It is working on every Linux 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 BSD and other Unices out of the box, supposed they have `/bin/bash` and standard tools like sed and awk installed. MacOS X and Windows (using MSYS2) work too.
It is working on every Linux 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 BSD and other Unices out of the box, supposed they have `/bin/bash` and standard tools like sed and awk installed. MacOS X and Windows (using MSYS2) work too. OpenSSL version >= 1 is highly recommended.
On github you will find in the master branch the development version of the software -- with new features and maybe some bugs. For the stable version and a more thorough description of the software please see [testssl.sh](https://testssl.sh/ "Go to the site with the stable version and more documentation").
@ -16,13 +16,13 @@ New features in the upcoming stable release 2.4 are:
* certificate information: done,
* more HTTP header infos (cookies+security headers): done.
* protocol check via bash sockets, SSLv2+v3: done
* maybe: cipher check via bash sockets: for now only with development option -q
* cipher check via bash sockets: for now only with development option -q
* debug file handling: done so far
* BEAST: done, maybe needs long output as option
* BEAST: done, maybe needs long output as option (-->pushed to 2.5/6)
* FREAK: done
* Secure Client-Initiated Renegotiation: done
* cosmetic code cleanusp
* bugfixing
* cosmetic code cleanups: done
* bugfixing: WIP
Bottom line: Expect no further big features now. Plan is to stabilize, bug fix and publish a 2.4 release before the next bigger development stage.