Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(386)

Side by Side Diff: net/data/ssl/certificates/README

Issue 14492003: Work around GTE CyberTrust/Baltimore CyberTrust cross-signing issues (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Review feedback Created 7 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 This directory contains various certificates for use with SSL-related 1 This directory contains various certificates for use with SSL-related
2 unit tests. 2 unit tests.
3 3
4 - google.binary.p7b 4 - google.binary.p7b
5 - google.chain.pem 5 - google.chain.pem
6 - google.pem_cert.p7b 6 - google.pem_cert.p7b
7 - google.pem_pkcs7.p7b 7 - google.pem_pkcs7.p7b
8 - google.pkcs7.p7b 8 - google.pkcs7.p7b
9 - google.single.der 9 - google.single.der
10 - google.single.pem 10 - google.single.pem
(...skipping 153 matching lines...) Expand 10 before | Expand all | Expand 10 after
164 164
165 - eku-test-root.pem 165 - eku-test-root.pem
166 - non-crit-codeSigning-chain.pem 166 - non-crit-codeSigning-chain.pem
167 - crit-codeSigning-chain.pem 167 - crit-codeSigning-chain.pem
168 Two code-signing certificates (eKU: codeSigning; eKU: critical, 168 Two code-signing certificates (eKU: codeSigning; eKU: critical,
169 codeSigning) which we use to test that clients are making sure that web 169 codeSigning) which we use to test that clients are making sure that web
170 server certs are checked for correct eKU fields (when an eKU field is 170 server certs are checked for correct eKU fields (when an eKU field is
171 present). Since codeSigning is not valid for web server auth, the checks 171 present). Since codeSigning is not valid for web server auth, the checks
172 should fail. 172 should fail.
173 173
174 - cybertrust_gte_root.pem
175 - cybertrust_baltimore_root.pem
176 - cybertrust_omniroot_chain.pem
177 - cybertrust_baltimore_cross_certified_1.pem
178 - cybertrust_baltimore_cross_certified_2.pem
179 These certificates are reflect a portion of the CyberTrust (Verizon
180 Business) CA hierarchy. _gte_root.pem is a legacy 1024-bit root that is
181 still widely supported, while _baltimore_root.pem reflects the newer
182 2048-bit root. For clients that only support the GTE root, two versions
183 of the Baltimore root were cross-signed by GTE, namely
184 _cross_certified_[1,2].pem. _omniroot_chain.pem contains a certificate
185 chain that was issued under the Baltimore root. Combined, these
186 certificates can be used to test real-world cross-signing; in practice,
187 they are used to test certain workarounds for OS X's chain building code.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698