From bad6667e9a4c1faa0e0165faa66e7bc9753c4599 Mon Sep 17 00:00:00 2001
From: Dirk Wetter <dirk@testssl.sh>
Date: Fri, 7 Mar 2025 13:34:12 +0100
Subject: [PATCH] Start with an FAQ

From time to time we get similar questions. This is an approach to provide answers beforehand.

You're welcome to contribute!
---
 FAQs/index.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 FAQs/index.md

diff --git a/FAQs/index.md b/FAQs/index.md
new file mode 100644
index 0000000..34cc9f0
--- /dev/null
+++ b/FAQs/index.md
@@ -0,0 +1,19 @@
+### FAQs
+
+This is a collection of frequently asked questions which should help to answer you some questions or gain some insights. It could be helpful reading before filing issues. 
+
+#### Coding
+
+* Why are you using bash, everybody nowadys uses (python|Golang|Java|etc), it's much faster and modern!
+   * The project started in 2007 as serious of OpenSSL commands in a shell script which was used for pen testing. OpenSSL then was the central part (and partly is) to do some basic operations for connections and certificates verification which would have been more tedious to implement in other programming languages. Over time the project became bigger and it in terms of resources it wasn't a viable option to convert it to (python|Golang|Java|etc). Besides, bash is easy to debug as opposed to a compiled binary. Personally, I believe its capabilities are often underestimated.
+
+* But why don't you now amend it with a (python|perl|Golang|Java|etc) function which does \<ABC\> or \<DEF\> much faster?
+   * The philosophy and the beauty of testssl.sh is that it runs *everywhere* with a minimal set of dependencies like typical Unix binaries. No worries about having a different version of libraries/ interpreter not installed.
+
+
+#### Runtime
+
+* I believe I spotted a false positive as testssl.sh complained about a finding \<XYZ\> but my OpenSSL command `openssl s_client -connect <host:port> <MoreParameters> </dev/null` showed no connection. 
+   * First of all modern operating systems have disabled some insecure features. You can temporarily reenable those by using `openssl s_client -connect <host:port>  -cipher 'DEFAULT@SECLEVEL=0'  <MoreParameters> </dev/null `. Or use the (by testssl.sh project) supplied OpenSSL-bad version like `OPENSSL_CONF='' ./bin/openssl.Linux.x86_64 s_client -connect <host:port>  -cipher 'DEFAULT@SECLEVEL=0 <MoreParameters>'  </dev/null`. 
+   * There is other bad crypto though which you can't test this way, e.g. modern OS supply OpenSSL binaries which have [SSLv2 and SSLv3 disabled in the source code or at least when compiling](https://docs.openssl.org/3.3/man7/ossl-guide-tls-introduction/#what-is-tls) which you can't reenable during runtime. OTOH the supplied OpenSSL-bad version  from our project has this and more enabled but doesn't support TLS 1.3 or modern elliptic curves.
+   * To amend any lack of capabilties of any OpenSSL version testssl.sh is picking up we're using bash sockets ([random picked example](https://www.xmodulo.com/tcp-udp-socket-bash-shell.html)).