40155ed222
Other than before teh Java store was extracted directly from a keystore from a Java JRE from https://jdk.java.net/. The Debian keystore used previously used the certificates from the Debian machine itself (installation script in ``/etc/ca-certificates/update.d/``. Check with ``keytool -list -rfc -keystore /etc/ssl/certs/java/cacerts | grep -i 'alias'`` As a consequence this store contains less certificates: etc/Java.pem:90 etc/Linux.pem:128 and needs some testing whether it really should be still included. |
||
|---|---|---|
| .. | ||
| Apple.pem | ||
| ca_hashes.txt | ||
| cipher-mapping.txt | ||
| client-simulation.txt | ||
| client-simulation.wiresharked.txt | ||
| common-primes.txt | ||
| curves.txt | ||
| Java.pem | ||
| Linux.pem | ||
| Microsoft.pem | ||
| Mozilla.pem | ||
| README.md | ||
| tls_data.txt | ||
Certificate stores
The certificate trust stores were retrieved from
- Linux: Copied from an up-to-date Debian Linux machine
- Mozilla: https://curl.haxx.se/docs/caextract.html
- Java: extracted (
keytool -list -rfc -keystore <file> | grep -E -v '^$|^\*\*\*\*\*|^Entry |^Creation |^Alias ') from a JRE 8 from https://jdk.java.net/ (previously JRE keystore extracted from $JAVA_HOME/jre/lib/security/cacerts using Linux) - Microsoft: Following command pulls all certificates from Windows Update services:
CertUtil -syncWithWU -f -f .(see also http://aka.ms/RootCertDownload, https://technet.microsoft.com/en-us/library/dn265983(v=ws.11).aspx#BKMK_CertUtilOptions). - Apple:
- System: from Apple OS X keychain app. Open Keychain Access utility, i.e. In the Finder window, under Favorites --> "Applications" --> "Utilities" (OR perform a Spotlight Search for Keychain Access) --> "Keychain Access" (2 click). In that window --> "Keychains" --> "System" --> "Category" --> "All Items" Select all CA certificates except for Developer ID Certification Authority, "File" --> "Export Items"
- Internet: Pick the latest subdir from https://opensource.apple.com/source/security_certificates/. They are in DER format despite their file extension.
Google Chromium uses basically the trust stores above, see https://www.chromium.org/Home/chromium-security/root-ca-policy.
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>.
Further files
-
tls_data.txtcontains lists of cipher suites and private keys for sockets-based tests -
cipher-mapping.txtcontains information about all of the cipher suites defined for SSL/TLS -
ca_hashes.txtis used for HPKP test in order to have a fast comparison with known CAs. Use~/utils/create_ca_hashes.shfor an update -
common-primes.txtis used for LOGJAM and the PFS section -
client-simulation.txt/client-simulation.wiresharked.txtare as the names indicate data for the client simulation. The first one is derived from~/utils/update_client_sim_data.pl, and manually edited to sort and label those we don't want. The second file provides more client data retrieved from wireshark captures and some instructions how to do that yourself.