Git/testssl.sh
1
0
Fork 0
mirror of https://github.com/drwetter/testssl.sh.git synced 2025-04-08 02:34:02 +02:00
Code Issues Packages Projects Releases Wiki Activity

Typos / when needed

Browse Source
This commit is contained in:
Dirk Wetter 2025-03-30 19:59:23 +02:00 committed by GitHub
parent 3a414d60bf
commit 2dfd192f27
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
bin/Readme.md
View File

@ -16,9 +16,9 @@ The important thing upfront: **DO NOT USE THESE BINARIES FOR PRODUCTION PURPOSES
More
====
In general these binaries are not needed anymore as weak crypto is covered by bash sockets if the binary from the vendor can't handle weak crypto. In the future release they will ne retired.
In general these binaries are not needed anymore as weak crypto is covered by bash sockets if the binary from the vendor can't handle weak crypto. In a future release they will be retired.
Testing with openssl however is at the moment faster opposed to using bash sockets. And binaries can handle protocols (/better) once the SSL/TLS connection is established, like retrieving the HTTP header.
Testing with openssl however is at the moment faster as opposed to using bash sockets. And binaries can handle protocols (/better) once the SSL/TLS connection is established, like retrieving the HTTP header. Distributors / vendors however support as of 2024/2025 still protocols like TLS 1.0 and TLS 1.1, most of them even SSLv3, with some tweaks. So using older binaries like the ones in this directory is very often not needed.
General
-------