You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+16-16
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@
21
21
* Detect better when no STARTTLS is offered
22
22
* Rating (SSL Labs, not complete)
23
23
* Don't penalize missing trust in rating when CA not in Java store
24
-
* Added support for certificates with EdDSA signatures and pubilc keys
24
+
* Added support for certificates with EdDSA signatures and public keys
25
25
* --add-ca can also now be a directory with \*.pem files
26
26
* Warning of 398 day limit for certificates issued after 2020/9/1
27
27
* Added environment variable for amount of attempts for ssl renegotiation check
@@ -48,7 +48,7 @@
48
48
* Socket timeouts (``--connect-timeout``)
49
49
* IDN/IDN2 servername/URI + emoji support, supposed libidn/idn2 is installed and DNS resolver is recent) support
50
50
* Initial support for certificate compression
51
-
* Better JSON output: renamed IDs and findings shorter/better parsable, also includes certficate
51
+
* Better JSON output: renamed IDs and findings shorter/better parsable, also includes certificate
52
52
* JSON output now valid also for non-responding servers
53
53
* Testing now per default 370 ciphers
54
54
* Further improving the robustness of TLS sockets (sending and parsing)
@@ -82,7 +82,7 @@
82
82
* Support for NNTP and LMTP via STARTTLS, fixes for MySQL and PostgresQL
83
83
* Support for SNI and STARTTLS
84
84
* More robustness for any STARTTLS protocol (fall back to plaintext while in TLS caused problems)
85
-
* Renegotiation checks improved, also no false potive for Node.js anymore
85
+
* Renegotiation checks improved, also no false positive for Node.js anymore
86
86
* Major update of client simulations with self-collected up-to-date data
87
87
* Update of CA certificate stores
88
88
* Lots of bug fixes
@@ -93,7 +93,7 @@
93
93
94
94
* Way better coverage of ciphers as most checks are done via bash sockets where ever possible
95
95
* Further tests via TLS sockets and improvements (handshake parsing, completeness, robustness)
96
-
* 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.
96
+
* Testing 359 default ciphers (``testssl.sh -e/-E``) with a mixture of sockets and openssl. Same speed as with openssl only but additional ciphers such as post-quantum ciphers, new CHAHA20/POLY1305, CamelliaGCM etc.
97
97
* TLS 1.2 protocol check via sockets in production
98
98
* Finding more TLS extensions via sockets
99
99
* TLS Supported Groups Registry (RFC 7919), key shares extension
@@ -137,7 +137,7 @@
137
137
* Even more compatibility improvements for FreeBSD, NetBSD, Gentoo, RH-ish, F5 and Cisco systems
138
138
* Considerable speed improvements for each cipher runs (-e/-E)
139
139
* More robust SSLv2 + TLS socket interface
140
-
*seperate check for curves
140
+
*separate check for curves
141
141
* OpenSSL 1.1.0 compliant
142
142
* check for DROWN
143
143
* Whole number of bugs squashed
@@ -156,7 +156,7 @@
156
156
* (HTTP) proxy support! Also with sockets -- thx @jnewbigin
157
157
* Extended validation certificate detection
158
158
* Run in default mode through all ciphers at the end of a default run
159
-
* will test multiple IP adresses of one supplied server name in one shot, --ip= restricts it accordingly
159
+
* will test multiple IP addresses of one supplied server name in one shot, --ip= restricts it accordingly
160
160
* new mass testing file option --file option where testssl.sh commands are being read from, see https://twitter.com/drwetter/status/627619848344989696
161
161
* TLS time and HTTP time stamps
162
162
* TLS time displayed also for STARTTLS protocols
@@ -212,7 +212,7 @@ Full changelog @ https://github.com/drwetter/testssl.sh/commits/2.2/testssl.sh
212
212
* tests ciphers per protocol
213
213
* HSTS
214
214
* web and application server banner
215
-
* server prefereences
215
+
* server preferences
216
216
* TLS server extensions
217
217
* server key size
218
218
* cipher suite mapping from openssl to RFC
@@ -225,10 +225,10 @@ Full changelog @ https://github.com/drwetter/testssl.sh/commits/2.2/testssl.sh
225
225
- IPv6 display fix
226
226
227
227
1.111
228
-
- NEW: tested unter FreeBSD (works with exception of xxd in CCS)
228
+
- NEW: tested under FreeBSD (works with exception of xxd in CCS)
229
229
- getent now works under Linux and FreeBSD
230
230
- sed -i in hsts sacrificed for compatibility
231
-
-reomved query for IP for finishing banner, is now called once in parse_hn_port
231
+
-removed query for IP for finishing banner, is now called once in parse_hn_port
232
232
- GOST warning after banner
233
233
- empty build date is not displayed anymore
234
234
- long build date strings minimized
@@ -318,7 +318,7 @@ Full changelog @ https://github.com/drwetter/testssl.sh/commits/2.2/testssl.sh
318
318
1.91
319
319
- replaced most lcyan to brown (=not really bad but somehow)
320
320
- empty server string better displayed
321
-
-prefered CBC TLS 1.2 cipher is now brown (lucky13)
321
+
-preferred CBC TLS 1.2 cipher is now brown (lucky13)
322
322
323
323
1.90
324
324
- fix for netweaver banner (server is lowercase)
@@ -327,7 +327,7 @@ Full changelog @ https://github.com/drwetter/testssl.sh/commits/2.2/testssl.sh
327
327
328
328
1.89
329
329
- reordered! : protocols + cipher come first
330
-
- colorized prefered server preference (e.g. CBC+RC4 is light red now, TLSv1.2 green)
330
+
- colorized preferred server preference (e.g. CBC+RC4 is light red now, TLSv1.2 green)
331
331
- SSLv3 is now light cyan
332
332
- NEW: -P|--preference now in help menu
333
333
- light cyan is more appropriate than red for HSTS
@@ -362,10 +362,10 @@ Full changelog @ https://github.com/drwetter/testssl.sh/commits/2.2/testssl.sh
362
362
- headline of -V / PFS+RC4 ciphers unified
363
363
364
364
1.82
365
-
- NEW: output for -V now better (bits seperate, spacing improved)
365
+
- NEW: output for -V now better (bits separate, spacing improved)
366
366
367
367
1.81
368
-
- output for RC4+PFS now better (with headline, bits seperate, spacing improved)
368
+
- output for RC4+PFS now better (with headline, bits separate, spacing improved)
369
369
- both also sorted by encr. strength .. umm ..err bits!
370
370
371
371
1.80
@@ -390,7 +390,7 @@ Full changelog @ https://github.com/drwetter/testssl.sh/commits/2.2/testssl.sh
390
390
- removed legacy code (PROD_REL var)
391
391
392
392
1.76
393
-
- bash was gone!! desaster for Ubuntu, fixed
393
+
- bash was gone!! disaster for Ubuntu, fixed
394
394
- starttls+rc4 check: bottom line was wrong
395
395
- starttls had too much output (certificate) at first a/v check
396
396
@@ -480,13 +480,13 @@ Full changelog @ https://github.com/drwetter/testssl.sh/commits/2.2/testssl.sh
480
480
1.19
481
481
* bugfix
482
482
1.18
483
-
* Rearragement of arguments: URL comes now always last!
483
+
* Rearrangement of arguments: URL comes now always last!
484
484
* small code cleanups for readability
485
485
* individual cipher test is now with bold headline, not blue
486
486
* NOPARANOID flag tells whether medium grade ciphers are ok. NOW they are (=<1.17 was paranoid)
Copy file name to clipboardExpand all lines: doc/testssl.1
+2-2
Original file line number
Diff line number
Diff line change
@@ -125,7 +125,7 @@ Please note that \fBfname\fR has to be in Unix format\. DOS carriage returns won
125
125
\fB\-\-mode<serial|parallel>\fR\. Mass testing to be done serial (default) or parallel (\fB\-\-parallel\fR is shortcut for the latter, \fB\-\-serial\fR is the opposite option)\. Per default mass testing is being run in serial mode, i\.e\. one line after the other is processed and invoked\. The variable \fBMASS_TESTING_MODE\fR can be defined to be either equal \fBserial\fR or \fBparallel\fR\.
126
126
.
127
127
.P
128
-
\fB\-\-warnings<batch|off>\fR\. The warnings parameter determines how testssl\.sh will deal with situations where user input normally will be necessary\. There are two options\.\fBbatch\fR doesn\'t wait for a confirming keypress when a client\- or server\-side probem is encountered\. As of 3\.0 it just then terminates the particular scan\. This is automatically chosen for mass testing (\fB\-\-file\fR)\.\fBoff\fR just skips the warning, the confirmation but continues the scan, independent whether it makes sense or not\. Please note that there are conflicts where testssl\.sh will still ask for confirmation which are the ones which otherwise would have a drastic impact on the results\. Almost any other decision will be made in the future as a best guess by testssl\.sh\. The same can be achieved by setting the environment variable \fBWARNINGS\fR\.
128
+
\fB\-\-warnings<batch|off>\fR\. The warnings parameter determines how testssl\.sh will deal with situations where user input normally will be necessary\. There are two options\.\fBbatch\fR doesn\'t wait for a confirming keypress when a client\- or server\-side problem is encountered\. As of 3\.0 it just then terminates the particular scan\. This is automatically chosen for mass testing (\fB\-\-file\fR)\.\fBoff\fR just skips the warning, the confirmation but continues the scan, independent whether it makes sense or not\. Please note that there are conflicts where testssl\.sh will still ask for confirmation which are the ones which otherwise would have a drastic impact on the results\. Almost any other decision will be made in the future as a best guess by testssl\.sh\. The same can be achieved by setting the environment variable \fBWARNINGS\fR\.
129
129
.
130
130
.P
131
131
\fB\-\-connect\-timeout<seconds>\fR This is useful for socket TCP connections to a node\. If the node does not complete a TCP handshake (e\.g\. because it is down or behind a firewall or there\'s an IDS or a tarpit) testssl\.sh may usually hang for around 2 minutes or even much more\. This parameter instructs testssl\.sh to wait at most \fBseconds\fR for the handshake to complete before giving up\. This option only works if your OS has a timeout binary installed\. CONNECT_TIMEOUT is the corresponding environment variable\.
\fB\-g,\-\-grease\fR checks several server implementation bugs like tolerance to size limitations and GREASE, see RFC 8701\. This check doesn\'t run per default\.
343
343
.
344
344
.SS "VULNERABILITIES"
345
-
\fB\-U,\-\-vulnerable,\-\-vulnerabilities\fR Just tests all (of the following) vulnerabilities\. The environment variable \fBVULN_THRESHLD\fR determines after which value a separate headline for each vulnerability is being displayed\. Default is \fB1\fR which means if you check for two vulnerabilities, only the general headline for vulnerabilities section is displayed \-\- in addition to the vulnerability and the result\. Otherwise each vulnerability or vulnerability section gets its own headline in addition to the output of the name of the vulnerabilty and test result\. A vulnerability section is comprised of more than one check, e\.g\. the renegotiation vulnerability check has two checks, so has Logjam\.
345
+
\fB\-U,\-\-vulnerable,\-\-vulnerabilities\fR Just tests all (of the following) vulnerabilities\. The environment variable \fBVULN_THRESHLD\fR determines after which value a separate headline for each vulnerability is being displayed\. Default is \fB1\fR which means if you check for two vulnerabilities, only the general headline for vulnerabilities section is displayed \-\- in addition to the vulnerability and the result\. Otherwise each vulnerability or vulnerability section gets its own headline in addition to the output of the name of the vulnerability and test result\. A vulnerability section is comprised of more than one check, e\.g\. the renegotiation vulnerability check has two checks, so has Logjam\.
346
346
.
347
347
.P
348
348
\fB\-H,\-\-heartbleed\fR Checks for Heartbleed, a memory leakage in openssl\. Unless the server side doesn\'t support the heartbeat extension it is likely that this check runs into a timeout\. The seconds to wait for a reply can be adjusted with \fBHEARTBLEED_MAX_WAITSOCK\fR\. 8 is the default\.
0 commit comments