diff options
author | David Benjamin <davidben@google.com> | 2018-09-14 17:17:36 -0700 |
---|---|---|
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | 2018-09-15 00:55:02 +0000 |
commit | d1673c2191034a65b38c5553a19572f26b122703 (patch) | |
tree | 64a1712b72e0e79198d9859ca3d6f74f606ca932 /ssl/d1_both.cc | |
parent | 3f18c4c5b78610d14022a9cd64131ddc984b514b (diff) | |
download | boringssl-d1673c2191034a65b38c5553a19572f26b122703.zip boringssl-d1673c2191034a65b38c5553a19572f26b122703.tar.gz boringssl-d1673c2191034a65b38c5553a19572f26b122703.tar.bz2 |
Remove the add_alert hook.
This was added to support the no_certificate warning alert in SSLv3. That has
since been removed. In the long run, I would like for ssl_send_alert to go
through a flow similar to add_alert so the BIO-free APIs work right and avoid a
host of strangeness surrounding wpend_buf. For now, remove the unused hook.
Change-Id: I1995028b8af4ffa836028794e6b33b2cd1b2435b
Reviewed-on: https://boringssl-review.googlesource.com/31984
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>
Diffstat (limited to 'ssl/d1_both.cc')
-rw-r--r-- | ssl/d1_both.cc | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/ssl/d1_both.cc b/ssl/d1_both.cc index 3f7739e..d82852d 100644 --- a/ssl/d1_both.cc +++ b/ssl/d1_both.cc @@ -601,15 +601,6 @@ bool dtls1_add_change_cipher_spec(SSL *ssl) { return add_outgoing(ssl, true /* ChangeCipherSpec */, Array<uint8_t>()); } -bool dtls1_add_alert(SSL *ssl, uint8_t level, uint8_t desc) { - // The |add_alert| path is only used for warning alerts for now, which DTLS - // never sends. This will be implemented later once closure alerts are - // converted. - assert(false); - OPENSSL_PUT_ERROR(SSL, ERR_R_INTERNAL_ERROR); - return false; -} - // dtls1_update_mtu updates the current MTU from the BIO, ensuring it is above // the minimum. static void dtls1_update_mtu(SSL *ssl) { |