2014-06-20 20:00:00 +01:00
|
|
|
/* DTLS implementation written by Nagendra Modadugu
|
|
|
|
* (nagendra@cs.stanford.edu) for the OpenSSL project 2005. */
|
|
|
|
/* ====================================================================
|
|
|
|
* Copyright (c) 1998-2005 The OpenSSL Project. All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
*
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
*
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in
|
|
|
|
* the documentation and/or other materials provided with the
|
|
|
|
* distribution.
|
|
|
|
*
|
|
|
|
* 3. All advertising materials mentioning features or use of this
|
|
|
|
* software must display the following acknowledgment:
|
|
|
|
* "This product includes software developed by the OpenSSL Project
|
|
|
|
* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
|
|
|
|
*
|
|
|
|
* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
|
|
|
|
* endorse or promote products derived from this software without
|
|
|
|
* prior written permission. For written permission, please contact
|
|
|
|
* openssl-core@openssl.org.
|
|
|
|
*
|
|
|
|
* 5. Products derived from this software may not be called "OpenSSL"
|
|
|
|
* nor may "OpenSSL" appear in their names without prior written
|
|
|
|
* permission of the OpenSSL Project.
|
|
|
|
*
|
|
|
|
* 6. Redistributions of any form whatsoever must retain the following
|
|
|
|
* acknowledgment:
|
|
|
|
* "This product includes software developed by the OpenSSL Project
|
|
|
|
* for use in the OpenSSL Toolkit (http://www.openssl.org/)"
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
|
|
|
|
* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
|
|
|
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
|
|
|
|
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
|
|
|
|
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
|
|
|
|
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
|
|
|
|
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
|
|
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
|
|
|
|
* OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
* ====================================================================
|
|
|
|
*
|
|
|
|
* This product includes cryptographic software written by Eric Young
|
|
|
|
* (eay@cryptsoft.com). This product includes software written by Tim
|
|
|
|
* Hudson (tjh@cryptsoft.com).
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
|
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* This package is an SSL implementation written
|
|
|
|
* by Eric Young (eay@cryptsoft.com).
|
|
|
|
* The implementation was written so as to conform with Netscapes SSL.
|
|
|
|
*
|
|
|
|
* This library is free for commercial and non-commercial use as long as
|
|
|
|
* the following conditions are aheared to. The following conditions
|
|
|
|
* apply to all code found in this distribution, be it the RC4, RSA,
|
|
|
|
* lhash, DES, etc., code; not just the SSL code. The SSL documentation
|
|
|
|
* included with this distribution is covered by the same copyright terms
|
|
|
|
* except that the holder is Tim Hudson (tjh@cryptsoft.com).
|
|
|
|
*
|
|
|
|
* Copyright remains Eric Young's, and as such any Copyright notices in
|
|
|
|
* the code are not to be removed.
|
|
|
|
* If this package is used in a product, Eric Young should be given attribution
|
|
|
|
* as the author of the parts of the library used.
|
|
|
|
* This can be in the form of a textual message at program startup or
|
|
|
|
* in documentation (online or textual) provided with the package.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
* 3. All advertising materials mentioning features or use of this software
|
|
|
|
* must display the following acknowledgement:
|
|
|
|
* "This product includes cryptographic software written by
|
|
|
|
* Eric Young (eay@cryptsoft.com)"
|
|
|
|
* The word 'cryptographic' can be left out if the rouines from the library
|
|
|
|
* being used are not cryptographic related :-).
|
|
|
|
* 4. If you include any Windows specific code (or a derivative thereof) from
|
|
|
|
* the apps directory (application code) you must include an acknowledgement:
|
|
|
|
* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
*
|
|
|
|
* The licence and distribution terms for any publically available version or
|
|
|
|
* derivative of this code cannot be changed. i.e. this code cannot simply be
|
|
|
|
* copied and put under another distribution licence
|
|
|
|
* [including the GNU Public Licence.] */
|
|
|
|
|
2015-09-15 06:48:04 +01:00
|
|
|
#include <openssl/ssl.h>
|
|
|
|
|
2014-06-20 20:00:00 +01:00
|
|
|
#include <assert.h>
|
2015-04-08 04:05:04 +01:00
|
|
|
#include <string.h>
|
2014-06-20 20:00:00 +01:00
|
|
|
|
2016-05-11 01:51:34 +01:00
|
|
|
#include <openssl/bio.h>
|
2014-06-20 20:00:00 +01:00
|
|
|
#include <openssl/buf.h>
|
2016-06-02 21:38:35 +01:00
|
|
|
#include <openssl/bytestring.h>
|
2014-06-20 20:00:00 +01:00
|
|
|
#include <openssl/mem.h>
|
|
|
|
#include <openssl/evp.h>
|
|
|
|
#include <openssl/err.h>
|
|
|
|
#include <openssl/rand.h>
|
|
|
|
|
2016-12-13 06:07:13 +00:00
|
|
|
#include "../crypto/internal.h"
|
2015-04-08 03:38:30 +01:00
|
|
|
#include "internal.h"
|
2014-12-14 00:28:18 +00:00
|
|
|
|
|
|
|
|
Move libssl's internals into the bssl namespace.
This is horrible, but everything else I tried was worse. The goal with
this CL is to take the extern "C" out of ssl/internal.h and move most
symbols to namespace bssl, so we can start using C++ helpers and
destructors without worry.
Complications:
- Public API functions must be extern "C" and match their declaration in
ssl.h, which is unnamespaced. C++ really does not want you to
interleave namespaced and unnamespaced things. One can actually write
a namespaced extern "C" function, but this means, from C++'s
perspective, the function is namespaced. Trying to namespace the
public header would worked but ended up too deep a rabbithole.
- Our STACK_OF macros do not work right in namespaces.
- The typedefs for our exposed but opaque types are visible in the
header files and copied into consuming projects as forward
declarations. We ultimately want to give SSL a destructor, but
clobbering an unnamespaced ssl_st::~ssl_st seems bad manners.
- MSVC complains about ambiguous names if one typedefs SSL to bssl::SSL.
This CL opts for:
- ssl/*.cc must begin with #define BORINGSSL_INTERNAL_CXX_TYPES. This
informs the public headers to create forward declarations which are
compatible with our namespaces.
- For now, C++-defined type FOO ends up at bssl::FOO with a typedef
outside. Later I imagine we'll rename many of them.
- Internal functions get namespace bssl, so we stop worrying about
stomping the tls1_prf symbol. Exported C functions are stuck as they
are. Rather than try anything weird, bite the bullet and reorder files
which have a mix of public and private functions. I expect that over
time, the public functions will become fairly small as we move logic
to more idiomatic C++.
Files without any public C functions can just be written normally.
- To avoid MSVC troubles, some bssl types are renamed to CPlusPlusStyle
in advance of them being made idiomatic C++.
Bug: 132
Change-Id: Ic931895e117c38b14ff8d6e5a273e868796c7581
Reviewed-on: https://boringssl-review.googlesource.com/18124
Reviewed-by: David Benjamin <davidben@google.com>
2017-07-18 21:34:25 +01:00
|
|
|
namespace bssl {
|
|
|
|
|
2016-06-02 21:38:35 +01:00
|
|
|
int dtls1_get_record(SSL *ssl) {
|
2014-06-20 20:00:00 +01:00
|
|
|
again:
|
2017-10-06 21:02:47 +01:00
|
|
|
switch (ssl->s3->read_shutdown) {
|
2016-05-10 22:03:10 +01:00
|
|
|
case ssl_shutdown_none:
|
|
|
|
break;
|
|
|
|
case ssl_shutdown_fatal_alert:
|
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_PROTOCOL_IS_SHUTDOWN);
|
|
|
|
return -1;
|
|
|
|
case ssl_shutdown_close_notify:
|
2016-03-10 06:15:15 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// Read a new packet if there is no unconsumed one.
|
2017-10-04 23:14:28 +01:00
|
|
|
if (ssl_read_buffer(ssl).empty()) {
|
2016-06-02 20:42:01 +01:00
|
|
|
int read_ret = ssl_read_buffer_extend_to(ssl, 0 /* unused */);
|
|
|
|
if (read_ret < 0 && dtls1_is_timer_expired(ssl)) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// Historically, timeouts were handled implicitly if the caller did not
|
|
|
|
// handle them.
|
|
|
|
//
|
|
|
|
// TODO(davidben): This was to support blocking sockets but affected
|
|
|
|
// non-blocking sockets. Can it be removed?
|
2016-05-11 01:51:34 +01:00
|
|
|
int timeout_ret = DTLSv1_handle_timeout(ssl);
|
|
|
|
if (timeout_ret <= 0) {
|
|
|
|
return timeout_ret;
|
|
|
|
}
|
|
|
|
goto again;
|
|
|
|
}
|
2016-06-02 20:42:01 +01:00
|
|
|
if (read_ret <= 0) {
|
|
|
|
return read_ret;
|
2014-12-14 00:28:18 +00:00
|
|
|
}
|
|
|
|
}
|
2017-10-04 23:14:28 +01:00
|
|
|
assert(!ssl_read_buffer(ssl).empty());
|
2014-12-14 00:28:18 +00:00
|
|
|
|
2017-10-04 23:14:28 +01:00
|
|
|
Span<uint8_t> body;
|
2015-07-29 02:34:45 +01:00
|
|
|
uint8_t type, alert;
|
2016-06-06 23:54:51 +01:00
|
|
|
size_t consumed;
|
2017-10-04 23:14:28 +01:00
|
|
|
enum ssl_open_record_t open_ret = dtls_open_record(
|
|
|
|
ssl, &type, &body, &consumed, &alert, ssl_read_buffer(ssl));
|
2016-06-02 20:42:01 +01:00
|
|
|
ssl_read_buffer_consume(ssl, consumed);
|
|
|
|
switch (open_ret) {
|
|
|
|
case ssl_open_record_partial:
|
2017-08-29 21:33:21 +01:00
|
|
|
// Impossible in DTLS.
|
2016-06-02 20:42:01 +01:00
|
|
|
break;
|
2015-07-29 02:34:45 +01:00
|
|
|
|
2017-07-09 21:17:55 +01:00
|
|
|
case ssl_open_record_success: {
|
2017-10-04 23:14:28 +01:00
|
|
|
if (body.size() > 0xffff) {
|
2015-07-29 02:34:45 +01:00
|
|
|
OPENSSL_PUT_ERROR(SSL, ERR_R_OVERFLOW);
|
|
|
|
return -1;
|
|
|
|
}
|
2015-07-25 20:22:17 +01:00
|
|
|
|
2015-07-29 02:34:45 +01:00
|
|
|
SSL3_RECORD *rr = &ssl->s3->rrec;
|
|
|
|
rr->type = type;
|
2017-10-04 23:14:28 +01:00
|
|
|
rr->length = static_cast<uint16_t>(body.size());
|
|
|
|
rr->data = body.data();
|
2015-07-29 02:34:45 +01:00
|
|
|
return 1;
|
2017-07-09 21:17:55 +01:00
|
|
|
}
|
2015-07-25 20:22:17 +01:00
|
|
|
|
2015-07-29 02:34:45 +01:00
|
|
|
case ssl_open_record_discard:
|
|
|
|
goto again;
|
2015-07-25 20:22:17 +01:00
|
|
|
|
2016-06-02 20:42:01 +01:00
|
|
|
case ssl_open_record_close_notify:
|
|
|
|
return 0;
|
|
|
|
|
2015-07-29 02:34:45 +01:00
|
|
|
case ssl_open_record_error:
|
2017-09-25 18:37:30 +01:00
|
|
|
if (alert != 0) {
|
|
|
|
ssl3_send_alert(ssl, SSL3_AL_FATAL, alert);
|
|
|
|
}
|
2015-07-29 02:34:45 +01:00
|
|
|
return -1;
|
2015-07-25 20:22:17 +01:00
|
|
|
}
|
|
|
|
|
2015-07-29 02:34:45 +01:00
|
|
|
assert(0);
|
|
|
|
OPENSSL_PUT_ERROR(SSL, ERR_R_INTERNAL_ERROR);
|
|
|
|
return -1;
|
2014-12-14 00:28:18 +00:00
|
|
|
}
|
2014-06-20 20:00:00 +01:00
|
|
|
|
2017-08-31 20:13:12 +01:00
|
|
|
int dtls1_read_app_data(SSL *ssl, bool *out_got_handshake, uint8_t *buf,
|
|
|
|
int len, int peek) {
|
2016-03-10 06:28:00 +00:00
|
|
|
assert(!SSL_in_init(ssl));
|
2016-06-02 01:49:50 +01:00
|
|
|
|
2017-08-31 20:13:12 +01:00
|
|
|
*out_got_handshake = false;
|
2016-06-02 01:49:50 +01:00
|
|
|
SSL3_RECORD *rr = &ssl->s3->rrec;
|
|
|
|
|
|
|
|
again:
|
|
|
|
if (rr->length == 0) {
|
|
|
|
int ret = dtls1_get_record(ssl);
|
|
|
|
if (ret <= 0) {
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (rr->type == SSL3_RT_HANDSHAKE) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// Parse the first fragment header to determine if this is a pre-CCS or
|
|
|
|
// post-CCS handshake record. DTLS resets handshake message numbers on each
|
|
|
|
// handshake, so renegotiations and retransmissions are ambiguous.
|
2016-06-02 01:49:50 +01:00
|
|
|
CBS cbs, body;
|
|
|
|
struct hm_header_st msg_hdr;
|
|
|
|
CBS_init(&cbs, rr->data, rr->length);
|
|
|
|
if (!dtls1_parse_fragment(&cbs, &msg_hdr, &body)) {
|
|
|
|
ssl3_send_alert(ssl, SSL3_AL_FATAL, SSL_AD_DECODE_ERROR);
|
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_BAD_HANDSHAKE_RECORD);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2016-07-27 22:40:37 +01:00
|
|
|
if (msg_hdr.type == SSL3_MT_FINISHED &&
|
2016-07-27 22:51:49 +01:00
|
|
|
msg_hdr.seq == ssl->d1->handshake_read_seq - 1) {
|
2016-06-02 01:49:50 +01:00
|
|
|
if (msg_hdr.frag_off == 0) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// Retransmit our last flight of messages. If the peer sends the second
|
|
|
|
// Finished, they may not have received ours. Only do this for the
|
|
|
|
// first fragment, in case the Finished was fragmented.
|
2017-08-03 00:46:29 +01:00
|
|
|
if (!dtls1_check_timeout_num(ssl)) {
|
2016-06-02 01:49:50 +01:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2016-06-23 22:49:12 +01:00
|
|
|
dtls1_retransmit_outgoing_messages(ssl);
|
2016-06-02 01:49:50 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
rr->length = 0;
|
|
|
|
goto again;
|
|
|
|
}
|
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// Otherwise, this is a pre-CCS handshake message from an unsupported
|
|
|
|
// renegotiation attempt. Fall through to the error path.
|
2016-06-02 01:49:50 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
if (rr->type != SSL3_RT_APPLICATION_DATA) {
|
|
|
|
ssl3_send_alert(ssl, SSL3_AL_FATAL, SSL_AD_UNEXPECTED_MESSAGE);
|
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_UNEXPECTED_RECORD);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// Discard empty records.
|
2016-06-02 01:49:50 +01:00
|
|
|
if (rr->length == 0) {
|
|
|
|
goto again;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (len <= 0) {
|
|
|
|
return len;
|
|
|
|
}
|
|
|
|
|
|
|
|
if ((unsigned)len > rr->length) {
|
|
|
|
len = rr->length;
|
|
|
|
}
|
|
|
|
|
2016-12-13 06:07:13 +00:00
|
|
|
OPENSSL_memcpy(buf, rr->data, len);
|
2016-06-02 01:49:50 +01:00
|
|
|
if (!peek) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// TODO(davidben): Should the record be truncated instead? This is a
|
|
|
|
// datagram transport. See https://crbug.com/boringssl/65.
|
2016-06-02 01:49:50 +01:00
|
|
|
rr->length -= len;
|
|
|
|
rr->data += len;
|
|
|
|
if (rr->length == 0) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// The record has been consumed, so we may now clear the buffer.
|
2016-06-02 01:49:50 +01:00
|
|
|
ssl_read_buffer_discard(ssl);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return len;
|
2015-05-30 21:22:10 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
void dtls1_read_close_notify(SSL *ssl) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// Bidirectional shutdown doesn't make sense for an unordered transport. DTLS
|
|
|
|
// alerts also aren't delivered reliably, so we may even time out because the
|
|
|
|
// peer never received our close_notify. Report to the caller that the channel
|
|
|
|
// has fully shut down.
|
2017-10-06 21:02:47 +01:00
|
|
|
if (ssl->s3->read_shutdown == ssl_shutdown_none) {
|
|
|
|
ssl->s3->read_shutdown = ssl_shutdown_close_notify;
|
2016-05-10 22:03:10 +01:00
|
|
|
}
|
2015-05-30 21:22:10 +01:00
|
|
|
}
|
|
|
|
|
2017-08-31 20:13:12 +01:00
|
|
|
int dtls1_write_app_data(SSL *ssl, bool *out_needs_handshake,
|
|
|
|
const uint8_t *buf, int len) {
|
2016-03-10 05:41:25 +00:00
|
|
|
assert(!SSL_in_init(ssl));
|
2017-08-31 20:13:12 +01:00
|
|
|
*out_needs_handshake = false;
|
2014-12-14 00:28:18 +00:00
|
|
|
|
|
|
|
if (len > SSL3_RT_MAX_PLAIN_LENGTH) {
|
2015-06-29 05:28:17 +01:00
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_DTLS_MESSAGE_TOO_BIG);
|
2014-12-14 00:28:18 +00:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2016-06-07 20:20:49 +01:00
|
|
|
if (len < 0) {
|
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_BAD_LENGTH);
|
|
|
|
return -1;
|
|
|
|
}
|
2014-12-14 00:28:18 +00:00
|
|
|
|
2016-06-07 20:20:49 +01:00
|
|
|
if (len == 0) {
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2017-02-02 20:05:35 +00:00
|
|
|
int ret = dtls1_write_record(ssl, SSL3_RT_APPLICATION_DATA, buf, (size_t)len,
|
2016-06-07 20:20:49 +01:00
|
|
|
dtls1_use_current_epoch);
|
|
|
|
if (ret <= 0) {
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
return len;
|
2014-12-14 00:28:18 +00:00
|
|
|
}
|
|
|
|
|
2016-06-07 20:20:49 +01:00
|
|
|
int dtls1_write_record(SSL *ssl, int type, const uint8_t *buf, size_t len,
|
|
|
|
enum dtls1_use_epoch_t use_epoch) {
|
|
|
|
assert(len <= SSL3_RT_MAX_PLAIN_LENGTH);
|
2017-08-29 21:33:21 +01:00
|
|
|
// There should never be a pending write buffer in DTLS. One can't write half
|
|
|
|
// a datagram, so the write buffer is always dropped in
|
|
|
|
// |ssl_write_buffer_flush|.
|
2015-12-19 22:05:56 +00:00
|
|
|
assert(!ssl_write_buffer_is_pending(ssl));
|
2014-12-14 00:28:18 +00:00
|
|
|
|
2015-07-29 02:34:45 +01:00
|
|
|
if (len > SSL3_RT_MAX_PLAIN_LENGTH) {
|
|
|
|
OPENSSL_PUT_ERROR(SSL, ERR_R_INTERNAL_ERROR);
|
2015-03-03 19:20:26 +00:00
|
|
|
return -1;
|
|
|
|
}
|
2014-12-14 00:28:18 +00:00
|
|
|
|
2016-11-04 19:44:28 +00:00
|
|
|
size_t max_out = len + SSL_max_seal_overhead(ssl);
|
2015-07-29 02:34:45 +01:00
|
|
|
uint8_t *out;
|
2015-03-03 19:20:26 +00:00
|
|
|
size_t ciphertext_len;
|
2015-12-19 22:05:56 +00:00
|
|
|
if (!ssl_write_buffer_init(ssl, &out, max_out) ||
|
|
|
|
!dtls_seal_record(ssl, out, &ciphertext_len, max_out, type, buf, len,
|
2015-07-29 02:34:45 +01:00
|
|
|
use_epoch)) {
|
2015-12-19 22:05:56 +00:00
|
|
|
ssl_write_buffer_clear(ssl);
|
2015-03-03 19:20:26 +00:00
|
|
|
return -1;
|
2015-04-05 05:21:39 +01:00
|
|
|
}
|
2015-12-19 22:05:56 +00:00
|
|
|
ssl_write_buffer_set_len(ssl, ciphertext_len);
|
2014-12-14 00:28:18 +00:00
|
|
|
|
2015-12-19 22:05:56 +00:00
|
|
|
int ret = ssl_write_buffer_flush(ssl);
|
2015-11-02 22:50:10 +00:00
|
|
|
if (ret <= 0) {
|
|
|
|
return ret;
|
|
|
|
}
|
2016-06-07 20:20:49 +01:00
|
|
|
return 1;
|
2014-12-14 00:28:18 +00:00
|
|
|
}
|
2014-06-20 20:00:00 +01:00
|
|
|
|
2015-12-19 22:05:56 +00:00
|
|
|
int dtls1_dispatch_alert(SSL *ssl) {
|
2016-06-07 20:20:49 +01:00
|
|
|
int ret = dtls1_write_record(ssl, SSL3_RT_ALERT, &ssl->s3->send_alert[0], 2,
|
|
|
|
dtls1_use_current_epoch);
|
2016-03-10 06:41:55 +00:00
|
|
|
if (ret <= 0) {
|
|
|
|
return ret;
|
|
|
|
}
|
2017-01-28 01:51:33 +00:00
|
|
|
ssl->s3->alert_dispatch = 0;
|
2014-12-14 00:28:18 +00:00
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// If the alert is fatal, flush the BIO now.
|
2016-03-10 06:41:55 +00:00
|
|
|
if (ssl->s3->send_alert[0] == SSL3_AL_FATAL) {
|
|
|
|
BIO_flush(ssl->wbio);
|
|
|
|
}
|
2014-12-14 00:28:18 +00:00
|
|
|
|
2017-10-04 23:14:28 +01:00
|
|
|
ssl_do_msg_callback(ssl, 1 /* write */, SSL3_RT_ALERT, ssl->s3->send_alert);
|
2014-06-20 20:00:00 +01:00
|
|
|
|
2016-06-02 01:16:03 +01:00
|
|
|
int alert = (ssl->s3->send_alert[0] << 8) | ssl->s3->send_alert[1];
|
|
|
|
ssl_do_info_callback(ssl, SSL_CB_WRITE_ALERT, alert);
|
2016-03-10 06:41:55 +00:00
|
|
|
|
|
|
|
return 1;
|
2014-12-14 00:28:18 +00:00
|
|
|
}
|
Move libssl's internals into the bssl namespace.
This is horrible, but everything else I tried was worse. The goal with
this CL is to take the extern "C" out of ssl/internal.h and move most
symbols to namespace bssl, so we can start using C++ helpers and
destructors without worry.
Complications:
- Public API functions must be extern "C" and match their declaration in
ssl.h, which is unnamespaced. C++ really does not want you to
interleave namespaced and unnamespaced things. One can actually write
a namespaced extern "C" function, but this means, from C++'s
perspective, the function is namespaced. Trying to namespace the
public header would worked but ended up too deep a rabbithole.
- Our STACK_OF macros do not work right in namespaces.
- The typedefs for our exposed but opaque types are visible in the
header files and copied into consuming projects as forward
declarations. We ultimately want to give SSL a destructor, but
clobbering an unnamespaced ssl_st::~ssl_st seems bad manners.
- MSVC complains about ambiguous names if one typedefs SSL to bssl::SSL.
This CL opts for:
- ssl/*.cc must begin with #define BORINGSSL_INTERNAL_CXX_TYPES. This
informs the public headers to create forward declarations which are
compatible with our namespaces.
- For now, C++-defined type FOO ends up at bssl::FOO with a typedef
outside. Later I imagine we'll rename many of them.
- Internal functions get namespace bssl, so we stop worrying about
stomping the tls1_prf symbol. Exported C functions are stuck as they
are. Rather than try anything weird, bite the bullet and reorder files
which have a mix of public and private functions. I expect that over
time, the public functions will become fairly small as we move logic
to more idiomatic C++.
Files without any public C functions can just be written normally.
- To avoid MSVC troubles, some bssl types are renamed to CPlusPlusStyle
in advance of them being made idiomatic C++.
Bug: 132
Change-Id: Ic931895e117c38b14ff8d6e5a273e868796c7581
Reviewed-on: https://boringssl-review.googlesource.com/18124
Reviewed-by: David Benjamin <davidben@google.com>
2017-07-18 21:34:25 +01:00
|
|
|
|
|
|
|
} // namespace bssl
|