diff options
author | David Benjamin <davidben@chromium.org> | 2016-01-30 22:58:52 +0300 |
---|---|---|
committer | Adam Langley <agl@google.com> | 2016-02-27 01:39:02 +0300 |
commit | 17727c6843e3b3d4ec93132a454732dd5176ff85 (patch) | |
tree | 51dc0c980d6da8456ae0178245b9f2b49fe331a4 /crypto/err | |
parent | 93a69b4f8f33d70a3350512ec744b5b948fe2f6b (diff) |
Move all signature algorithm code to crypto/x509.
All the signature algorithm logic depends on X509_ALGOR. This also
removes the X509_ALGOR-based EVP functions which are no longer used
externally. I think those APIs were a mistake on my part. The use in
Chromium was unnecessary (and has since been removed anyway). The new
X.509 stack will want to process the signatureAlgorithm itself to be
able to enforce policies on it.
This also moves the RSA_PSS_PARAMS bits to crypto/x509 from crypto/rsa.
That struct is also tied to crypto/x509. Any new RSA-PSS code would
have to use something else anyway.
BUG=499653
Change-Id: I6c4b4573b2800a2e0f863d35df94d048864b7c41
Reviewed-on: https://boringssl-review.googlesource.com/7025
Reviewed-by: Adam Langley <agl@google.com>
Diffstat (limited to 'crypto/err')
-rw-r--r-- | crypto/err/x509.errordata | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/crypto/err/x509.errordata b/crypto/err/x509.errordata index f4828ce8..727d7296 100644 --- a/crypto/err/x509.errordata +++ b/crypto/err/x509.errordata @@ -4,12 +4,16 @@ X509,102,BAD_X509_FILETYPE X509,103,BASE64_DECODE_ERROR X509,104,CANT_CHECK_DH_KEY X509,105,CERT_ALREADY_IN_HASH_TABLE +X509,137,CONTEXT_NOT_INITIALISED X509,106,CRL_ALREADY_DELTA X509,107,CRL_VERIFY_FAILURE X509,108,IDP_MISMATCH X509,109,INVALID_BIT_STRING_BITS_LEFT X509,110,INVALID_DIRECTORY X509,111,INVALID_FIELD_NAME +X509,138,INVALID_PSS_PARAMETERS +X509,139,INVALID_SALT_LENGTH +X509,140,INVALID_TRAILER X509,112,INVALID_TRUST X509,113,ISSUER_MISMATCH X509,114,KEY_TYPE_MISMATCH @@ -34,4 +38,5 @@ X509,131,UNKNOWN_PURPOSE_ID X509,132,UNKNOWN_TRUST_ID X509,133,UNSUPPORTED_ALGORITHM X509,134,WRONG_LOOKUP_TYPE +X509,141,WRONG_PUBLIC_KEY_TYPE X509,135,WRONG_TYPE |