kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
5ede28c8a4
boringssl/crypto/err/ssl.errordata

231 lines
7.3 KiB
Plaintext
Raw Normal View History

Add Data-less Zero-RTT support. This adds support on the server and client to accept data-less early data. The server will still fail to parse early data with any contents, so this should remain disabled. BUG=76 Change-Id: Id85d192d8e0360b8de4b6971511b5e8a0e8012f7 Reviewed-on: https://boringssl-review.googlesource.com/12921 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-01-11 16:34:52 +00:00
SSL,277,ALPN_MISMATCH_ON_EARLY_DATA
Detect WatchGuard's TLS 1.3 interference failure mode. WatchGuard's bug is very distinctive. Report a dedicated error code out of BoringSSL so we can better track this. Bug: chromium:733223 Change-Id: Ia42abd8654e7987b1d43c63a4f454f35f6aa873b Reviewed-on: https://boringssl-review.googlesource.com/17328 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-06-22 20:03:18 +01:00
SSL,281,APPLICATION_DATA_INSTEAD_OF_HANDSHAKE
Reject unexpected application data in bidirectional shutdown. Update-Note: This tweaks the SSL_shutdown behavior. OpenSSL's original SSL_shutdown behavior was an incoherent mix of discarding the record and rejecting it (it would return SSL_ERROR_SYSCALL but retrying the operation would discard it). SSLeay appears to have intended to discard it, so we previously "fixed" it actually discard. However, this behavior is somewhat bizarre and means we skip over unbounded data, which we typically try to avoid. If you are trying to cleanly shutdown the TLS portion of your protocol, surely it is at a point where additional data is a syntax error. I suspect I originally did not realize that, because the discarded record did not properly continue the loop, SSL_shutdown would appear as if it rejected the data, and so it's unlikely anyone was relying on that behavior. Discussion in https://github.com/openssl/openssl/pull/6340 suggests (some of) upstream also prefers rejecting. Change-Id: Icde419049306ed17eb06ce1a7e1ff587901166f3 Reviewed-on: https://boringssl-review.googlesource.com/28864 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Steven Valdez <svaldez@google.com>
2018-05-30 15:18:09 +01:00
SSL,291,APPLICATION_DATA_ON_SHUTDOWN
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
SSL,100,APP_DATA_IN_HANDSHAKE
SSL,101,ATTEMPT_TO_REUSE_SESSION_IN_DIFFERENT_CONTEXT
SSL,102,BAD_ALERT
SSL,103,BAD_CHANGE_CIPHER_SPEC
SSL,104,BAD_DATA_RETURNED_BY_CALLBACK
SSL,105,BAD_DH_P_LENGTH
SSL,106,BAD_DIGEST_LENGTH
SSL,107,BAD_ECC_CERT
SSL,108,BAD_ECPOINT
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,109,BAD_HANDSHAKE_RECORD
SSL,110,BAD_HELLO_REQUEST
SSL,111,BAD_LENGTH
SSL,112,BAD_PACKET_LENGTH
SSL,113,BAD_RSA_ENCRYPT
SSL,114,BAD_SIGNATURE
SSL,115,BAD_SRTP_MKI_VALUE
SSL,116,BAD_SRTP_PROTECTION_PROFILE_LIST
SSL,117,BAD_SSL_FILETYPE
SSL,118,BAD_WRITE_RETRY
SSL,119,BIO_NOT_SET
Declare SSL_R_BLOCK_CIPHER_PAD_IS_WRONG and SSL_R_NO_CIPHERS_SPECIFIED. nginx consumes these error codes without #ifdefs. Continue to define them for compatibility, even though we never emit them. BUG=95 Change-Id: I1e991987ce25fc4952cc85b98ffa050a8beab92e Reviewed-on: https://boringssl-review.googlesource.com/10446 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-08-17 20:54:36 +01:00
SSL,261,BLOCK_CIPHER_PAD_IS_WRONG
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,120,BN_LIB
Check for buffered handshake messages on cipher change in DTLS. This is the equivalent of FragmentAcrossChangeCipherSuite for DTLS. It is possible for us to, while receiving pre-CCS handshake messages, to buffer up a message with sequence number meant for a post-CCS Finished. When we then get to the new epoch and attempt to read the Finished, we will process the buffered Finished although it was sent with the wrong encryption. Move ssl_set_{read,write}_state to SSL_PROTOCOL_METHOD hooks as this is a property of the transport. Notably, read_state may fail. In DTLS check the handshake buffer size. We could place this check in read_change_cipher_spec, but TLS 1.3 has no ChangeCipherSpec message, so we will need to implement this at the cipher change point anyway. (For now, there is only an assert on the TLS side. This will be replaced with a proper check in TLS 1.3.) Change-Id: Ia52b0b81e7db53e9ed2d4f6d334a1cce13e93297 Reviewed-on: https://boringssl-review.googlesource.com/8790 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-07-15 04:10:43 +01:00
SSL,255,BUFFERED_MESSAGES_ON_CIPHER_CHANGE
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,121,BUFFER_TOO_SMALL
Add |SSL[_CTX]_set_chain_and_key|. This allows a caller to configure a serving chain without dealing with crypto/x509. Change-Id: Ib42bb2ab9227d32071cf13ab07f92d029643a9a6 Reviewed-on: https://boringssl-review.googlesource.com/14126 Commit-Queue: Adam Langley <alangley@gmail.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-02-28 19:26:51 +00:00
SSL,275,CANNOT_HAVE_BOTH_PRIVKEY_AND_METHOD
Don't depend on the X509 code for getting public keys. This change removes the use of |X509_get_pubkey| from the TLS <= 1.2 code. That function is replaced with a shallow parse of the certificate to extract the public key instead. Change-Id: I8938c6c5a01b32038c6b6fa58eb065e5b44ca6d2 Reviewed-on: https://boringssl-review.googlesource.com/12707 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-12-12 19:37:43 +00:00
SSL,272,CANNOT_PARSE_LEAF_CERT
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,122,CA_DN_LENGTH_MISMATCH
SSL,123,CA_DN_TOO_LONG
SSL,124,CCS_RECEIVED_EARLY
Add |SSL[_CTX]_set_chain_and_key|. This allows a caller to configure a serving chain without dealing with crypto/x509. Change-Id: Ib42bb2ab9227d32071cf13ab07f92d029643a9a6 Reviewed-on: https://boringssl-review.googlesource.com/14126 Commit-Queue: Adam Langley <alangley@gmail.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-02-28 19:26:51 +00:00
SSL,274,CERTIFICATE_AND_PRIVATE_KEY_MISMATCH
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,125,CERTIFICATE_VERIFY_FAILED
SSL,126,CERT_CB_ERROR
Implement the client side of certificate compression. Change-Id: I0aced480af98276ebfe0970b4afb9aa957ee07cb Reviewed-on: https://boringssl-review.googlesource.com/29024 Reviewed-by: Adam Langley <agl@google.com>
2018-06-08 00:39:49 +01:00
SSL,292,CERT_DECOMPRESSION_FAILED
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,127,CERT_LENGTH_MISMATCH
SSL,128,CHANNEL_ID_NOT_P256
SSL,129,CHANNEL_ID_SIGNATURE_INVALID
SSL,130,CIPHER_OR_HASH_UNAVAILABLE
SSL,131,CLIENTHELLO_PARSE_FAILED
SSL,132,CLIENTHELLO_TLSEXT
SSL,133,CONNECTION_REJECTED
SSL,134,CONNECTION_TYPE_NOT_SET
SSL,135,CUSTOM_EXTENSION_ERROR
SSL,136,DATA_LENGTH_TOO_LONG
SSL,137,DECODE_ERROR
SSL,138,DECRYPTION_FAILED
SSL,139,DECRYPTION_FAILED_OR_BAD_RECORD_MAC
SSL,140,DH_PUBLIC_VALUE_LENGTH_IS_WRONG
SSL,141,DH_P_TOO_LONG
SSL,142,DIGEST_CHECK_FAILED
Implement TLS 1.3's downgrade signal. For now, skip the 1.2 -> 1.1 signal since that will affect shipping code. We may as well enable it too, but wait until things have settled down. This implements the version in draft-14 since draft-13's isn't backwards-compatible. Change-Id: I46be43e6f4c5203eb4ae006d1c6a2fe7d7a949ec Reviewed-on: https://boringssl-review.googlesource.com/8724 Reviewed-by: David Benjamin <davidben@google.com>
2016-07-10 17:20:35 +01:00
SSL,254,DOWNGRADE_DETECTED
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,143,DTLS_MESSAGE_TOO_BIG
Add TLS 1.3 1-RTT. This adds the machinery for doing TLS 1.3 1RTT. Change-Id: I736921ffe9dc6f6e64a08a836df6bb166d20f504 Reviewed-on: https://boringssl-review.googlesource.com/8720 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-07-11 18:19:03 +01:00
SSL,257,DUPLICATE_EXTENSION
Fix some bugs in TLS 1.3 server key_share code. Found by libFuzzer and then one more mistake caught by valgrind. Add a test for this case. Change-Id: I92773bc1231bafe5fc069e8568d93ac0df4c8acb Reviewed-on: https://boringssl-review.googlesource.com/11129 Reviewed-by: David Benjamin <davidben@google.com>
2016-09-21 00:24:40 +01:00
SSL,264,DUPLICATE_KEY_SHARE
Support OpenSSL APIs SSL[_CTX]_set1_sigalgs[_list]. These functions can be used to configure the signature algorithms. One of them is a string mini-languaging parsing function, which we generally dislike because it defeats static analysis. However, some dependent projects (in this case TensorFlow) need it and we also dislike making people patch. Change-Id: I13f990c896a7f7332d78b1c351357d418ade8d11 Reviewed-on: https://boringssl-review.googlesource.com/30304 Reviewed-by: Steven Valdez <svaldez@google.com>
2018-08-03 18:31:21 +01:00
SSL,296,DUPLICATE_SIGNATURE_ALGORITHM
Implement TLS 1.3 early exporters. Bug: 222 Change-Id: I33ee56358a62afcd9c3921026d55efcc543a5c11 Reviewed-on: https://boringssl-review.googlesource.com/23945 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-12-08 22:05:06 +00:00
SSL,283,EARLY_DATA_NOT_IN_USE
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,144,ECC_CERT_NOT_FOR_SIGNING
Run TLS 1.3 tests at all variants and fix bugs. We were only running a random subset of TLS 1.3 tests with variants and let a lot of bugs through as a result. - HelloRetryRequest-EmptyCookie wasn't actually testing what we were trying to test. - The second HelloRetryRequest detection needs tweaks in draft-22. - The empty HelloRetryRequest logic can't be based on non-empty extensions in draft-22. - We weren't sending ChangeCipherSpec correctly in HRR or testing it right. - Rework how runner reads ChangeCipherSpec by setting a flag which affects the next readRecord. This cuts down a lot of cases and works correctly if the client didn't send early data. (In that case, we don't flush CCS until EndOfEarlyData and runner deadlocks waiting for the ChangeCipherSpec to arrive.) Change-Id: I559c96ea3a8b350067e391941231713c6edb2f78 Reviewed-on: https://boringssl-review.googlesource.com/23125 Reviewed-by: Steven Valdez <svaldez@chromium.org> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-11-16 23:36:38 +00:00
SSL,282,EMPTY_HELLO_RETRY_REQUEST
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,145,EMS_STATE_INCONSISTENT
SSL,146,ENCRYPTED_LENGTH_TOO_LONG
SSL,147,ERROR_ADDING_EXTENSION
SSL,148,ERROR_IN_RECEIVED_CIPHER_LIST
SSL,149,ERROR_PARSING_EXTENSION
SSL,150,EXCESSIVE_MESSAGE_SIZE
SSL,151,EXTRA_DATA_IN_MESSAGE
SSL,152,FRAGMENT_MISMATCH
SSL,153,GOT_NEXT_PROTO_WITHOUT_EXTENSION
SSL,154,HANDSHAKE_FAILURE_ON_CLIENT_HELLO
SSL_export_keying_material should work in half-RTT. QUIC will need to derive keys at this point. This also smooths over a part of the server 0-RTT abstraction. Like with False Start, the SSL object is largely in a functional state at this point. Bug: 221 Change-Id: I4207d8cb1273a1156e728a7bff3943cc2c69e288 Reviewed-on: https://boringssl-review.googlesource.com/24224 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-12-16 19:37:26 +00:00
SSL,284,HANDSHAKE_NOT_COMPLETE
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,155,HTTPS_PROXY_REQUEST
SSL,156,HTTP_REQUEST
SSL,157,INAPPROPRIATE_FALLBACK
Enforce the server ALPN protocol was advertised. The server should not be allowed select a protocol that wasn't advertised. Callers tend to not really notice and act as if some default were chosen which is unlikely to work very well. Change-Id: Ib6388db72f05386f854d275bab762ca79e8174e6 Reviewed-on: https://boringssl-review.googlesource.com/10284 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-08-11 16:52:23 +01:00
SSL,259,INVALID_ALPN_PROTOCOL
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,158,INVALID_COMMAND
Add TLS 1.3 1-RTT. This adds the machinery for doing TLS 1.3 1RTT. Change-Id: I736921ffe9dc6f6e64a08a836df6bb166d20f504 Reviewed-on: https://boringssl-review.googlesource.com/8720 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-07-11 18:19:03 +01:00
SSL,256,INVALID_COMPRESSION_LIST
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,159,INVALID_MESSAGE
Build up TLS 1.3 record-layer tests. This also adds a missing check to the C half to ensure fake record types are always correct, to keep implementations honest. Change-Id: I1d65272e647ffa67018c721d52c639f8ba47d647 Reviewed-on: https://boringssl-review.googlesource.com/8510 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-06-25 03:56:37 +01:00
SSL,251,INVALID_OUTER_RECORD_TYPE
Don't allow invalid SCT lists to be set. This change causes SSL_CTX_set_signed_cert_timestamp_list to check the SCT list for shallow validity before allowing it to be set. Change-Id: Ib8a1fe185224ff02ed4ce53a0109e60d934e96b3 Reviewed-on: https://boringssl-review.googlesource.com/12401 Commit-Queue: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: David Benjamin <davidben@google.com>
2016-11-18 22:21:03 +00:00
SSL,269,INVALID_SCT_LIST
Support OpenSSL APIs SSL[_CTX]_set1_sigalgs[_list]. These functions can be used to configure the signature algorithms. One of them is a string mini-languaging parsing function, which we generally dislike because it defeats static analysis. However, some dependent projects (in this case TensorFlow) need it and we also dislike making people patch. Change-Id: I13f990c896a7f7332d78b1c351357d418ade8d11 Reviewed-on: https://boringssl-review.googlesource.com/30304 Reviewed-by: Steven Valdez <svaldez@google.com>
2018-08-03 18:31:21 +01:00
SSL,295,INVALID_SIGNATURE_ALGORITHM
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,160,INVALID_SSL_SESSION
SSL,161,INVALID_TICKET_KEYS_LENGTH
SSL,162,LENGTH_MISMATCH
SSL,164,MISSING_EXTENSION
Add TLS 1.3 1-RTT. This adds the machinery for doing TLS 1.3 1RTT. Change-Id: I736921ffe9dc6f6e64a08a836df6bb166d20f504 Reviewed-on: https://boringssl-review.googlesource.com/8720 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-07-11 18:19:03 +01:00
SSL,258,MISSING_KEY_SHARE
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,165,MISSING_RSA_CERTIFICATE
SSL,166,MISSING_TMP_DH_KEY
SSL,167,MISSING_TMP_ECDH_KEY
SSL,168,MIXED_SPECIAL_OPERATOR_WITH_GROUPS
SSL,169,MTU_TOO_SMALL
SSL,170,NEGOTIATED_BOTH_NPN_AND_ALPN
Implement Token Binding Update-Note: Token Binding can no longer be configured with the custom extensions API. Instead, use the new built-in implementation. (The internal repository should be all set.) Bug: 183 Change-Id: I007523a638dc99582ebd1d177c38619fa7e1ac38 Reviewed-on: https://boringssl-review.googlesource.com/20645 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: David Benjamin <davidben@google.com>
2017-09-21 23:02:22 +01:00
SSL,285,NEGOTIATED_TB_WITHOUT_EMS_OR_RI
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,171,NESTED_GROUP
SSL,172,NO_CERTIFICATES_RETURNED
SSL,173,NO_CERTIFICATE_ASSIGNED
SSL,174,NO_CERTIFICATE_SET
SSL,175,NO_CIPHERS_AVAILABLE
SSL,176,NO_CIPHERS_PASSED
Declare SSL_R_BLOCK_CIPHER_PAD_IS_WRONG and SSL_R_NO_CIPHERS_SPECIFIED. nginx consumes these error codes without #ifdefs. Continue to define them for compatibility, even though we never emit them. BUG=95 Change-Id: I1e991987ce25fc4952cc85b98ffa050a8beab92e Reviewed-on: https://boringssl-review.googlesource.com/10446 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-08-17 20:54:36 +01:00
SSL,262,NO_CIPHERS_SPECIFIED
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,177,NO_CIPHER_MATCH
Refine SHA-1 default in signature algorithm negotiation. Rather than blindly select SHA-1 if we can't find a matching one, act as if the peer advertised rsa_pkcs1_sha1 and ecdsa_sha1. This means that we will fail the handshake if no common algorithm may be found. This is done in preparation for removing the SHA-1 default in TLS 1.3. Change-Id: I3584947909d3d6988b940f9404044cace265b20d Reviewed-on: https://boringssl-review.googlesource.com/8695 Reviewed-by: David Benjamin <davidben@google.com>
2016-07-08 23:52:59 +01:00
SSL,253,NO_COMMON_SIGNATURE_ALGORITHMS
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,178,NO_COMPRESSION_SPECIFIED
Only predict X25519 in TLS 1.3. We'd previously been assuming we'd want to predict P-256 and X25519 but, on reflection, that's nonsense. Although, today, P-256 is widespread and X25519 is less so, that's not the right question to ask. Those servers are all 1.2. The right question is whether we believe enough servers will get to TLS 1.3 before X25519 to justify wasting 64 bytes on all other connections. Given that OpenSSL has already shipped X25519 and Microsoft was doing interop testing on X25519 around when we were shipping it, I think the answer is no. Moreover, if we are wrong, it will be easier to go from predicting one group to two rather than the inverse (provided we send a fake one with GREASE). I anticipate prediction-miss HelloRetryRequest logic across the TLS/TCP ecosystem will be largely untested (no one wants to pay an RTT), so taking a group out of the predicted set will likely be a risky operation. Only predicting one group also makes things a bit simpler. I haven't done this here, but we'll be able to fold the 1.2 and 1.3 ecdh_ctx's together, even. Change-Id: Ie7e42d3105aca48eb9d97e2e05a16c5379aa66a3 Reviewed-on: https://boringssl-review.googlesource.com/10960 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-09-09 04:47:48 +01:00
SSL,265,NO_GROUPS_SPECIFIED
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,179,NO_METHOD_SPECIFIED
SSL,180,NO_P256_SUPPORT
SSL,181,NO_PRIVATE_KEY_ASSIGNED
SSL,182,NO_RENEGOTIATION
SSL,183,NO_REQUIRED_DIGEST
SSL,184,NO_SHARED_CIPHER
Update crypto negotation to draft 15. BUG=77 Change-Id: If568412655aae240b072c29d763a5b17bb5ca3f7 Reviewed-on: https://boringssl-review.googlesource.com/10840 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Commit-Queue: David Benjamin <davidben@google.com>
2016-09-06 19:13:43 +01:00
SSL,266,NO_SHARED_GROUP
Disable SSLv3 by default. As a precursor to removing the code entirely later, disable the protocol by default. Callers must use SSL_CTX_set_min_version to enable it. This change also makes SSLv3_method *not* enable SSL 3.0. Normally version-specific methods set the minimum and maximum version to their version. SSLv3_method leaves the minimum at the default, so we will treat it as all versions disabled. To help debugging, the error code is switched from WRONG_SSL_VERSION to a new NO_SUPPORTED_VERSIONS_ENABLED. This also defines OPENSSL_NO_SSL3 and OPENSSL_NO_SSL3_METHOD to kick in any no-ssl3 build paths in consumers which should provide a convenient hook for any upstreaming changes that may be needed. (OPENSSL_NO_SSL3 existed in older versions of OpenSSL, so in principle one may encounter an OpenSSL with the same settings.) Change-Id: I96a8f2f568eb77b2537b3a774b2f7108bd67dd0c Reviewed-on: https://boringssl-review.googlesource.com/14031 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-03-01 21:48:38 +00:00
SSL,280,NO_SUPPORTED_VERSIONS_ENABLED
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,185,NULL_SSL_CTX
SSL,186,NULL_SSL_METHOD_PASSED
Implement legacy OCSP APIs for libssl. Previously, we'd omitted OpenSSL's OCSP APIs because they depend on a complex OCSP mechanism and encourage the the unreliable server behavior that hampers using OCSP stapling to fix revocation today. (OCSP responses should not be fetched on-demand on a callback. They should be managed like other server credentials and refreshed eagerly, so temporary CA outage does not translate to loss of OCSP.) But most of the APIs are byte-oriented anyway, so they're easy to support. Intentionally omit the one that takes a bunch of OCSP_RESPIDs. The callback is benign on the client (an artifact of OpenSSL reading OCSP and verifying certificates in the wrong order). On the server, it encourages unreliability, but pyOpenSSL/cryptography.io depends on this. Dcument that this is only for compatibility with legacy software. Also tweak a few things for compatilibility. cryptography.io expects SSL_CTX_set_read_ahead to return something, SSL_get_server_tmp_key's signature was wrong, and cryptography.io tries to redefine SSL_get_server_tmp_key if SSL_CTRL_GET_SERVER_TMP_KEY is missing. Change-Id: I2f99711783456bfb7324e9ad972510be8a95e845 Reviewed-on: https://boringssl-review.googlesource.com/28404 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2018-05-11 00:55:02 +01:00
SSL,289,OCSP_CB_ERROR
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,187,OLD_SESSION_CIPHER_NOT_RETURNED
Tolerate cipher changes on TLS 1.3 resumption as a client. As a client, we must tolerate this to avoid interoperability failures with allowed server behaviors. BUG=117 Change-Id: I9c40a2a048282e2e63ab5ee1d40773fc2eda110a Reviewed-on: https://boringssl-review.googlesource.com/12311 Reviewed-by: David Benjamin <davidben@google.com>
2016-11-16 07:25:58 +00:00
SSL,268,OLD_SESSION_PRF_HASH_MISMATCH
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,188,OLD_SESSION_VERSION_NOT_RETURNED
SSL,189,OUTPUT_ALIASES_INPUT
SSL,190,PARSE_TLSEXT
SSL,191,PATH_TOO_LONG
SSL,192,PEER_DID_NOT_RETURN_A_CERTIFICATE
SSL,193,PEER_ERROR_UNSUPPORTED_CERTIFICATE_TYPE
Update to TLS 1.3 draft 18. This is the squash of the following CLs: https://boringssl-review.googlesource.com/c/12021/9 https://boringssl-review.googlesource.com/c/12022/9 https://boringssl-review.googlesource.com/c/12107/19 https://boringssl-review.googlesource.com/c/12141/22 https://boringssl-review.googlesource.com/c/12181/33 The Go portions were written by Nick Harper BUG=112 Change-Id: I375a1fcead493ec3e0282e231ccc8d7c4dde5063 Reviewed-on: https://boringssl-review.googlesource.com/12300 CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com>
2016-11-01 17:39:36 +00:00
SSL,267,PRE_SHARED_KEY_MUST_BE_LAST
Push an error if custom private keys fail. The private key callback may not push one of its own (it's possible to register a custom error library and whatnot, but this is tedious). If the callback does not push any, we report SSL_ERROR_SYSCALL. This is not completely wrong, as "syscall" really means "I don't know, something you gave me, probably the BIO, failed so I assume you know what happened", but most callers just check errno. And indeed cert_cb pushes its own error, so this probably should as well. Update-Note: Custom private key callbacks which push an error code on failure will report both that error followed by SSL_R_PRIVATE_KEY_OPERATION_FAILED. Callbacks which did not push any error will switch from SSL_ERROR_SYSCALL to SSL_ERROR_SSL with SSL_R_PRIVATE_KEY_OPERATION_FAILED. Change-Id: I7e90cd327fe0cbcff395470381a3591364a82c74 Reviewed-on: https://boringssl-review.googlesource.com/25544 Reviewed-by: Adam Langley <agl@google.com>
2018-02-01 20:07:30 +00:00
SSL,287,PRIVATE_KEY_OPERATION_FAILED
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,194,PROTOCOL_IS_SHUTDOWN
Parse the entire PSK extension. Although we ignore all but the first identity, keep clients honest by parsing the whole thing. Also explicitly check that the binder and identity counts match. Change-Id: Ib9c4caae18398360f3b80f8db1b22d4549bd5746 Reviewed-on: https://boringssl-review.googlesource.com/12469 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-12-01 21:47:56 +00:00
SSL,271,PSK_IDENTITY_BINDER_COUNT_MISMATCH
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,195,PSK_IDENTITY_NOT_FOUND
SSL,196,PSK_NO_CLIENT_CB
SSL,197,PSK_NO_SERVER_CB
SSL,198,READ_TIMEOUT_EXPIRED
SSL,199,RECORD_LENGTH_MISMATCH
SSL,200,RECORD_TOO_LARGE
Forbid EMS from changing during renegotation. Changing parameters on renegotiation makes all our APIs confusing. This one has no reason to change, so lock it down. In particular, our preference to forbid Token Binding + renego may be overridden at the IETF, even though it's insane. Loosening it will be a bit less of a headache if EMS can't change. https://www.ietf.org/mail-archive/web/unbearable/current/msg00690.html claims that this is already in the specification and enforced by NSS. I can't find anything to this effect in the specification. It just says the client MUST disable renegotiation when EMS is missing, which is wishful thinking. At a glance, NSS doesn't seem to check, though I could be misunderstanding the code. Nonetheless, locking this down is a good idea anyway. Accurate or not, take the email as an implicit endorsement of this from Mozilla. Change-Id: I236b05991d28bed199763dcf2f47bbfb9d0322d7 Reviewed-on: https://boringssl-review.googlesource.com/10721 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-08-30 04:14:17 +01:00
SSL,263,RENEGOTIATION_EMS_MISMATCH
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,201,RENEGOTIATION_ENCODING_ERR
SSL,202,RENEGOTIATION_MISMATCH
SSL,203,REQUIRED_CIPHER_MISSING
SSL,204,RESUMED_EMS_SESSION_WITHOUT_EMS_EXTENSION
SSL,205,RESUMED_NON_EMS_SESSION_WITH_EMS_EXTENSION
SSL,206,SCSV_RECEIVED_WHEN_RENEGOTIATING
Enforce supported_versions in the second ServerHello. We forgot to do this in our original implementation on general ecosystem grounds. It's also mandated starting draft-26. Just to avoid unnecessary turbulence, since draft-23 is doomed to die anyway, condition this on our draft-28 implementation. (We don't support 24 through 27.) We'd actually checked this already on the Go side, but the spec wants a different alert. Change-Id: I0014cda03d7129df0b48de077e45f8ae9fd16976 Reviewed-on: https://boringssl-review.googlesource.com/28124 Commit-Queue: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Steven Valdez <svaldez@google.com>
2018-05-05 03:00:33 +01:00
SSL,288,SECOND_SERVERHELLO_VERSION_MISMATCH
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,207,SERVERHELLO_TLSEXT
Forbid the server certificate from changing on renego. This allows us to move the code from Chrome into BoringSSL itself. BUG=126 Change-Id: I04b4f63008a6de0a58dd6c685c78e9edd06deda6 Reviewed-on: https://boringssl-review.googlesource.com/14028 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-03-01 01:54:28 +00:00
SSL,273,SERVER_CERT_CHANGED
Notice earlier if a server echoes the TLS 1.3 compatibility session ID. Mono's legacy TLS 1.0 stack, as a server, does not implement any form of resumption, but blindly echos the ClientHello session ID in the ServerHello for no particularly good reason. This is invalid, but due to quirks of how our client checked session ID equality, we only noticed on the second connection, rather than the first. Flaky failures do no one any good, so break deterministically on the first connection, when we realize something strange is going on. Bug: chromium:796910 Change-Id: I1f255e915fcdffeafb80be481f6c0acb3c628846 Reviewed-on: https://boringssl-review.googlesource.com/25424 Commit-Queue: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Steven Valdez <svaldez@google.com>
2018-01-26 21:33:12 +00:00
SSL,286,SERVER_ECHOED_INVALID_SESSION_ID
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,208,SESSION_ID_CONTEXT_UNINITIALIZED
SSL,209,SESSION_MAY_NOT_BE_CREATED
Handle SSL_shutdown while in init more appropriately Calling SSL_shutdown while in init previously gave a "1" response, meaning everything was successfully closed down (even though it wasn't). Better is to send our close_notify, but fail when trying to receive one. The problem with doing a shutdown while in the middle of a handshake is that once our close_notify is sent we shouldn't really do anything else (including process handshake/CCS messages) until we've received a close_notify back from the peer. However the peer might send a CCS before acting on our close_notify - so we won't be able to read it because we're not acting on CCS messages! (Imported from upstream's f73c737c7ac908c5d6407c419769123392a3b0a9) Change-Id: Iaad5c5e38983456d3697c955522a89919628024b Reviewed-on: https://boringssl-review.googlesource.com/7207 Reviewed-by: David Benjamin <davidben@google.com>
2016-02-24 15:47:52 +00:00
SSL,250,SHUTDOWN_WHILE_IN_INIT
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,210,SIGNATURE_ALGORITHMS_EXTENSION_SENT_BY_SERVER
SSL,211,SRTP_COULD_NOT_ALLOCATE_PROFILES
SSL,212,SRTP_UNKNOWN_PROTECTION_PROFILE
SSL,213,SSL3_EXT_INVALID_SERVERNAME
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
SSL,1042,SSLV3_ALERT_BAD_CERTIFICATE
SSL,1020,SSLV3_ALERT_BAD_RECORD_MAC
SSL,1045,SSLV3_ALERT_CERTIFICATE_EXPIRED
SSL,1044,SSLV3_ALERT_CERTIFICATE_REVOKED
SSL,1046,SSLV3_ALERT_CERTIFICATE_UNKNOWN
SSL,1000,SSLV3_ALERT_CLOSE_NOTIFY
SSL,1030,SSLV3_ALERT_DECOMPRESSION_FAILURE
SSL,1040,SSLV3_ALERT_HANDSHAKE_FAILURE
SSL,1047,SSLV3_ALERT_ILLEGAL_PARAMETER
SSL,1041,SSLV3_ALERT_NO_CERTIFICATE
SSL,1010,SSLV3_ALERT_UNEXPECTED_MESSAGE
SSL,1043,SSLV3_ALERT_UNSUPPORTED_CERTIFICATE
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,214,SSL_CTX_HAS_NO_DEFAULT_SSL_VERSION
SSL,215,SSL_HANDSHAKE_FAILURE
SSL,216,SSL_SESSION_ID_CONTEXT_TOO_LONG
Add SSL_SESSION_set1_id. This matches the OpenSSL 1.1.0 spelling. I'd thought we could hide SSL_SESSION this pass, but I missed one test that messed with session IDs! Bug: 6 Change-Id: I84ea113353eb0eaa2b06b68dec71cb9061c047ca Reviewed-on: https://boringssl-review.googlesource.com/28866 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2018-06-03 21:25:55 +01:00
SSL,290,SSL_SESSION_ID_TOO_LONG
Support asynchronous ticket decryption with TLS 1.0–1.2. This change adds support for setting an |SSL_TICKET_AEAD_METHOD| which allows a caller to control ticket encryption and decryption to a greater extent than previously possible and also permits asynchronous ticket decryption. This change only includes partial support: TLS 1.3 work remains to be done. Change-Id: Ia2e10ebb3257e1a119630c463b6bf389cf20ef18 Reviewed-on: https://boringssl-review.googlesource.com/14144 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com>
2017-03-09 03:33:21 +00:00
SSL,276,TICKET_ENCRYPTION_FAILED
Fix error strings for SSL_R_TLS13_DOWNGRADE. make_errors.go didn't seem to get run. Change-Id: I12739fbab75b9f4898f73f206e404d101642b9c0 Reviewed-on: https://boringssl-review.googlesource.com/31184 Reviewed-by: Adam Langley <agl@google.com>
2018-08-22 01:51:17 +01:00
SSL,297,TLS13_DOWNGRADE
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
SSL,1049,TLSV1_ALERT_ACCESS_DENIED
SSL,1050,TLSV1_ALERT_DECODE_ERROR
SSL,1021,TLSV1_ALERT_DECRYPTION_FAILED
SSL,1051,TLSV1_ALERT_DECRYPT_ERROR
SSL,1060,TLSV1_ALERT_EXPORT_RESTRICTION
SSL,1086,TLSV1_ALERT_INAPPROPRIATE_FALLBACK
SSL,1071,TLSV1_ALERT_INSUFFICIENT_SECURITY
SSL,1080,TLSV1_ALERT_INTERNAL_ERROR
SSL,1100,TLSV1_ALERT_NO_RENEGOTIATION
SSL,1070,TLSV1_ALERT_PROTOCOL_VERSION
SSL,1022,TLSV1_ALERT_RECORD_OVERFLOW
SSL,1048,TLSV1_ALERT_UNKNOWN_CA
SSL,1090,TLSV1_ALERT_USER_CANCELLED
SSL,1114,TLSV1_BAD_CERTIFICATE_HASH_VALUE
SSL,1113,TLSV1_BAD_CERTIFICATE_STATUS_RESPONSE
Add the certificate_required alert. This is part of TLS 1.3 draft 16 but isn't much of a wire format change, so go ahead and add it now. When rolling into Chromium, we'll want to add an entry to the error mapping. Change-Id: I8fd7f461dca83b725a31ae19ef96c890d603ce53 Reviewed-on: https://boringssl-review.googlesource.com/11563 Reviewed-by: David Benjamin <davidben@google.com>
2016-10-08 01:51:43 +01:00
SSL,1116,TLSV1_CERTIFICATE_REQUIRED
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
SSL,1111,TLSV1_CERTIFICATE_UNOBTAINABLE
Add the certificate_required alert. This is part of TLS 1.3 draft 16 but isn't much of a wire format change, so go ahead and add it now. When rolling into Chromium, we'll want to add an entry to the error mapping. Change-Id: I8fd7f461dca83b725a31ae19ef96c890d603ce53 Reviewed-on: https://boringssl-review.googlesource.com/11563 Reviewed-by: David Benjamin <davidben@google.com>
2016-10-08 01:51:43 +01:00
SSL,1115,TLSV1_UNKNOWN_PSK_IDENTITY
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
SSL,1112,TLSV1_UNRECOGNIZED_NAME
SSL,1110,TLSV1_UNSUPPORTED_EXTENSION
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,217,TLS_PEER_DID_NOT_RESPOND_WITH_CERTIFICATE_LIST
SSL,218,TLS_RSA_ENCRYPTED_VALUE_LENGTH_IS_WRONG
SSL,219,TOO_MANY_EMPTY_FRAGMENTS
Add limit for consecutive KeyUpdate messages. Change-Id: I2e1ee319bb9852b9c686f2f297c470db54f72279 Reviewed-on: https://boringssl-review.googlesource.com/10370 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-08-16 16:25:03 +01:00
SSL,260,TOO_MANY_KEY_UPDATES
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,220,TOO_MANY_WARNING_ALERTS
Detect WatchGuard's TLS 1.3 interference failure mode. WatchGuard's bug is very distinctive. Report a dedicated error code out of BoringSSL so we can better track this. Bug: chromium:733223 Change-Id: Ia42abd8654e7987b1d43c63a4f454f35f6aa873b Reviewed-on: https://boringssl-review.googlesource.com/17328 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-06-22 20:03:18 +01:00
SSL,1117,TOO_MUCH_READ_EARLY_DATA
Skipping early data on 0RTT rejection. BUG=101 Change-Id: Ia1edbccee535b0bc3a0e18465286d5bcca240035 Reviewed-on: https://boringssl-review.googlesource.com/12470 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-11-29 18:36:45 +00:00
SSL,270,TOO_MUCH_SKIPPED_EARLY_DATA
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,221,UNABLE_TO_FIND_ECDH_PARAMETERS
Implement the client side of certificate compression. Change-Id: I0aced480af98276ebfe0970b4afb9aa957ee07cb Reviewed-on: https://boringssl-review.googlesource.com/29024 Reviewed-by: Adam Langley <agl@google.com>
2018-06-08 00:39:49 +01:00
SSL,293,UNCOMPRESSED_CERT_TOO_LARGE
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,222,UNEXPECTED_EXTENSION
Prevent both early data and custom extensions from being accepted. This loosens the earlier restriction to match Channel ID. Both may be configured and offered, but the server is obligated to select only one of them. This aligns with the current tokbind + 0-RTT draft where the combination is signaled by a separate extension. Bug: 183 Change-Id: I786102a679999705d399f0091f76da236be091c2 Reviewed-on: https://boringssl-review.googlesource.com/19124 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: Steven Valdez <svaldez@google.com>
2017-08-10 19:02:56 +01:00
SSL,279,UNEXPECTED_EXTENSION_ON_EARLY_DATA
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,223,UNEXPECTED_MESSAGE
SSL,224,UNEXPECTED_OPERATOR_IN_GROUP
SSL,225,UNEXPECTED_RECORD
SSL,226,UNINITIALIZED
SSL,227,UNKNOWN_ALERT_TYPE
SSL,228,UNKNOWN_CERTIFICATE_TYPE
Implement the client side of certificate compression. Change-Id: I0aced480af98276ebfe0970b4afb9aa957ee07cb Reviewed-on: https://boringssl-review.googlesource.com/29024 Reviewed-by: Adam Langley <agl@google.com>
2018-06-08 00:39:49 +01:00
SSL,294,UNKNOWN_CERT_COMPRESSION_ALG
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,229,UNKNOWN_CIPHER_RETURNED
SSL,230,UNKNOWN_CIPHER_TYPE
SSL,231,UNKNOWN_DIGEST
SSL,232,UNKNOWN_KEY_EXCHANGE_TYPE
SSL,233,UNKNOWN_PROTOCOL
SSL,234,UNKNOWN_SSL_VERSION
SSL,235,UNKNOWN_STATE
SSL,236,UNSAFE_LEGACY_RENEGOTIATION_DISABLED
SSL,237,UNSUPPORTED_CIPHER
SSL,238,UNSUPPORTED_COMPRESSION_ALGORITHM
SSL,239,UNSUPPORTED_ELLIPTIC_CURVE
SSL,240,UNSUPPORTED_PROTOCOL
Move the Digest/Sign split for SignatureAlgorithms to a lower level. In order to delay the digest of the handshake transcript and unify around message-based signing callbacks, a copy of the transcript is kept around until we are sure there is no certificate authentication. This removes support for SSL_PRIVATE_KEY_METHOD as a client in SSL 3.0. Change-Id: If8999a19ca021b4ff439319ab91e2cd2103caa64 Reviewed-on: https://boringssl-review.googlesource.com/8561 Reviewed-by: David Benjamin <davidben@google.com>
2016-06-30 18:27:23 +01:00
SSL,252,UNSUPPORTED_PROTOCOL_FOR_CUSTOM_KEY
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,241,WRONG_CERTIFICATE_TYPE
SSL,242,WRONG_CIPHER_RETURNED
SSL,243,WRONG_CURVE
SSL,244,WRONG_MESSAGE_TYPE
SSL,245,WRONG_SIGNATURE_TYPE
SSL,246,WRONG_SSL_VERSION
SSL,247,WRONG_VERSION_NUMBER
Add Data-less Zero-RTT support. This adds support on the server and client to accept data-less early data. The server will still fail to parse early data with any contents, so this should remain disabled. BUG=76 Change-Id: Id85d192d8e0360b8de4b6971511b5e8a0e8012f7 Reviewed-on: https://boringssl-review.googlesource.com/12921 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-01-11 16:34:52 +00:00
SSL,278,WRONG_VERSION_ON_EARLY_DATA
Reset ssl error codes. 38 error codes have fallen off the list since the last time we did this. Change-Id: Id7ee30889a5da2f6ab66957fd8e49e97640c8489 Reviewed-on: https://boringssl-review.googlesource.com/6643 Reviewed-by: Adam Langley <agl@google.com>
2015-12-06 18:37:52 +00:00
SSL,248,X509_LIB
SSL,249,X509_VERIFICATION_SETUP_PROBLEMS
Reference in New Issue Copy Permalink