You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: FAQ.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
### FAQs
2
2
3
-
This is a collection of frequently asked questions which should help to answer some of those or gain some insights. It could be helpful reading before filing issues.
3
+
This is a collection of frequently asked questions which should help to answer some of those. It is is recommended reading this before filing issues.
4
4
5
5
#### Coding
6
6
@@ -19,8 +19,7 @@ This is a collection of frequently asked questions which should help to answer s
19
19
20
20
* Will you backport TLS 1.3, QUIC or some other modern crypto to the supplied OpenSSL-bad version?
21
21
* That is not going to happen as it's more resource efficient use the vendor supplied version and compensate deficiencies with either the OpenSSL-bad version or with bash sockets as/where we see it fit.
22
-
* Also likely there won't be another set of compiled binaries --unless the sky falls on our head.
23
-
22
+
* Also likely there won't be another set of compiled binaries --unless the sky falls on our heads.
24
23
25
24
* Where can I find infos about "your" OpenSSL version?
26
25
* Source code, documentation and license see [here](https://github.com/testssl/openssl-1.0.2.bad). You may use it for testing. But don't use it in production on a server or as a client in any other context like testssl.sh!
0 commit comments