| OLD | NEW | 
|    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 | 
|   11 - thawte.single.pem : Certificates for testing parsing of different formats. |   11 - thawte.single.pem : Certificates for testing parsing of different formats. | 
|   12  |   12  | 
|   13 - googlenew.chain.pem : The refreshed Google certificate |   13 - googlenew.chain.pem : The refreshed Google certificate | 
|   14      (valid until Sept 30 2013). |   14      (valid until Sept 30 2013). | 
|   15  |   15  | 
|   16 - mit.davidben.der : An expired MIT client certificate. |   16 - mit.davidben.der : An expired MIT client certificate. | 
|   17  |   17  | 
|   18 - foaf.me.chromium-test-cert.der : A client certificate for a FOAF.ME identity |   18 - foaf.me.chromium-test-cert.der : A client certificate for a FOAF.ME identity | 
|   19      created for testing. |   19      created for testing. | 
|   20  |   20  | 
|   21 - www_us_army_mil_cert.der |   21 - www_us_army_mil_cert.der | 
|   22 - dod_ca_17_cert.der |   22 - dod_ca_17_cert.der | 
|   23 - dod_root_ca_2_cert.der : A certificate chain for regression tests of |   23 - dod_root_ca_2_cert.der : A certificate chain for regression tests of | 
|   24      http://crbug.com/31497. |   24      http://crbug.com/31497. | 
|   25  |   25  | 
|   26 - expired_cert.pem : An expired certificate, used by test_server.cc. |  | 
|   27  |  | 
|   28 - ok_cert.pem : A valid certificate, used by test_server.cc |  | 
|   29  |  | 
|   30 - root_ca_cert.crt : The testing root CA used to sign the test_server.cc's |  | 
|   31      certificates. |  | 
|   32  |  | 
|   33 - unosoft_hu_cert : Certificate used by X509CertificateTest.UnoSoftCertParsing. |   26 - unosoft_hu_cert : Certificate used by X509CertificateTest.UnoSoftCertParsing. | 
|   34  |   27  | 
|   35 - client.p12 : A PKCS #12 file containing a client certificate and a private |   28 - client.p12 : A PKCS #12 file containing a client certificate and a private | 
|   36      key created for testing.  The password is "12345". |   29      key created for testing.  The password is "12345". | 
|   37  |   30  | 
|   38 - client-nokey.p12 : A PKCS #12 file containing a client certificate (the same |   31 - client-nokey.p12 : A PKCS #12 file containing a client certificate (the same | 
|   39      as the one in client.p12) but no private key. The password is "12345". |   32      as the one in client.p12) but no private key. The password is "12345". | 
|   40  |   33  | 
|   41 - punycodetest.der : A test self-signed server certificate with punycode name. |   34 - punycodetest.der : A test self-signed server certificate with punycode name. | 
|   42      The common name is "xn--wgv71a119e.com" (日本語.com) |   35      The common name is "xn--wgv71a119e.com" (日本語.com) | 
| (...skipping 162 matching lines...) Expand 10 before | Expand all | Expand 10 after  Loading... | 
|  205      2048-bit root. For clients that only support the GTE root, two versions |  198      2048-bit root. For clients that only support the GTE root, two versions | 
|  206      of the Baltimore root were cross-signed by GTE, namely |  199      of the Baltimore root were cross-signed by GTE, namely | 
|  207      _cross_certified_[1,2].pem. _omniroot_chain.pem contains a certificate |  200      _cross_certified_[1,2].pem. _omniroot_chain.pem contains a certificate | 
|  208      chain that was issued under the Baltimore root. Combined, these |  201      chain that was issued under the Baltimore root. Combined, these | 
|  209      certificates can be used to test real-world cross-signing; in practice, |  202      certificates can be used to test real-world cross-signing; in practice, | 
|  210      they are used to test certain workarounds for OS X's chain building code. |  203      they are used to test certain workarounds for OS X's chain building code. | 
|  211  |  204  | 
|  212 - no_subject_common_name_cert.pem: Used to test the function that generates a |  205 - no_subject_common_name_cert.pem: Used to test the function that generates a | 
|  213   NSS certificate nickname for a user certificate. This certificate's Subject |  206   NSS certificate nickname for a user certificate. This certificate's Subject | 
|  214   field doesn't have a common name. |  207   field doesn't have a common name. | 
 |  208  | 
 |  209 - expired_cert.pem | 
 |  210 - ok_cert.pem | 
 |  211 - root_ca_cert.pem | 
 |  212      These certificates are the common certificates used by the Python test | 
 |  213      server for simulating HTTPS connections. They are generated by running | 
 |  214      the script net/data/ssl/scripts/generate-test-certs.sh. | 
 |  215  | 
| OLD | NEW |