kris
/
boringssl
1
0
Förgrening 0
Kod Ärenden 0 Pull-förfrågningar 0 Släpp 0 Wiki Aktiviteter
Du kan inte välja fler än 25 ämnen Ämnen måste starta med en bokstav eller siffra, kan innehålla bindestreck ('-') och vara max 35 tecken långa.
3578 Incheckningar
12 Grenar
38 MiB
Träd: 8a55ce4954
Grenar Taggar
${ item.name }
Skapa branchen ${ searchTerm }
från '8a55ce4954'
${ noResults }
boringssl/crypto/err/asn1.errordata

asn1.errordata 2.6 KiB
Rå Normal vy Historik

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>
9 år sedan
​
​
​
​
​
​
​
Align with upstream's error strings, take two. I messed up a few of these. ASN1_R_UNSUPPORTED_ALGORITHM doesn't exist. X509_R_UNSUPPORTED_ALGORITHM does exist as part of X509_PUBKEY_set, but the SPKI parser doesn't emit this. (I don't mind the legacy code having really weird errors, but since EVP is now limited to things we like, let's try to keep that clean.) To avoid churn in Conscrypt, we'll keep defining X509_R_UNSUPPORTED_ALGORITHM, but not actually do anything with it anymore. Conscrypt was already aware of EVP_R_UNSUPPORTED_ALGORITHM, so this should be fine. (I don't expect EVP_R_UNSUPPORTED_ALGORITHM to go away. The SPKI parsers we like live in EVP now.) A few other ASN1_R_* values didn't quite match upstream, so make those match again. Finally, I got some of the rsa_pss.c values wrong. Each of those corresponds to an (overly specific) RSA_R_* value in upstream. However, those were gone in BoringSSL since even the initial commit. We placed the RSA <-> EVP glue in crypto/evp (so crypto/rsa wouldn't depend on crypto/evp) while upstream placed them in crypto/rsa. Since no one seemed to notice the loss of RSA_R_INVALID_SALT_LENGTH, let's undo all the cross-module errors inserted in crypto/rsa. Instead, since that kind of specificity is not useful, funnel it all into X509_R_INVALID_PSS_PARAMETERS (formerly EVP_R_INVALID_PSS_PARAMETERS, formerly RSA_R_INVALID_PSS_PARAMETERS). Reset the error codes for all affected modules. (That our error code story means error codes are not stable across this kind of refactoring is kind of a problem. Hopefully this will be the last of it.) Change-Id: Ibfb3a0ac340bfc777bc7de6980ef3ddf0a8c84bc Reviewed-on: https://boringssl-review.googlesource.com/7458 Reviewed-by: Emily Stark (Dunn) <estark@google.com> Reviewed-by: David Benjamin <davidben@google.com>
8 år sedan
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Match upstream's error codes for the old sigalg code. People seem to condition on these a lot. Since this code has now been moved twice, just make them all cross-module errors rather than leave a trail of renamed error codes in our wake. Change-Id: Iea18ab3d320f03cf29a64a27acca119768c4115c Reviewed-on: https://boringssl-review.googlesource.com/7431 Reviewed-by: Emily Stark (Dunn) <estark@google.com> Reviewed-by: David Benjamin <davidben@google.com>
8 år sedan
Align with upstream's error strings, take two. I messed up a few of these. ASN1_R_UNSUPPORTED_ALGORITHM doesn't exist. X509_R_UNSUPPORTED_ALGORITHM does exist as part of X509_PUBKEY_set, but the SPKI parser doesn't emit this. (I don't mind the legacy code having really weird errors, but since EVP is now limited to things we like, let's try to keep that clean.) To avoid churn in Conscrypt, we'll keep defining X509_R_UNSUPPORTED_ALGORITHM, but not actually do anything with it anymore. Conscrypt was already aware of EVP_R_UNSUPPORTED_ALGORITHM, so this should be fine. (I don't expect EVP_R_UNSUPPORTED_ALGORITHM to go away. The SPKI parsers we like live in EVP now.) A few other ASN1_R_* values didn't quite match upstream, so make those match again. Finally, I got some of the rsa_pss.c values wrong. Each of those corresponds to an (overly specific) RSA_R_* value in upstream. However, those were gone in BoringSSL since even the initial commit. We placed the RSA <-> EVP glue in crypto/evp (so crypto/rsa wouldn't depend on crypto/evp) while upstream placed them in crypto/rsa. Since no one seemed to notice the loss of RSA_R_INVALID_SALT_LENGTH, let's undo all the cross-module errors inserted in crypto/rsa. Instead, since that kind of specificity is not useful, funnel it all into X509_R_INVALID_PSS_PARAMETERS (formerly EVP_R_INVALID_PSS_PARAMETERS, formerly RSA_R_INVALID_PSS_PARAMETERS). Reset the error codes for all affected modules. (That our error code story means error codes are not stable across this kind of refactoring is kind of a problem. Hopefully this will be the last of it.) Change-Id: Ibfb3a0ac340bfc777bc7de6980ef3ddf0a8c84bc Reviewed-on: https://boringssl-review.googlesource.com/7458 Reviewed-by: Emily Stark (Dunn) <estark@google.com> Reviewed-by: David Benjamin <davidben@google.com>
8 år sedan
​
 1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192 
  1. ASN1,100,ASN1_LENGTH_MISMATCH

  2. ASN1,101,AUX_ERROR

  3. ASN1,102,BAD_GET_ASN1_OBJECT_CALL

  4. ASN1,103,BAD_OBJECT_HEADER

  5. ASN1,104,BMPSTRING_IS_WRONG_LENGTH

  6. ASN1,105,BN_LIB

  7. ASN1,106,BOOLEAN_IS_WRONG_LENGTH

  8. ASN1,107,BUFFER_TOO_SMALL

  9. ASN1,108,CONTEXT_NOT_INITIALISED

  10. ASN1,109,DECODE_ERROR

  11. ASN1,110,DEPTH_EXCEEDED

  12. ASN1,111,DIGEST_AND_KEY_TYPE_NOT_SUPPORTED

  13. ASN1,112,ENCODE_ERROR

  14. ASN1,113,ERROR_GETTING_TIME

  15. ASN1,114,EXPECTING_AN_ASN1_SEQUENCE

  16. ASN1,115,EXPECTING_AN_INTEGER

  17. ASN1,116,EXPECTING_AN_OBJECT

  18. ASN1,117,EXPECTING_A_BOOLEAN

  19. ASN1,118,EXPECTING_A_TIME

  20. ASN1,119,EXPLICIT_LENGTH_MISMATCH

  21. ASN1,120,EXPLICIT_TAG_NOT_CONSTRUCTED

  22. ASN1,121,FIELD_MISSING

  23. ASN1,122,FIRST_NUM_TOO_LARGE

  24. ASN1,123,HEADER_TOO_LONG

  25. ASN1,124,ILLEGAL_BITSTRING_FORMAT

  26. ASN1,125,ILLEGAL_BOOLEAN

  27. ASN1,126,ILLEGAL_CHARACTERS

  28. ASN1,127,ILLEGAL_FORMAT

  29. ASN1,128,ILLEGAL_HEX

  30. ASN1,129,ILLEGAL_IMPLICIT_TAG

  31. ASN1,130,ILLEGAL_INTEGER

  32. ASN1,131,ILLEGAL_NESTED_TAGGING

  33. ASN1,132,ILLEGAL_NULL

  34. ASN1,133,ILLEGAL_NULL_VALUE

  35. ASN1,134,ILLEGAL_OBJECT

  36. ASN1,135,ILLEGAL_OPTIONAL_ANY

  37. ASN1,136,ILLEGAL_OPTIONS_ON_ITEM_TEMPLATE

  38. ASN1,137,ILLEGAL_TAGGED_ANY

  39. ASN1,138,ILLEGAL_TIME_VALUE

  40. ASN1,139,INTEGER_NOT_ASCII_FORMAT

  41. ASN1,140,INTEGER_TOO_LARGE_FOR_LONG

  42. ASN1,141,INVALID_BIT_STRING_BITS_LEFT

  43. ASN1,142,INVALID_BMPSTRING_LENGTH

  44. ASN1,143,INVALID_DIGIT

  45. ASN1,144,INVALID_MODIFIER

  46. ASN1,145,INVALID_NUMBER

  47. ASN1,146,INVALID_OBJECT_ENCODING

  48. ASN1,147,INVALID_SEPARATOR

  49. ASN1,148,INVALID_TIME_FORMAT

  50. ASN1,149,INVALID_UNIVERSALSTRING_LENGTH

  51. ASN1,150,INVALID_UTF8STRING

  52. ASN1,151,LIST_ERROR

  53. ASN1,152,MISSING_ASN1_EOS

  54. ASN1,153,MISSING_EOC

  55. ASN1,154,MISSING_SECOND_NUMBER

  56. ASN1,155,MISSING_VALUE

  57. ASN1,156,MSTRING_NOT_UNIVERSAL

  58. ASN1,157,MSTRING_WRONG_TAG

  59. ASN1,158,NESTED_ASN1_ERROR

  60. ASN1,159,NESTED_ASN1_STRING

  61. ASN1,160,NON_HEX_CHARACTERS

  62. ASN1,161,NOT_ASCII_FORMAT

  63. ASN1,162,NOT_ENOUGH_DATA

  64. ASN1,163,NO_MATCHING_CHOICE_TYPE

  65. ASN1,164,NULL_IS_WRONG_LENGTH

  66. ASN1,165,OBJECT_NOT_ASCII_FORMAT

  67. ASN1,166,ODD_NUMBER_OF_CHARS

  68. ASN1,167,SECOND_NUMBER_TOO_LARGE

  69. ASN1,168,SEQUENCE_LENGTH_MISMATCH

  70. ASN1,169,SEQUENCE_NOT_CONSTRUCTED

  71. ASN1,170,SEQUENCE_OR_SET_NEEDS_CONFIG

  72. ASN1,171,SHORT_LINE

  73. ASN1,172,STREAMING_NOT_SUPPORTED

  74. ASN1,173,STRING_TOO_LONG

  75. ASN1,174,STRING_TOO_SHORT

  76. ASN1,175,TAG_VALUE_TOO_HIGH

  77. ASN1,176,TIME_NOT_ASCII_FORMAT

  78. ASN1,177,TOO_LONG

  79. ASN1,178,TYPE_NOT_CONSTRUCTED

  80. ASN1,179,TYPE_NOT_PRIMITIVE

  81. ASN1,180,UNEXPECTED_EOC

  82. ASN1,181,UNIVERSALSTRING_IS_WRONG_LENGTH

  83. ASN1,182,UNKNOWN_FORMAT

  84. ASN1,183,UNKNOWN_MESSAGE_DIGEST_ALGORITHM

  85. ASN1,184,UNKNOWN_SIGNATURE_ALGORITHM

  86. ASN1,185,UNKNOWN_TAG

  87. ASN1,186,UNSUPPORTED_ANY_DEFINED_BY_TYPE

  88. ASN1,187,UNSUPPORTED_PUBLIC_KEY_TYPE

  89. ASN1,188,UNSUPPORTED_TYPE

  90. ASN1,189,WRONG_PUBLIC_KEY_TYPE

  91. ASN1,190,WRONG_TAG

  92. ASN1,191,WRONG_TYPE