diff --git a/.github/workflows/codespell.yml b/.github/workflows/codespell.yml index cd46e2f..44dd038 100644 --- a/.github/workflows/codespell.yml +++ b/.github/workflows/codespell.yml @@ -12,5 +12,5 @@ jobs: - uses: actions/checkout@v3 - uses: codespell-project/actions-codespell@master with: - skip: ca_hashes.txt,tls_data.txt,*.pem,OPENSSL-LICENSE.txt,.git + skip: ca_hashes.txt,tls_data.txt,*.pem,OPENSSL-LICENSE.txt,.git,CREDITS.md,openssl.cnf ignore_words_list: borken,gost,ciph,ba,bloc,isnt,chello,fo,alle,nmake,anull diff --git a/t/07_isJSON_valid.t b/t/07_isJSON_valid.t index 26814b8..0296114 100755 --- a/t/07_isJSON_valid.t +++ b/t/07_isJSON_valid.t @@ -44,7 +44,7 @@ $tests++; #3 -# This testss.sh run deliberately does NOT work as travis-ci.org blocks port 25 egress. +# This testssl.sh run deliberately does NOT work as travis-ci.org blocks port 25 egress. # but the output should be fine. The idea is to have a unit test for a failed connection. printf "%s\n", ".. plain JSON for a failed run: '--mx $uri' ..."; $out = `./testssl.sh --ssl-native --openssl-timeout=10 $check2run --jsonfile tmp.json --mx $uri`; diff --git a/testssl.sh b/testssl.sh index 250f7eb..4e5e03f 100755 --- a/testssl.sh +++ b/testssl.sh @@ -9569,7 +9569,7 @@ run_server_defaults() { if $TLS13_ONLY; then generic_nonfatal "Client problem: We need openssl supporting TLS 1.3. We can't continue with \"server defaults\" as we cannot retrieve the certificate. " else - generic_nonfatal "Client problem, No server cerificate could be retrieved. Thus we can't continue with \"server defaults\"." + generic_nonfatal "Client problem, No server certificate could be retrieved. Thus we can't continue with \"server defaults\"." fi fi [[ $DEBUG -ge 1 ]] && [[ -e $HOSTCERT.nosni ]] && $OPENSSL x509 -in $HOSTCERT.nosni -text -noout 2>>$ERRFILE > $HOSTCERT.nosni.txt @@ -15248,7 +15248,7 @@ run_tls_fallback_scsv() { pr_svrty_good "Probably OK. " fileout "$jsonID" "OK" "Probably oK" # see RFC 7507, https://github.com/drwetter/testssl.sh/issues/121 - # other case reported by Nicolas was F5 and at costumer of mine: the same + # other case reported by Nicolas was F5 and at customer of mine: the same pr_svrty_medium "But received non-RFC-compliant \"handshake failure\" instead of \"inappropriate fallback\"" fileout "$jsonID" "MEDIUM" "received non-RFC-compliant \"handshake failure\" instead of \"inappropriate fallback\"" elif grep -qa "ssl handshake failure" "$TMPFILE"; then