John Safranek 6298074f93 OCSP and ECDSA Signers ...

OCSP uses an identified hash of the issuer's public key to identify the
certificate's signer. (Typically this is SHA-1, but can be any SHA
hash.) The AKID/SKID for the certificates usually are the SHA-1 hash of
the public key, but may be anything. We cannot depend on the AKID for
OCSP purposes. For OCSP lookups, wolfSSL calculates the hash of the
public key based on the copy saved for use with the handshake signing.
For RSA, that was fine. For ECDSA, we use the whole public key including
the curve ID, but for OCSP the curve ID isn't hashed. Stored the hash of
the public key at the point where we are looking at the key when reading
in the certificate, and saving the hash in the signer record.

2019-02-07 17:34:25 -08:00

..

benchmark

Merge pull request #2061 from SparkiDev/x86_asm_not_in_c

2019-02-01 10:01:34 -08:00

src

OCSP and ECDSA Signers

2019-02-07 17:34:25 -08:00

test

Merge pull request #2061 from SparkiDev/x86_asm_not_in_c

2019-02-01 10:01:34 -08:00

user-crypto

Fix for unused variable in new fast-rsa function wc_RsaPublicKeyDecode_ex.

2018-10-25 11:12:33 -07:00