Bring in the core of chromium certificate verifier as libpki Initially this leaves the canonical source in chrome, Additions and fillins are committed directly, the chrome files are coverted using the IMPORT script run from the pki directory for the moment. The intention here is to continue frequent automatic conversion (and avoid wholesale cosmetic changes in here for now) until chrome converts to use these files in place of it's versions. At that point these will become the definiative files, and the IMPORT script can be tossed out. A middle step along the way will be to change google3's verify.cc in third_party/chromium_certificate_verifier to use this instead of it's own extracted copy. Status (and what is not done yet) being roughly tracked in README.md Bug: chromium:1322914 Change-Id: Ibdb5479bc68985fa61ce6b10f98f31f6b3a7cbdf Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/60285 Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Adam Langley <agl@google.com>
diff --git a/pki/testdata/ssl/certificates/key_usage_p256.key b/pki/testdata/ssl/certificates/key_usage_p256.key new file mode 100644 index 0000000..0143378 --- /dev/null +++ b/pki/testdata/ssl/certificates/key_usage_p256.key
@@ -0,0 +1,5 @@ +-----BEGIN PRIVATE KEY----- +MIGHAgEAMBMGByqGSM49AgEGCCqGSM49AwEHBG0wawIBAQQgeor3507Mmwvc9idK +suXWTudE0GDlVmEc64H7acez5xShRANCAATzrZ6+AHOlorp9D4i4ZEuFW2IcT16D +RCr5q46eSP89CxqRkr4fDMaHCr0GRwtjBrcnuljjBWRtHTAo7u7yqXuT +-----END PRIVATE KEY-----