yuzu-emu/mbedtls
1
0
Fork 0
mirror of https://github.com/yuzu-emu/mbedtls.git synced 2024-11-23 16:55:47 +01:00
Code Issues Packages Projects Releases Wiki Activity
9c7e92b5db
mbedtls/tests/data_files/cert_sha224.crt

21 lines
1.2 KiB
Plaintext
Raw Normal View History

- Added extra certificates and tests
2009-07-12 13:11:06 +02:00
-----BEGIN CERTIFICATE-----
- Corrected parsing of UTCTime dates before 1990 and after 1950 - Support more exotic OID's when parsing certificates - Support more exotic name representations when parsing certificates - Replaced the expired test certificates
2011-02-20 11:40:16 +01:00
MIIDQjCCAiqgAwIBAgIBCDANBgkqhkiG9w0BAQ4FADA7MQswCQYDVQQGEwJOTDER
Regenerate test client certificates with a PrintableString issuer The test certificate used for clients in compat.sh, cert_sha256.crt, had the issuer ON and CN encoded as UTF8String, but the corresponding CA certificate test-ca_cat12.crt had them encoded as PrintableString. The strings matched, which is sufficient according to RFC 5280 §7.1 and RFC 4518 §2.1. However, GnuTLS 3.4.10 requires the strings to have the same encoding, so it did not accept that the certificate issued by UTF8String "PolarSSL Test CA" was validly issued by the PrintableString "PolarSSL Test CA" CA. ebc1f40aa008f6a2ba42e7436e4596d8f780b612, merged via https://github.com/ARMmbed/mbedtls/pull/1641 and released in Mbed TLS 2.14, updated these certificates. 4f928c0f374558ec352825061a399db7a37ca2fc merged, via https://github.com/ARMmbed/mbedtls/pull/2418 fixed this in the 2.7 LTS branch for the SHA-1 certificate which was used at the time. The present commit applies the same fix for the SHA-256 certificate that is now in use. For uniformity, this commit regenerates all the cert_*.crt. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2020-08-21 19:09:34 +02:00
MA8GA1UEChMIUG9sYXJTU0wxGTAXBgNVBAMTEFBvbGFyU1NMIFRlc3QgQ0EwHhcN
Update certificates to expire in 2029 Update certificates that expire on 2021, to prolong their validity, to make tests pass three years ahead.
2019-02-12 14:03:42 +01:00
MTkwMjEwMTQ0NDA2WhcNMjkwMjEwMTQ0NDA2WjA/MQswCQYDVQQGEwJOTDERMA8G
Regenerate test client certificates with a PrintableString issuer The test certificate used for clients in compat.sh, cert_sha256.crt, had the issuer ON and CN encoded as UTF8String, but the corresponding CA certificate test-ca_cat12.crt had them encoded as PrintableString. The strings matched, which is sufficient according to RFC 5280 §7.1 and RFC 4518 §2.1. However, GnuTLS 3.4.10 requires the strings to have the same encoding, so it did not accept that the certificate issued by UTF8String "PolarSSL Test CA" was validly issued by the PrintableString "PolarSSL Test CA" CA. ebc1f40aa008f6a2ba42e7436e4596d8f780b612, merged via https://github.com/ARMmbed/mbedtls/pull/1641 and released in Mbed TLS 2.14, updated these certificates. 4f928c0f374558ec352825061a399db7a37ca2fc merged, via https://github.com/ARMmbed/mbedtls/pull/2418 fixed this in the 2.7 LTS branch for the SHA-1 certificate which was used at the time. The present commit applies the same fix for the SHA-256 certificate that is now in use. For uniformity, this commit regenerates all the cert_*.crt. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2020-08-21 19:09:34 +02:00
A1UEChMIUG9sYXJTU0wxHTAbBgNVBAMTFFBvbGFyU1NMIENlcnQgU0hBMjI0MIIB
Update certificates to expire in 2029 Update certificates that expire on 2021, to prolong their validity, to make tests pass three years ahead.
2019-02-12 14:03:42 +01:00
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqQIfPUBq1VVTi/027oJlLhVh
Xom/uOhFkNvuiBZS0/FDUEeWEllkh2v9K+BG+XO+3c+S4ZFb7Wagb4kpeUWA0INq
1UFDd185fAkER4KwVzlw7aPsFRkeqDMIR8EFQqn9TMO0390GH00QUUBncxMPQPht
gSVfCrFTxjB+FTms+Vruf5KepgVb5xOXhbUjktnUJAbVCSWJdQfdphqPPwkZvq1l
LGTrlZvc/kFeF6babFtpzAK6FCwWJJxK3M3Q91Jnc/EtoCP9fvQxyi1wyokLBNsu
pk9wbp7OvViJ4lNZnm5akmXiiD8MlBmj3eXonZUT7Snbq3AS3FrKaxerUoJUsQID
AQABo00wSzAJBgNVHRMEAjAAMB0GA1UdDgQWBBQfdNY/KcF0dEU7BRIsPai9Q1kC
pjAfBgNVHSMEGDAWgBS0WuSls97SUva51aaVD+s+vMf9/zANBgkqhkiG9w0BAQ4F
Regenerate test client certificates with a PrintableString issuer The test certificate used for clients in compat.sh, cert_sha256.crt, had the issuer ON and CN encoded as UTF8String, but the corresponding CA certificate test-ca_cat12.crt had them encoded as PrintableString. The strings matched, which is sufficient according to RFC 5280 §7.1 and RFC 4518 §2.1. However, GnuTLS 3.4.10 requires the strings to have the same encoding, so it did not accept that the certificate issued by UTF8String "PolarSSL Test CA" was validly issued by the PrintableString "PolarSSL Test CA" CA. ebc1f40aa008f6a2ba42e7436e4596d8f780b612, merged via https://github.com/ARMmbed/mbedtls/pull/1641 and released in Mbed TLS 2.14, updated these certificates. 4f928c0f374558ec352825061a399db7a37ca2fc merged, via https://github.com/ARMmbed/mbedtls/pull/2418 fixed this in the 2.7 LTS branch for the SHA-1 certificate which was used at the time. The present commit applies the same fix for the SHA-256 certificate that is now in use. For uniformity, this commit regenerates all the cert_*.crt. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2020-08-21 19:09:34 +02:00
AAOCAQEAeRpMhu1KTn2NQjCCPaRkOO38EPhlc6/jolqvb+2h7evGk0u606uHLDPg
ejUUmuHpJTGbVgU27dRucSUaAlGOE0SJvLyRlvhjFwKQczdZBi4zGbsokTl9Oi6r
BOHDTpDr3OQ1FIxGHyTnxKgw1/WBHaqPmT5tS6UwItQ22XRhrZffi9QZJ8AQElAd
7Z7whSwsV77SCQow4VbHYl5o+vUB1jG0MrQu8FoOVt6/HXHyKCZsGzkp8SXhGzl+
Oy0eCbLETKieg9bUGH3hVYsH64JsZpVfTp1WaDm0Duui2gRIL2ROetA6xoROwl5j
PmTT7I0AJVzCvnt4kYxHAMD0RGBd1A==
- Added extra certificates and tests
2009-07-12 13:11:06 +02:00
-----END CERTIFICATE-----
Reference in New Issue Copy Permalink