Mirror of BoringSSL (grpc依赖) https://boringssl.googlesource.com/boringssl
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
..
README
annotate_test_data.py
ecdsa-prime256v1-sha512-spki-params-null.pem
ecdsa-prime256v1-sha512-unused-bits-signature.pem
ecdsa-prime256v1-sha512-using-ecdh-key.pem
ecdsa-prime256v1-sha512-using-ecmqv-key.pem
ecdsa-prime256v1-sha512-using-rsa-algorithm.pem
ecdsa-prime256v1-sha512-wrong-signature-format.pem
ecdsa-prime256v1-sha512.pem
ecdsa-secp384r1-sha256-corrupted-data.pem
ecdsa-secp384r1-sha256.pem
ecdsa-using-rsa-key.pem
rsa-pkcs1-sha1-bad-key-der-length.pem
rsa-pkcs1-sha1-bad-key-der-null.pem
rsa-pkcs1-sha1-key-params-absent.pem
rsa-pkcs1-sha1-using-pss-key-no-params.pem
rsa-pkcs1-sha1-wrong-algorithm.pem
rsa-pkcs1-sha1.pem
rsa-pkcs1-sha256-key-encoded-ber.pem
rsa-pkcs1-sha256-spki-non-null-params.pem
rsa-pkcs1-sha256-using-ecdsa-algorithm.pem
rsa-pkcs1-sha256-using-id-ea-rsa.pem
rsa-pkcs1-sha256.pem
rsa-pss-sha256-using-pss-key-with-params.pem
rsa-pss-sha256-wrong-salt.pem
rsa-pss-sha256.pem
rsa-using-ec-key.pem
rsa2048-pkcs1-sha512.pem

README

This directory contains test data for testing net::VerifySignedData().

When adding or changing test data, run the script
$ python annotate_test_data.py

This script will apply a uniform formatting. For instance it will add a
comment showing what the parsed ASN.1 looks like, and reformat the base64 to
have consistent line breaks.

The general format for the test files is as follows:


<A description of the test>

-----BEGIN PUBLIC KEY-----
<base64-encoded, DER-encoded, SPKI>
-----END PUBLIC KEY-----

-----BEGIN ALGORITHM-----
<base64-encoded, DER-encoded, AlgorithmIdentifier for the signature.>
-----END ALGORITHM-----

-----BEGIN DATA-----
<base64-encoded data that is being verified>
-----END DATA-----

-----BEGIN SIGNATURE-----
<base64-encoded, DER-encoded, BIT STRING of the signature>
-----END SIGNATURE-----


Comments for a PEM block should be placed immediately below that block.
The script will also insert a comment after the block describing its parsed
ASN.1 structure (your extra comments need to be above the script-generated
comments or they will be stripped).