kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
b018908475
boringssl/crypto/err/pkcs8.errordata

34 lines
1010 B
Plaintext
Raw Normal View History

Update pkcs8 error data. We forgot to run the script at some point. Change-Id: I0bd142fdd13d64c1ed81d9b1515449220d1c936b Reviewed-on: https://boringssl-review.googlesource.com/14329 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-03-22 22:38:16 +00:00
PKCS8,129,BAD_ITERATION_COUNT
Get rid of err function codes. Running make_errors.go every time a function is renamed is incredibly tedious. Plus we keep getting them wrong. Instead, sample __func__ (__FUNCTION__ in MSVC) in the OPENSSL_PUT_ERROR macro and store it alongside file and line number. This doesn't change the format of ERR_print_errors, however ERR_error_string_n now uses the placeholder "OPENSSL_internal" rather than an actual function name since that only takes the uint32_t packed error code as input. This updates err scripts to not emit the function string table. The OPENSSL_PUT_ERROR invocations, for now, still include the extra parameter. That will be removed in a follow-up. BUG=468039 Change-Id: Iaa2ef56991fb58892fa8a1283b3b8b995fbb308d Reviewed-on: https://boringssl-review.googlesource.com/5275 Reviewed-by: Adam Langley <agl@google.com>
2015-06-29 04:36:21 +01:00
PKCS8,100,BAD_PKCS12_DATA
PKCS8,101,BAD_PKCS12_VERSION
PKCS8,102,CIPHER_HAS_NO_OBJECT_IDENTIFIER
PKCS8,103,CRYPT_ERROR
PKCS8,104,DECODE_ERROR
PKCS8,105,ENCODE_ERROR
PKCS8,106,ENCRYPT_ERROR
PKCS8,107,ERROR_SETTING_CIPHER_PARAMS
PKCS8,108,INCORRECT_PASSWORD
Treat PKCS#12 passwords as UTF-8. This aligns with OpenSSL 1.1.0's behavior, which deviated from OpenSSL 1.0.2. OpenSSL 1.0.2 effectively assumed input passwords were always Latin-1. Update-Note: If anyone was using PKCS#12 passwords with non-ASCII characters, this changes them from being encoding-confused to hopefully interpretting "correctly". If this breaks anything, we can add a fallback to PKCS12_get_key_and_certs/PKCS12_parse, but OpenSSL 1.1.0 does not have such behavior. It only implements a fallback in the command-line tool, not the APIs. Change-Id: I0aa92db26077b07a40f85b89f4d3e0f6b0d7be87 Reviewed-on: https://boringssl-review.googlesource.com/28326 Reviewed-by: Adam Langley <agl@google.com>
2018-05-10 00:58:51 +01:00
PKCS8,131,INVALID_CHARACTERS
Get rid of err function codes. Running make_errors.go every time a function is renamed is incredibly tedious. Plus we keep getting them wrong. Instead, sample __func__ (__FUNCTION__ in MSVC) in the OPENSSL_PUT_ERROR macro and store it alongside file and line number. This doesn't change the format of ERR_print_errors, however ERR_error_string_n now uses the placeholder "OPENSSL_internal" rather than an actual function name since that only takes the uint32_t packed error code as input. This updates err scripts to not emit the function string table. The OPENSSL_PUT_ERROR invocations, for now, still include the extra parameter. That will be removed in a follow-up. BUG=468039 Change-Id: Iaa2ef56991fb58892fa8a1283b3b8b995fbb308d Reviewed-on: https://boringssl-review.googlesource.com/5275 Reviewed-by: Adam Langley <agl@google.com>
2015-06-29 04:36:21 +01:00
PKCS8,109,KEYGEN_FAILURE
PKCS8,110,KEY_GEN_ERROR
PKCS8,111,METHOD_NOT_SUPPORTED
PKCS8,112,MISSING_MAC
PKCS8,113,MULTIPLE_PRIVATE_KEYS_IN_PKCS12
PKCS8,114,PKCS12_PUBLIC_KEY_INTEGRITY_NOT_SUPPORTED
PKCS8,115,PKCS12_TOO_DEEPLY_NESTED
PKCS8,116,PRIVATE_KEY_DECODE_ERROR
PKCS8,117,PRIVATE_KEY_ENCODE_ERROR
PKCS8,118,TOO_LONG
PKCS8,119,UNKNOWN_ALGORITHM
PKCS8,120,UNKNOWN_CIPHER
PKCS8,121,UNKNOWN_CIPHER_ALGORITHM
PKCS8,122,UNKNOWN_DIGEST
PKCS8,123,UNKNOWN_HASH
Update pkcs8 error data. We forgot to run the script at some point. Change-Id: I0bd142fdd13d64c1ed81d9b1515449220d1c936b Reviewed-on: https://boringssl-review.googlesource.com/14329 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-03-22 22:38:16 +00:00
PKCS8,127,UNSUPPORTED_CIPHER
PKCS8,125,UNSUPPORTED_KEYLENGTH
PKCS8,128,UNSUPPORTED_KEY_DERIVATION_FUNCTION
Add PKCS12_create. PyOpenSSL calls this function these days. Tested by roundtripping with ourselves and also manually confirming our output interoperates with OpenSSL. (For anyone repeating this experiment, the OpenSSL command-line tool has a bug and does not correctly output friendlyName attributes with non-ASCII characters. I'll send them a PR to fix this shortly.) Between this and the UTF-8 logic earlier, the theme of this patch series seems to be "implement in C something I last implemented in JavaScript"... Change-Id: I258d563498d82998c6bffc6789efeaba36fe3a5e Reviewed-on: https://boringssl-review.googlesource.com/28328 Reviewed-by: Adam Langley <agl@google.com>
2018-05-09 22:28:09 +01:00
PKCS8,132,UNSUPPORTED_OPTIONS
Update pkcs8 error data. We forgot to run the script at some point. Change-Id: I0bd142fdd13d64c1ed81d9b1515449220d1c936b Reviewed-on: https://boringssl-review.googlesource.com/14329 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-03-22 22:38:16 +00:00
PKCS8,130,UNSUPPORTED_PRF
Get rid of err function codes. Running make_errors.go every time a function is renamed is incredibly tedious. Plus we keep getting them wrong. Instead, sample __func__ (__FUNCTION__ in MSVC) in the OPENSSL_PUT_ERROR macro and store it alongside file and line number. This doesn't change the format of ERR_print_errors, however ERR_error_string_n now uses the placeholder "OPENSSL_internal" rather than an actual function name since that only takes the uint32_t packed error code as input. This updates err scripts to not emit the function string table. The OPENSSL_PUT_ERROR invocations, for now, still include the extra parameter. That will be removed in a follow-up. BUG=468039 Change-Id: Iaa2ef56991fb58892fa8a1283b3b8b995fbb308d Reviewed-on: https://boringssl-review.googlesource.com/5275 Reviewed-by: Adam Langley <agl@google.com>
2015-06-29 04:36:21 +01:00
PKCS8,124,UNSUPPORTED_PRIVATE_KEY_ALGORITHM
Update pkcs8 error data. We forgot to run the script at some point. Change-Id: I0bd142fdd13d64c1ed81d9b1515449220d1c936b Reviewed-on: https://boringssl-review.googlesource.com/14329 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-03-22 22:38:16 +00:00
PKCS8,126,UNSUPPORTED_SALT_TYPE
Reference in New Issue Copy Permalink