Git/testssl.sh
1
0
Fork 0
mirror of https://github.com/drwetter/testssl.sh.git synced 2025-01-03 23:39:45 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update Readme.md

Browse Source
This commit is contained in:
Dirk Wetter 2016-10-21 22:16:19 +02:00 committed by GitHub
parent 5e5edd5c89
commit bfad620bf5
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Readme.md
View File

@ -26,15 +26,17 @@ cryptographic flaws.
going on and you can change it. going on and you can change it.
* Heck, even the development is open (github) * Heck, even the development is open (github)
#### General #### Status
Here in the master branch you find the stable version 2.8rc2 of the software, it _ _Here in the master branch you find the stable version 2.8rc2 of the software, it
superseds 2.6. Version 2.8 is currently being finalized. The 2.9dev branch is the developemnet superseds 2.6. Version 2.8 is currently being finalized_ _. The 2.9dev branch is the developement
-- with new features and maybe some bugs. For the stable version and **a -- with new features and maybe some bugs. For the stable version and **a
more thorough description of the command line options** please see more thorough description of the command line options** please see
[testssl.sh](https://testssl.sh/ "Go to the site with the stable version [testssl.sh](https://testssl.sh/ "Go to the site with the stable version
and more documentation") or https://github.com/drwetter/testssl.sh/wiki/Usage-Documentation. and more documentation") 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 testssl.sh is working on every Linux/BSD distribution out of the box with
some limitations of disabled features from the openssl client -- some some limitations of disabled features from the openssl client -- some
workarounds are done with bash-socket-based checks. It also works on other workarounds are done with bash-socket-based checks. It also works on other