Skip to content

Commit 445d20c

Browse files
committed
Update client simulation for 3.0
see #2169, #2168 Added: * Safari for macOS * Java 17 LTS * OpenSSL 3.0.3 * Android 11 and 12 * Go client (1.17) * Firefox 100, Chrome and Edge 101 using Win10 * Thunderbird 91.9 * AppleMail * LibreSSL from MacOS * disabled Java 12 and Safari on OS X 10.12 * disabled Android < 6.0 * documention update how to add a client simulation * add curves-mapping.txt file
1 parent 2ca5311 commit 445d20c

File tree

5 files changed

+957
-384
lines changed

5 files changed

+957
-384
lines changed

etc/README.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,12 @@ The certificate trust stores were retrieved from
1414
--> "Keychain Access" (2 click). In that window --> "Keychains" --> "System"
1515
--> "Category" --> "All Items"
1616
Select all CA certificates except for Developer ID Certification Authority, "File" --> "Export Items"
17-
2. __Internet:__ Pick the latest subdir (=highest number) from https://opensource.apple.com/source/security_certificates/. They are in DER format despite their file extension. Download them with ``wget --level=1 --cut-dirs=5 --mirror --convert-links --adjust-extension --page-requisites --no-parent https://opensource.apple.com/source/security_certificates/security_certificates-*/certificates/roots/``
17+
2. __Internet:__ Pick the latest subdir (=highest number) from https://opensource.apple.com/source/security_certificates/. They are in DER format despite their file extension. Download them with ``wget --level=1 --cut-dirs=5 --mirror --convert-links --adjust-extension --page-requisites --no-parent https://opensource.apple.com/source/security_certificates/security_certificates-*/certificates/roots/``
1818

1919

2020
Google Chromium uses basically the trust stores above, see https://www.chromium.org/Home/chromium-security/root-ca-policy.
2121

22-
If you want to check trust against e.g. a company internal CA you need to use ``./testssl.sh --add-ca companyCA1.pem,companyCA2.pem <further_cmds>`` or ``ADDITIONAL_CA_FILES=companyCA1.pem,companyCA2.pem ./testssl.sh <further_cmds>``.
22+
If you want to check trust against e.g. a company internal CA you need to use ``./testssl.sh --add-ca companyCA1.pem,companyCA2.pem <further_cmds>`` or ``ADDTL_CA_FILES=companyCA1.pem,companyCA2.pem ./testssl.sh <further_cmds>``.
2323

2424

2525
#### Further files
@@ -28,6 +28,8 @@ If you want to check trust against e.g. a company internal CA you need to use ``
2828

2929
* ``cipher-mapping.txt`` contains information about all of the cipher suites defined for SSL/TLS
3030

31+
* ``curves-mapping.txt`` contains information about all of the elliptic curves defined by IANA
32+
3133
* ``ca_hashes.txt`` is used for HPKP test in order to have a fast comparison with known CAs. Use
3234
``~/utils/create_ca_hashes.sh`` for an update
3335

0 commit comments

Comments
 (0)