Trim excess whitespace

CHANGELOG.md

@@ -32,7 +32,6 @@
 * Added --reqheader to support custom headers in HTTP requests
 * Test for support for RFC 8879 certificate compression
 
-
 ### Features implemented / improvements in 3.0
 
 * Full support of TLS 1.3, shows also drafts supported
@@ -115,7 +114,6 @@
 * Postgres und MySQL STARTTLS support
 * Man page
 
-
 ### New in 2.8
 
 * Trust chain check against certificate stores from Apple (OS), Linux (OS),
@@ -169,7 +167,6 @@
 
 Full log @ https://github.com/drwetter/testssl.sh/commits/2.6/testssl.sh
 
-
 ### New in 2.4
   * "only one cmd line option at a time" is completely gone
   * several tuning parameters on the cmd line (only available through environment variables b4): --assuming-http, --ssl-native, --sneaky, --warnings, --color, -- debug, --long
@@ -324,7 +321,6 @@ Full changelog @  https://github.com/drwetter/testssl.sh/commits/2.2/testssl.sh
 - fix for netweaver banner (server is lowercase)
 - no server banner is no disadvantage (color code)
 
-
 1.89
 - reordered! : protocols + cipher come first
 - colorized preferred server preference (e.g. CBC+RC4 is light red now, TLSv1.2 green)
@@ -471,7 +467,6 @@ Full changelog @  https://github.com/drwetter/testssl.sh/commits/2.2/testssl.sh
   default now and there's a comment
 * openssl version + path to it in the banner
 
-
 1.20
 * bugfix (ssl in ssl handshake failure is sometimes too much)
 * date in output

Coding_Convention.md

@@ -70,4 +70,3 @@ Bash is actually quite powerful -- not only with respect to sockets. It's not as
 * Unit tests are done automatically done with Perl using Travis. The trigger is `~/.travis.yml`. The general documentation for [Test::More](https://perldoc.perl.org/Test/More.html) is a good start. You are encouraged to write own checks. You can use e.g. `t/20_baseline_ipv4_http.t` as an example.
 * If it's an OpenSSL feature you want to use and it could be not available for older OpenSSL versions testssl.sh needs to find out whether OpenSSL has that feature. Best do this with OpenSSL itself and not by checking the version as some vendors do backports. See the examples for `HAS_SSL2` or proxy option check of OpenSSL in `check_proxy()`.
 * If a feature of OpenSSL is not available you need to tell this the user by using `pr_warning*()`. Or accordingly with `fatal()` if a continuation of the program doesn't make sense anymore.
-

bin/Readme.md

@@ -130,5 +130,3 @@ Enjoy, Dirk
 [1] https://en.wikipedia.org/wiki/GOST_%29block_cipher%29
 
 [2] http://fossies.org/linux/openssl/engines/ccgost/README.gost
-
-

etc/client-simulation.wiresharked.md

@@ -22,7 +22,3 @@ The whole process is done manually.
 * "ciphersutes" are TLS 1.3 ciphersuites. You can identify them as they currently are like 0x130?. Retrieve them from above see ``~/utils/hexstream2cipher.sh``
 * Figure out the services by applying a good piece of human logic
 * Before submitting a PR: test it yourself! You can also watch it again via wireshark
-
-
-
-

t/11_baseline_ipv6_http.t.DISABLED

@@ -59,4 +59,3 @@ sub json($) {
 	unlink $file;
 	return from_json($file);
 }
-