Updated Usage Documentation (markdown)

Usage-Documentation.md

@@ -63,14 +63,15 @@ tuning options (can also be preset via environment variables):
      --openssl <PATH>              use this openssl binary (default: look in $PATH, $RUN_DIR of testssl.sh
      --proxy <host>:<port>         connect via the specified HTTP proxy
      -6                            use also IPv6 checks, works only with supporting OpenSSL version and IPv6 connectivity
-     --sneaky                      leave less traces in target logs: user agent, referer
+
+utput options (can also be preset via environment variables):
+     --warnings <batch|off|false>  "batch" doesn't wait for keypress, "off" or "false" skips connection warning
      --quiet                       don't output the banner. By doing this you acknowledge usage terms normally appearing in the banner
-     --log, --logging              logs stdout to <NODE-YYYYMMDD-HHMM.log> in current working directory
-     --logfile <file>              logs stdout to <file/NODE-YYYYMMDD-HHMM.log> if file is a dir or to specified file
      --wide                        wide output for tests like RC4, BEAST. PFS also with hexcode, kx, strength, RFC name
      --show-each                   for wide outputs: display all ciphers tested -- not only succeeded ones
-     --warnings <batch|off|false>  "batch" doesn't wait for keypress, "off" or "false" skips connection warning
+     --mapping <no-rfc>            don't display the RFC Cipher Suite Name
      --color <0|1|2>               0: no escape or other codes,  1: b/w escape codes,  2: color (default)
+     --colorblind                  swap green and blue in the output
       --debug <0-6>                0: none
                                    1: screen output normal but debug output in temp files.
                                    2: list more what's going on, lists some errors of connections
@@ -79,6 +80,18 @@ tuning options (can also be preset via environment variables):
                                    5: display bytes received via sockets
                                    6: whole 9 yards
 
+file output options (can also be preset via environment variables):
+     --log, --logging              logs stdout to <NODE-YYYYMMDD-HHMM.log> in current working directory
+     --logfile <logfile>           logs stdout to <file/NODE-YYYYMMDD-HHMM.log> if file is a dir or to specified log file
+     --json                        additional output of findings to JSON file <NODE-YYYYMMDD-HHMM.json> in cwd
+     --jsonfile <jsonfile>         additional output to JSON and output JSON to the specified file
+     --csv                         additional output of findings to CSV file  <NODE-YYYYMMDD-HHMM.csv> in cwd
+     --csvfile <csvfile>           set output to CSV and output CSV to the specified file
+     --append                      if <csvfile> or <jsonfile> exists rather append then overwrite
+
+All options requiring a value can also be called with '=' e.g. testssl.sh -t=smtp --wide --openssl=/usr/bin/openssl <URI>.
+
+
 All options requiring a value can also be called with `=` (e.g. `testssl.sh -t=smtp --wide --openssl=/usr/bin/openssl <URI>`.
 
 <URI> is always the last parameter. 
@@ -114,7 +127,7 @@ Developed by Dirk Wetter and others, see https://github.com/drwetter/testssl.sh/
 ### COPYRIGHT
 
 Copyright © 2016 Dirk Wetter. License GPLv2: Free Software Foundation, Inc.  
-       This is free software: you are free to change and redistribute it.  Usage WITHOUT ANY WARRANTY. USE at your OWN RISK.
+       This is free software: you are free to change and redistribute it under the terms of the license. Usage WITHOUT ANY WARRANTY. USE at your OWN RISK!
 
 
 ### BUGS
@@ -123,5 +136,5 @@ Known ones see https://testssl.sh/bugs
 
 ### SEE ALSO
 
-ciphers(1), openssl(1)
+ciphers(1), openssl(1), [Will Hunt's description](https://www.4armed.com/blog/doing-your-own-ssl-tls-testing/)