From 19f936becebd87c1952585ddb6ca1a93f57a84e2 Mon Sep 17 00:00:00 2001 From: Yuri Date: Sat, 22 Nov 2014 12:15:47 -0800 Subject: [PATCH] Fixed the problem when COLOR=0 caused 'printf' to break due to leading dashes interpreted as command line options. --- testssl.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/testssl.sh b/testssl.sh index 4f1cfcb..6fe0964 100755 --- a/testssl.sh +++ b/testssl.sh @@ -50,7 +50,7 @@ SWCONTACT="dirk aet testssl dot sh" CAPATH="${CAPATH:-/etc/ssl/certs/}" # same as previous. Doing nothing yet. FC has only a CA bundle per default, ==> openssl version -d OSSL_VER="" # openssl version, will be autodetermined NC="" # netcat will be autodetermined -ECHO="/usr/bin/printf" # works under Linux, BSD, MacOS. watch out under Solaris, not tested yet under cygwin +ECHO="/usr/bin/printf --" # works under Linux, BSD, MacOS. watch out under Solaris, not tested yet under cygwin COLOR=${COLOR:-2} # 2: Full color, 1: b/w+positioning, 0: no ESC at all SHOW_LCIPHERS=no # determines whether the client side ciphers are displayed at all (makes no sense normally) VERBERR=${VERBERR:-1} # 0 means to be more verbose (some like the errors to be dispayed so that one can tell better