2014-06-20 20:00:00 +01:00
|
|
|
/* 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.]
|
|
|
|
*/
|
|
|
|
/* ====================================================================
|
|
|
|
* Copyright (c) 1998-2002 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). */
|
|
|
|
|
2015-09-15 06:48:04 +01:00
|
|
|
#include <openssl/ssl.h>
|
|
|
|
|
2014-06-20 20:00:00 +01:00
|
|
|
#include <assert.h>
|
2014-06-20 20:00:00 +01:00
|
|
|
#include <limits.h>
|
2015-04-08 04:05:04 +01:00
|
|
|
#include <string.h>
|
2014-06-20 20:00:00 +01:00
|
|
|
|
|
|
|
#include <openssl/buf.h>
|
|
|
|
#include <openssl/err.h>
|
|
|
|
#include <openssl/evp.h>
|
|
|
|
#include <openssl/mem.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-06-20 20:00:00 +01:00
|
|
|
|
2014-12-19 01:42:32 +00:00
|
|
|
|
Support symbol prefixes
- In base.h, if BORINGSSL_PREFIX is defined, include
boringssl_prefix_symbols.h
- In all .S files, if BORINGSSL_PREFIX is defined, include
boringssl_prefix_symbols_asm.h
- In base.h, BSSL_NAMESPACE_BEGIN and BSSL_NAMESPACE_END are
defined with appropriate values depending on whether
BORINGSSL_PREFIX is defined; these macros are used in place
of 'namespace bssl {' and '}'
- Add util/make_prefix_headers.go, which takes a list of symbols
and auto-generates the header files mentioned above
- In CMakeLists.txt, if BORINGSSL_PREFIX and BORINGSSL_PREFIX_SYMBOLS
are defined, run util/make_prefix_headers.go to generate header
files
- In various CMakeLists.txt files, add "global_target" that all
targets depend on to give us a place to hook logic that must run
before all other targets (in particular, the header file generation
logic)
- Document this in BUILDING.md, including the fact that it is
the caller's responsibility to provide the symbol list and keep it
up to date
- Note that this scheme has not been tested on Windows, and likely
does not work on it; Windows support will need to be added in a
future commit
Change-Id: If66a7157f46b5b66230ef91e15826b910cf979a2
Reviewed-on: https://boringssl-review.googlesource.com/31364
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>
2018-08-27 02:53:36 +01:00
|
|
|
BSSL_NAMESPACE_BEGIN
|
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
|
|
|
|
2017-10-13 21:50:39 +01:00
|
|
|
static int do_ssl3_write(SSL *ssl, int type, const uint8_t *in, unsigned len);
|
2014-06-20 20:00:00 +01:00
|
|
|
|
2017-10-13 21:50:39 +01:00
|
|
|
int ssl3_write_app_data(SSL *ssl, bool *out_needs_handshake, const uint8_t *in,
|
2017-03-09 19:56:07 +00:00
|
|
|
int len) {
|
2016-12-19 18:19:29 +00:00
|
|
|
assert(ssl_can_write(ssl));
|
2017-07-19 03:45:18 +01:00
|
|
|
assert(!ssl->s3->aead_write_ctx->is_null_cipher());
|
2016-03-10 05:41:25 +00:00
|
|
|
|
2017-08-31 20:13:12 +01:00
|
|
|
*out_needs_handshake = false;
|
2017-03-09 19:56:07 +00:00
|
|
|
|
2017-10-12 23:09:20 +01:00
|
|
|
if (ssl->s3->write_shutdown != ssl_shutdown_none) {
|
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_PROTOCOL_IS_SHUTDOWN);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2016-03-10 06:41:55 +00:00
|
|
|
unsigned tot, n, nw;
|
2014-12-19 01:42:32 +00:00
|
|
|
|
2015-12-19 22:05:56 +00:00
|
|
|
assert(ssl->s3->wnum <= INT_MAX);
|
|
|
|
tot = ssl->s3->wnum;
|
|
|
|
ssl->s3->wnum = 0;
|
2014-12-19 01:42:32 +00:00
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// Ensure that if we end up with a smaller value of data to write out than
|
|
|
|
// the the original len from a write which didn't complete for non-blocking
|
|
|
|
// I/O and also somehow ended up avoiding the check for this in
|
|
|
|
// ssl3_write_pending/SSL_R_BAD_WRITE_RETRY as it must never be possible to
|
|
|
|
// end up with (len-tot) as a large number that will then promptly send
|
|
|
|
// beyond the end of the users buffer ... so we trap and report the error in
|
|
|
|
// a way the user will notice.
|
2014-12-19 01:42:32 +00:00
|
|
|
if (len < 0 || (size_t)len < tot) {
|
2015-06-29 05:28:17 +01:00
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_BAD_LENGTH);
|
2014-12-19 01:42:32 +00:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2017-03-09 19:56:07 +00:00
|
|
|
const int is_early_data_write =
|
|
|
|
!ssl->server && SSL_in_early_data(ssl) && ssl->s3->hs->can_early_write;
|
|
|
|
|
2017-02-02 20:05:35 +00:00
|
|
|
n = len - tot;
|
2014-12-19 01:42:32 +00:00
|
|
|
for (;;) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// max contains the maximum number of bytes that we can put into a record.
|
2015-12-19 22:05:56 +00:00
|
|
|
unsigned max = ssl->max_send_fragment;
|
2018-07-14 16:23:01 +01:00
|
|
|
if (is_early_data_write &&
|
|
|
|
max > ssl->session->ticket_max_early_data -
|
|
|
|
ssl->s3->hs->early_data_written) {
|
|
|
|
max =
|
|
|
|
ssl->session->ticket_max_early_data - ssl->s3->hs->early_data_written;
|
2017-03-09 19:56:07 +00:00
|
|
|
if (max == 0) {
|
|
|
|
ssl->s3->wnum = tot;
|
2017-08-31 19:49:09 +01:00
|
|
|
ssl->s3->hs->can_early_write = false;
|
2017-08-31 20:13:12 +01:00
|
|
|
*out_needs_handshake = true;
|
2017-03-09 19:56:07 +00:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-12-19 01:42:32 +00:00
|
|
|
if (n > max) {
|
|
|
|
nw = max;
|
|
|
|
} else {
|
|
|
|
nw = n;
|
|
|
|
}
|
|
|
|
|
2017-10-13 21:50:39 +01:00
|
|
|
int ret = do_ssl3_write(ssl, SSL3_RT_APPLICATION_DATA, &in[tot], nw);
|
2016-03-10 06:41:55 +00:00
|
|
|
if (ret <= 0) {
|
2015-12-19 22:05:56 +00:00
|
|
|
ssl->s3->wnum = tot;
|
2016-03-10 06:41:55 +00:00
|
|
|
return ret;
|
2014-12-19 01:42:32 +00:00
|
|
|
}
|
|
|
|
|
2017-03-09 19:56:07 +00:00
|
|
|
if (is_early_data_write) {
|
|
|
|
ssl->s3->hs->early_data_written += ret;
|
|
|
|
}
|
|
|
|
|
2017-02-02 20:05:35 +00:00
|
|
|
if (ret == (int)n || (ssl->mode & SSL_MODE_ENABLE_PARTIAL_WRITE)) {
|
2016-03-10 06:41:55 +00:00
|
|
|
return tot + ret;
|
2014-12-19 01:42:32 +00:00
|
|
|
}
|
|
|
|
|
2016-03-10 06:41:55 +00:00
|
|
|
n -= ret;
|
|
|
|
tot += ret;
|
2014-12-19 01:42:32 +00:00
|
|
|
}
|
|
|
|
}
|
2014-06-20 20:00:00 +01:00
|
|
|
|
2017-10-13 21:50:39 +01:00
|
|
|
static int ssl3_write_pending(SSL *ssl, int type, const uint8_t *in,
|
2015-11-02 22:50:10 +00:00
|
|
|
unsigned int len) {
|
2015-12-19 22:05:56 +00:00
|
|
|
if (ssl->s3->wpend_tot > (int)len ||
|
2016-10-25 01:13:20 +01:00
|
|
|
(!(ssl->mode & SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER) &&
|
2017-10-13 21:50:39 +01:00
|
|
|
ssl->s3->wpend_buf != in) ||
|
2015-12-19 22:05:56 +00:00
|
|
|
ssl->s3->wpend_type != type) {
|
2015-11-02 22:50:10 +00:00
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_BAD_WRITE_RETRY);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
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;
|
|
|
|
}
|
2017-08-31 20:06:42 +01:00
|
|
|
ssl->s3->wpend_pending = false;
|
2015-12-19 22:05:56 +00:00
|
|
|
return ssl->s3->wpend_ret;
|
2015-11-02 22:50:10 +00:00
|
|
|
}
|
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// do_ssl3_write writes an SSL record of the given type.
|
2017-10-13 21:50:39 +01:00
|
|
|
static int do_ssl3_write(SSL *ssl, int type, const uint8_t *in, unsigned len) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// If there is still data from the previous record, flush it.
|
2017-03-09 19:56:07 +00:00
|
|
|
if (ssl->s3->wpend_pending) {
|
2017-10-13 21:50:39 +01:00
|
|
|
return ssl3_write_pending(ssl, type, in, len);
|
2014-12-19 01:42:32 +00:00
|
|
|
}
|
|
|
|
|
2017-10-13 21:50:39 +01:00
|
|
|
SSLBuffer *buf = &ssl->s3->write_buffer;
|
|
|
|
if (len > SSL3_RT_MAX_PLAIN_LENGTH || buf->size() > 0) {
|
2015-07-29 02:34:45 +01:00
|
|
|
OPENSSL_PUT_ERROR(SSL, ERR_R_INTERNAL_ERROR);
|
2014-12-19 01:42:32 +00:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2018-05-24 22:17:34 +01:00
|
|
|
if (!tls_flush_pending_hs_data(ssl)) {
|
|
|
|
return -1;
|
|
|
|
}
|
2018-12-17 21:59:38 +00:00
|
|
|
|
2017-04-06 17:54:12 +01:00
|
|
|
size_t flight_len = 0;
|
2017-10-13 22:18:35 +01:00
|
|
|
if (ssl->s3->pending_flight != nullptr) {
|
2017-04-06 17:54:12 +01:00
|
|
|
flight_len =
|
|
|
|
ssl->s3->pending_flight->length - ssl->s3->pending_flight_offset;
|
|
|
|
}
|
|
|
|
|
2018-12-17 21:59:38 +00:00
|
|
|
size_t max_out = flight_len;
|
|
|
|
if (len > 0) {
|
|
|
|
const size_t max_ciphertext_len = len + SSL_max_seal_overhead(ssl);
|
|
|
|
if (max_ciphertext_len < len || max_out + max_ciphertext_len < max_out) {
|
|
|
|
OPENSSL_PUT_ERROR(SSL, ERR_R_OVERFLOW);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
max_out += max_ciphertext_len;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (max_out == 0) {
|
|
|
|
return 0;
|
2014-12-19 01:42:32 +00:00
|
|
|
}
|
2017-04-06 17:54:12 +01:00
|
|
|
|
2017-10-13 21:50:39 +01:00
|
|
|
if (!buf->EnsureCap(flight_len + ssl_seal_align_prefix_len(ssl), max_out)) {
|
2017-04-06 17:54:12 +01:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// Add any unflushed handshake data as a prefix. This may be a KeyUpdate
|
|
|
|
// acknowledgment or 0-RTT key change messages. |pending_flight| must be clear
|
|
|
|
// when data is added to |write_buffer| or it will be written in the wrong
|
|
|
|
// order.
|
2017-10-13 22:18:35 +01:00
|
|
|
if (ssl->s3->pending_flight != nullptr) {
|
2017-04-06 17:54:12 +01:00
|
|
|
OPENSSL_memcpy(
|
2017-10-13 21:50:39 +01:00
|
|
|
buf->remaining().data(),
|
|
|
|
ssl->s3->pending_flight->data + ssl->s3->pending_flight_offset,
|
2017-04-06 17:54:12 +01:00
|
|
|
flight_len);
|
2017-10-13 22:18:35 +01:00
|
|
|
ssl->s3->pending_flight.reset();
|
2017-04-06 17:54:12 +01:00
|
|
|
ssl->s3->pending_flight_offset = 0;
|
2017-10-13 21:50:39 +01:00
|
|
|
buf->DidWrite(flight_len);
|
2017-04-06 17:54:12 +01:00
|
|
|
}
|
|
|
|
|
2018-12-17 21:59:38 +00:00
|
|
|
if (len > 0) {
|
|
|
|
size_t ciphertext_len;
|
|
|
|
if (!tls_seal_record(ssl, buf->remaining().data(), &ciphertext_len,
|
|
|
|
buf->remaining().size(), type, in, len)) {
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
buf->DidWrite(ciphertext_len);
|
2014-12-19 01:42:32 +00:00
|
|
|
}
|
2017-04-06 17:54:12 +01:00
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// Now that we've made progress on the connection, uncork KeyUpdate
|
|
|
|
// acknowledgments.
|
2017-08-31 20:06:42 +01:00
|
|
|
ssl->s3->key_update_pending = false;
|
2014-12-19 01:42:32 +00:00
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// Memorize arguments so that ssl3_write_pending can detect bad write retries
|
|
|
|
// later.
|
2015-12-19 22:05:56 +00:00
|
|
|
ssl->s3->wpend_tot = len;
|
2017-10-13 21:50:39 +01:00
|
|
|
ssl->s3->wpend_buf = in;
|
2015-12-19 22:05:56 +00:00
|
|
|
ssl->s3->wpend_type = type;
|
|
|
|
ssl->s3->wpend_ret = len;
|
2017-08-31 20:06:42 +01:00
|
|
|
ssl->s3->wpend_pending = true;
|
2014-12-19 01:42:32 +00:00
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// We now just need to write the buffer.
|
2017-10-13 21:50:39 +01:00
|
|
|
return ssl3_write_pending(ssl, type, in, len);
|
2014-12-19 01:42:32 +00:00
|
|
|
}
|
2014-06-20 20:00:00 +01:00
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
ssl_open_record_t ssl3_open_app_data(SSL *ssl, Span<uint8_t> *out,
|
|
|
|
size_t *out_consumed, uint8_t *out_alert,
|
|
|
|
Span<uint8_t> in) {
|
|
|
|
assert(ssl_can_read(ssl));
|
|
|
|
assert(!ssl->s3->aead_read_ctx->is_null_cipher());
|
2016-07-28 16:05:58 +01:00
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
uint8_t type;
|
|
|
|
Span<uint8_t> body;
|
|
|
|
auto ret = tls_open_record(ssl, &type, &body, out_consumed, out_alert, in);
|
|
|
|
if (ret != ssl_open_record_success) {
|
|
|
|
return ret;
|
2016-07-28 16:05:58 +01:00
|
|
|
}
|
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
const bool is_early_data_read = ssl->server && SSL_in_early_data(ssl);
|
2016-07-28 16:05:58 +01:00
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
if (type == SSL3_RT_HANDSHAKE) {
|
|
|
|
// Post-handshake data prior to TLS 1.3 is always renegotiation, which we
|
|
|
|
// never accept as a server. Otherwise |ssl3_get_message| will send
|
|
|
|
// |SSL_R_EXCESSIVE_MESSAGE_SIZE|.
|
|
|
|
if (ssl->server && ssl_protocol_version(ssl) < TLS1_3_VERSION) {
|
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_NO_RENEGOTIATION);
|
|
|
|
*out_alert = SSL_AD_NO_RENEGOTIATION;
|
|
|
|
return ssl_open_record_error;
|
2016-07-28 16:05:58 +01:00
|
|
|
}
|
|
|
|
|
2018-11-02 23:31:17 +00:00
|
|
|
if (!tls_append_handshake_data(ssl, body)) {
|
2017-10-06 22:36:20 +01:00
|
|
|
*out_alert = SSL_AD_INTERNAL_ERROR;
|
|
|
|
return ssl_open_record_error;
|
2016-12-19 18:19:29 +00:00
|
|
|
}
|
2017-10-06 22:36:20 +01:00
|
|
|
return ssl_open_record_discard;
|
|
|
|
}
|
2016-12-19 18:19:29 +00:00
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
if (type != SSL3_RT_APPLICATION_DATA) {
|
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_UNEXPECTED_RECORD);
|
|
|
|
*out_alert = SSL_AD_UNEXPECTED_MESSAGE;
|
|
|
|
return ssl_open_record_error;
|
|
|
|
}
|
2017-04-17 19:12:33 +01:00
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
if (is_early_data_read) {
|
|
|
|
if (body.size() > kMaxEarlyDataAccepted - ssl->s3->hs->early_data_read) {
|
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_TOO_MUCH_READ_EARLY_DATA);
|
|
|
|
*out_alert = SSL3_AD_UNEXPECTED_MESSAGE;
|
|
|
|
return ssl_open_record_error;
|
2017-04-17 19:12:33 +01:00
|
|
|
}
|
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
ssl->s3->hs->early_data_read += body.size();
|
|
|
|
}
|
2016-07-28 16:05:58 +01:00
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
if (body.empty()) {
|
|
|
|
return ssl_open_record_discard;
|
2016-07-28 16:05:58 +01:00
|
|
|
}
|
2017-10-06 22:36:20 +01:00
|
|
|
|
|
|
|
*out = body;
|
|
|
|
return ssl_open_record_success;
|
2015-11-26 07:16:49 +00:00
|
|
|
}
|
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
ssl_open_record_t ssl3_open_change_cipher_spec(SSL *ssl, size_t *out_consumed,
|
|
|
|
uint8_t *out_alert,
|
|
|
|
Span<uint8_t> in) {
|
|
|
|
uint8_t type;
|
|
|
|
Span<uint8_t> body;
|
|
|
|
auto ret = tls_open_record(ssl, &type, &body, out_consumed, out_alert, in);
|
|
|
|
if (ret != ssl_open_record_success) {
|
|
|
|
return ret;
|
2014-12-19 01:42:32 +00:00
|
|
|
}
|
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
if (type != SSL3_RT_CHANGE_CIPHER_SPEC) {
|
2016-05-11 01:46:16 +01:00
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_UNEXPECTED_RECORD);
|
2017-10-06 22:36:20 +01:00
|
|
|
*out_alert = SSL_AD_UNEXPECTED_MESSAGE;
|
|
|
|
return ssl_open_record_error;
|
2016-05-11 01:46:16 +01:00
|
|
|
}
|
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
if (body.size() != 1 || body[0] != SSL3_MT_CCS) {
|
2015-11-26 07:16:49 +00:00
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_BAD_CHANGE_CIPHER_SPEC);
|
2017-10-06 22:36:20 +01:00
|
|
|
*out_alert = SSL_AD_ILLEGAL_PARAMETER;
|
|
|
|
return ssl_open_record_error;
|
2015-11-26 07:16:49 +00:00
|
|
|
}
|
2014-07-21 21:14:03 +01:00
|
|
|
|
2017-10-06 22:36:20 +01:00
|
|
|
ssl_do_msg_callback(ssl, 0 /* read */, SSL3_RT_CHANGE_CIPHER_SPEC, body);
|
|
|
|
return ssl_open_record_success;
|
2015-05-30 21:22:10 +01:00
|
|
|
}
|
|
|
|
|
2017-10-06 23:31:15 +01:00
|
|
|
int ssl_send_alert(SSL *ssl, int level, int desc) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// It is illegal to send an alert when we've already sent a closing one.
|
2017-10-06 21:02:47 +01:00
|
|
|
if (ssl->s3->write_shutdown != ssl_shutdown_none) {
|
2016-05-10 22:03:10 +01:00
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_PROTOCOL_IS_SHUTDOWN);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2017-01-28 01:51:33 +00:00
|
|
|
if (level == SSL3_AL_WARNING && desc == SSL_AD_CLOSE_NOTIFY) {
|
2017-10-06 21:02:47 +01:00
|
|
|
ssl->s3->write_shutdown = ssl_shutdown_close_notify;
|
2017-01-28 01:51:33 +00:00
|
|
|
} else {
|
|
|
|
assert(level == SSL3_AL_FATAL);
|
2017-09-25 18:37:30 +01:00
|
|
|
assert(desc != SSL_AD_CLOSE_NOTIFY);
|
2017-10-06 21:04:06 +01:00
|
|
|
ssl->s3->write_shutdown = ssl_shutdown_error;
|
2014-12-19 01:42:32 +00:00
|
|
|
}
|
|
|
|
|
2015-12-19 22:05:56 +00:00
|
|
|
ssl->s3->alert_dispatch = 1;
|
|
|
|
ssl->s3->send_alert[0] = level;
|
|
|
|
ssl->s3->send_alert[1] = desc;
|
2017-10-13 21:50:39 +01:00
|
|
|
if (ssl->s3->write_buffer.empty()) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// Nothing is being written out, so the alert may be dispatched
|
|
|
|
// immediately.
|
2016-06-15 22:44:37 +01:00
|
|
|
return ssl->method->dispatch_alert(ssl);
|
2014-12-19 01:42:32 +00:00
|
|
|
}
|
|
|
|
|
2017-08-29 21:33:21 +01:00
|
|
|
// The alert will be dispatched later.
|
2014-12-19 01:42:32 +00:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2015-12-19 22:05:56 +00:00
|
|
|
int ssl3_dispatch_alert(SSL *ssl) {
|
2018-12-13 13:53:57 +00:00
|
|
|
if (ssl->quic_method) {
|
|
|
|
if (!ssl->quic_method->send_alert(ssl, ssl->s3->write_level,
|
|
|
|
ssl->s3->send_alert[1])) {
|
2018-07-14 16:23:01 +01:00
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_QUIC_INTERNAL_ERROR);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
int ret = do_ssl3_write(ssl, SSL3_RT_ALERT, &ssl->s3->send_alert[0], 2);
|
|
|
|
if (ret <= 0) {
|
|
|
|
return ret;
|
|
|
|
}
|
2016-03-10 06:41:55 +00:00
|
|
|
}
|
2018-07-14 16:23:01 +01:00
|
|
|
|
2017-01-28 01:51:33 +00:00
|
|
|
ssl->s3->alert_dispatch = 0;
|
2014-12-19 01:42:32 +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) {
|
2018-07-03 00:47:27 +01:00
|
|
|
BIO_flush(ssl->wbio.get());
|
2016-03-10 06:41:55 +00:00
|
|
|
}
|
2014-12-19 01:42:32 +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-12-19 01:42:32 +00: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-19 01:42:32 +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
|
|
|
|
Support symbol prefixes
- In base.h, if BORINGSSL_PREFIX is defined, include
boringssl_prefix_symbols.h
- In all .S files, if BORINGSSL_PREFIX is defined, include
boringssl_prefix_symbols_asm.h
- In base.h, BSSL_NAMESPACE_BEGIN and BSSL_NAMESPACE_END are
defined with appropriate values depending on whether
BORINGSSL_PREFIX is defined; these macros are used in place
of 'namespace bssl {' and '}'
- Add util/make_prefix_headers.go, which takes a list of symbols
and auto-generates the header files mentioned above
- In CMakeLists.txt, if BORINGSSL_PREFIX and BORINGSSL_PREFIX_SYMBOLS
are defined, run util/make_prefix_headers.go to generate header
files
- In various CMakeLists.txt files, add "global_target" that all
targets depend on to give us a place to hook logic that must run
before all other targets (in particular, the header file generation
logic)
- Document this in BUILDING.md, including the fact that it is
the caller's responsibility to provide the symbol list and keep it
up to date
- Note that this scheme has not been tested on Windows, and likely
does not work on it; Windows support will need to be added in a
future commit
Change-Id: If66a7157f46b5b66230ef91e15826b910cf979a2
Reviewed-on: https://boringssl-review.googlesource.com/31364
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>
2018-08-27 02:53:36 +01:00
|
|
|
BSSL_NAMESPACE_END
|