kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
9113e0996f
boringssl/ssl/test/test_config.h

198 lines
6.6 KiB
C
Raw Normal View History

Move configuration into a dedicated TestConfig struct. This removes some duplicate code in parsing command-line flags and, more importantly, makes configuration available when constructing the SSL_CTX and avoids a number of globals. Change-Id: I26e2d2285b732f855a2c82752bc8e0db480c3b30 Reviewed-on: https://boringssl-review.googlesource.com/1502 Reviewed-by: Adam Langley <agl@google.com>
2014-08-12 00:51:50 +01:00
/* Copyright (c) 2014, Google Inc.
*
* Permission to use, copy, modify, and/or distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and this permission notice appear in all copies.
*
* THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
* WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
* MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
* SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
* OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
* CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. */
#ifndef HEADER_TEST_CONFIG
#define HEADER_TEST_CONFIG
#include <string>
Add SSL_set_signing_algorithm_prefs. This gives us a sigalg-based API for configuring signing algorithms. Change-Id: Ib746a56ebd1061eadd2620cdb140d5171b59bc02 Reviewed-on: https://boringssl-review.googlesource.com/8784 Reviewed-by: Adam Langley <agl@google.com>
2016-07-14 17:51:01 +01:00
#include <vector>
Move configuration into a dedicated TestConfig struct. This removes some duplicate code in parsing command-line flags and, more importantly, makes configuration available when constructing the SSL_CTX and avoids a number of globals. Change-Id: I26e2d2285b732f855a2c82752bc8e0db480c3b30 Reviewed-on: https://boringssl-review.googlesource.com/1502 Reviewed-by: Adam Langley <agl@google.com>
2014-08-12 00:51:50 +01:00
shim: move |TestState| and |TestConfig| to their own files. This makes |TestState| and |TestConfig| accessible outside bssl_shim.cc, as well as the functions SetupCtx() and NewSSL(), which become methods on |TestConfig|. A whole mess of callbacks move in order to support this change. Along the way, some bits of global state are moved (e.g. the global test clock) and made self-initializing. This helps with creating a separate binary to perform split handshakes. Change-Id: I39b00a1819074882353f5f04ed01312916f3cccb Reviewed-on: https://boringssl-review.googlesource.com/29345 Commit-Queue: Matt Braithwaite <mab@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: David Benjamin <davidben@google.com>
2018-06-22 23:53:19 +01:00
#include <openssl/base.h>
#include <openssl/x509.h>
#include "test_state.h"
Move configuration into a dedicated TestConfig struct. This removes some duplicate code in parsing command-line flags and, more importantly, makes configuration available when constructing the SSL_CTX and avoids a number of globals. Change-Id: I26e2d2285b732f855a2c82752bc8e0db480c3b30 Reviewed-on: https://boringssl-review.googlesource.com/1502 Reviewed-by: Adam Langley <agl@google.com>
2014-08-12 00:51:50 +01:00
struct TestConfig {
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
int port = 0;
bool is_server = false;
bool is_dtls = false;
Test resuming renewed sessions. In TLS 1.3 draft 14, due to resumption using a different cipher, this is actually not too hard to mess up. (In fact BoGo didn't quite get it right.) Fortunately, the new cipher suite negotiation in draft 15 should make this reasonable again once we implement it. In the meantime, test it. Change-Id: I2eb948eeaaa051ecacaa9095b66ff149582ea11d Reviewed-on: https://boringssl-review.googlesource.com/10442 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 05:51:00 +01:00
int resume_count = 0;
Update TLS fuzzer format with prepended settings. This allows us to fill in holes in our fuzzer coverage, notably client resumption (and thus early data) and server client certificates. The corpora are not refreshed yet. This will be done in upcoming changes. Also add an option for debugging fuzzers. It's very useful to test it on transcripts and make sure that fuzzer mode successfully makes things compatible. Bug: 104 Change-Id: I02f0be4045d1baf68efc9a4157f573df1429575d Reviewed-on: https://boringssl-review.googlesource.com/17531 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-07-01 00:11:22 +01:00
std::string write_settings;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
bool fallback_scsv = false;
Add SSL_set_signing_algorithm_prefs. This gives us a sigalg-based API for configuring signing algorithms. Change-Id: Ib746a56ebd1061eadd2620cdb140d5171b59bc02 Reviewed-on: https://boringssl-review.googlesource.com/8784 Reviewed-by: Adam Langley <agl@google.com>
2016-07-14 17:51:01 +01:00
std::vector<int> signing_prefs;
Add SSL_CTX_set_verify_algorithm_prefs. When writing tests and BoGo isn't available, it is useful to be able to configure the set of signature algorithms accepted on the verify side. Add an API for this. Change-Id: Ic873189da7f8853e412acd68614df9d9a872a0c8 Reviewed-on: https://boringssl-review.googlesource.com/15125 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>
2017-04-14 22:05:40 +01:00
std::vector<int> verify_prefs;
Add SSL_get0_peer_verify_algorithms. Callers who use SSL_get0_certificate_types today will find an empty list in TLS 1.3, which removed it. To provide feature parity, add an accessor for the signature algorithms list. SSL_get_signature_algorithm_key_type can be used to map it to a key type. "Peer signature algorithms" was already taken in the public API by SSL_get_peer_signature_algorithm to refer to which the peer selected, so I named this matching SSL_CTX_set_verify_algorithm_prefs. Change-Id: I12d411d7350e744ed9f88c610df48e0d9fc13256 Reviewed-on: https://boringssl-review.googlesource.com/29684 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Adam Vartanian <flooey@google.com> Reviewed-by: Steven Valdez <svaldez@google.com>
2018-07-10 22:27:45 +01:00
std::vector<int> expected_peer_verify_prefs;
Move configuration into a dedicated TestConfig struct. This removes some duplicate code in parsing command-line flags and, more importantly, makes configuration available when constructing the SSL_CTX and avoids a number of globals. Change-Id: I26e2d2285b732f855a2c82752bc8e0db480c3b30 Reviewed-on: https://boringssl-review.googlesource.com/1502 Reviewed-by: Adam Langley <agl@google.com>
2014-08-12 00:51:50 +01:00
std::string key_file;
std::string cert_file;
std::string expected_server_name;
std::string expected_certificate_types;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
bool require_any_client_certificate = false;
Move configuration into a dedicated TestConfig struct. This removes some duplicate code in parsing command-line flags and, more importantly, makes configuration available when constructing the SSL_CTX and avoids a number of globals. Change-Id: I26e2d2285b732f855a2c82752bc8e0db480c3b30 Reviewed-on: https://boringssl-review.googlesource.com/1502 Reviewed-by: Adam Langley <agl@google.com>
2014-08-12 00:51:50 +01:00
std::string advertise_npn;
std::string expected_next_proto;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
bool false_start = false;
Move configuration into a dedicated TestConfig struct. This removes some duplicate code in parsing command-line flags and, more importantly, makes configuration available when constructing the SSL_CTX and avoids a number of globals. Change-Id: I26e2d2285b732f855a2c82752bc8e0db480c3b30 Reviewed-on: https://boringssl-review.googlesource.com/1502 Reviewed-by: Adam Langley <agl@google.com>
2014-08-12 00:51:50 +01:00
std::string select_next_proto;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
bool async = false;
bool write_different_record_sizes = false;
bool cbc_record_splitting = false;
bool partial_write = false;
Adding TLS 1.3 constants. Constants representing TLS 1.3 are added to allow for future work to be flagged on TLS1_3_VERSION. To prevent BoringSSL from negotiating the non-existent TLS 1.3 version, it is explicitly disabled using SSL_OP_NO_TLSv1_3. Change-Id: Ie5258a916f4c19ef21646c4073d5b4a7974d6f3f Reviewed-on: https://boringssl-review.googlesource.com/8041 Reviewed-by: Adam Langley <agl@google.com>
2016-05-24 17:31:07 +01:00
bool no_tls13 = false;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
bool no_tls12 = false;
bool no_tls11 = false;
bool no_tls1 = false;
Don't mint TLS 1.3 tickets if SSL_OP_NO_TICKETS is set. Change-Id: I03e05acb024e34beaeaf2f02860da1763e08a093 Reviewed-on: https://boringssl-review.googlesource.com/29844 Reviewed-by: Adam Langley <agl@google.com>
2018-07-18 02:26:05 +01:00
bool no_ticket = false;
Add basic TLS Channel ID tests. Change-Id: I7ccf2b8282dfa8f3985775e8b67edcf3c2949752 Reviewed-on: https://boringssl-review.googlesource.com/1606 Reviewed-by: Adam Langley <agl@google.com>
2014-08-24 06:46:07 +01:00
std::string expected_channel_id;
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
bool enable_channel_id = false;
Add basic TLS Channel ID tests. Change-Id: I7ccf2b8282dfa8f3985775e8b67edcf3c2949752 Reviewed-on: https://boringssl-review.googlesource.com/1606 Reviewed-by: Adam Langley <agl@google.com>
2014-08-24 06:46:07 +01:00
std::string send_channel_id;
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
int expected_token_binding_param = -1;
std::string send_token_binding_params;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
bool shim_writes_first = false;
Improve test coverage for server_name extension. Notably, this would have caught ed8270a55c3845abbc85dfeed358597fef059ea9 (although, apart from staring at code coverage, knowing to set resumeSession on the server test isn't exactly obvious). Perhaps we should systematically set it on all extension server tests; ClientHello extension parsing happens after resumption has been determined and is often sensitive to it. Change-Id: Ie83f294a26881a6a41969e9dbd102d0a93cb68b5 Reviewed-on: https://boringssl-review.googlesource.com/1750 Reviewed-by: Adam Langley <agl@google.com>
2014-09-06 17:45:15 +01:00
std::string host_name;
Add tests for ALPN support. Both as client and as server. Also tests that ALPN causes False Start to kick in. Change-Id: Ib570346f3c511834152cd2df2ef29541946d3ab4 Reviewed-on: https://boringssl-review.googlesource.com/1753 Reviewed-by: Adam Langley <agl@google.com>
2014-09-06 17:58:58 +01:00
std::string advertise_alpn;
std::string expected_alpn;
Adding support for sending early data on the client. BUG=76 Change-Id: If58a73da38e46549fd55f84a9104e2dfebfda43f Reviewed-on: https://boringssl-review.googlesource.com/14164 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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-03-09 19:56:07 +00:00
std::string expected_late_alpn;
Add tests for ALPN support. Both as client and as server. Also tests that ALPN causes False Start to kick in. Change-Id: Ib570346f3c511834152cd2df2ef29541946d3ab4 Reviewed-on: https://boringssl-review.googlesource.com/1753 Reviewed-by: Adam Langley <agl@google.com>
2014-09-06 17:58:58 +01:00
std::string expected_advertised_alpn;
std::string select_alpn;
Add a test that declining ALPN works. Inspired by https://mta.openssl.org/pipermail/openssl-dev/2016-March/006150.html Change-Id: I973b3baf054ed1051002f7bb9941cb1deeb36d78 Reviewed-on: https://boringssl-review.googlesource.com/7504 Reviewed-by: David Benjamin <davidben@google.com>
2016-03-17 21:49:56 +00:00
bool decline_alpn = false;
Reject if the ALPN callback returned an empty protocol. If the callback returns an empty ALPN, we forget we negotiated ALPN at all (bssl::Array does not distinguish null and empty). Empty ALPN protocols are forbidden anyway, so reject these ahead of time. Change-Id: I42f1fc4c843bc865e23fb2a2e5d57424b569ee99 Reviewed-on: https://boringssl-review.googlesource.com/28546 Reviewed-by: Adam Langley <agl@google.com>
2018-05-15 20:06:28 +01:00
bool select_empty_alpn = false;
Add support for QUIC transport params. This adds support for sending the quic_transport_parameters (draft-ietf-quic-tls) in ClientHello and EncryptedExtensions, as well as reading the value sent by the peer. Bug: boringssl:224 Change-Id: Ied633f557cb13ac87454d634f2bd81ab156f5399 Reviewed-on: https://boringssl-review.googlesource.com/24464 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-12-22 23:50:43 +00:00
std::string quic_transport_params;
std::string expected_quic_transport_params;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
bool expect_session_miss = false;
bool expect_extended_master_secret = false;
Add tests for PSK cipher suites. Only the three plain PSK suites for now. ECDHE_PSK_WITH_AES_128_GCM_SHA256 will be in a follow-up. Change-Id: Iafc116a5b2798c61d90c139b461cf98897ae23b3 Reviewed-on: https://boringssl-review.googlesource.com/2051 Reviewed-by: Adam Langley <agl@google.com>
2014-10-27 05:06:24 +00:00
std::string psk;
std::string psk_identity;
Add DTLS-SRTP tests. Just the negotiation portion as everything else is external. This feature is used in WebRTC. Change-Id: Iccc3983ea99e7d054b59010182f9a56a8099e116 Reviewed-on: https://boringssl-review.googlesource.com/2310 Reviewed-by: Adam Langley <agl@google.com>
2014-11-16 00:06:08 +00:00
std::string srtp_profiles;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
bool enable_ocsp_stapling = false;
Add tests for OCSP stapling and SCT lists. We forgot to add those when we implemented the features. (Also relevant because they will provide test coverage later for configuring features when using the generic method tables rather than *_client_method.) Change-Id: Ie08b27de893095e01a05a7084775676616459807 Reviewed-on: https://boringssl-review.googlesource.com/2410 Reviewed-by: Adam Langley <agl@google.com>
2014-11-25 06:55:35 +00:00
std::string expected_ocsp_response;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
bool enable_signed_cert_timestamps = false;
Add tests for OCSP stapling and SCT lists. We forgot to add those when we implemented the features. (Also relevant because they will provide test coverage later for configuring features when using the generic method tables rather than *_client_method.) Change-Id: Ie08b27de893095e01a05a7084775676616459807 Reviewed-on: https://boringssl-review.googlesource.com/2410 Reviewed-by: Adam Langley <agl@google.com>
2014-11-25 06:55:35 +00:00
std::string expected_signed_cert_timestamps;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
int min_version = 0;
int max_version = 0;
Fix SSL_version on 0-RTT. Like other handshake properties, when in 0-RTT on the client, SSL_version should report the predicted version. This used to work on accident because of how ssl->version got set in handshake_client.c early (and that TLS 1.4 does not exist), but we no longer do that. Change-Id: Ifb63a22b795fe8964ac553844a46040acd5d7323 Reviewed-on: https://boringssl-review.googlesource.com/17664 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-07-07 18:17:19 +01:00
int expect_version = 0;
Use C++11 inline initialization. Google C++ style allows these. It's also considerably less tedious and error-prone than defining an out-of-line constructor. Change-Id: Ib76ccf6079be383722433046ac5c5d796dd1f525 Reviewed-on: https://boringssl-review.googlesource.com/4111 Reviewed-by: Adam Langley <agl@google.com>
2015-03-23 22:46:05 +00:00
int mtu = 0;
bool implicit_handshake = false;
bool use_early_callback = false;
bool fail_early_callback = false;
bool install_ddos_callback = false;
bool fail_ddos_callback = false;
Add tests for failing cert_cb. We missed that the TLS 1.3 code was inconsistent with the TLS 1.2 code. Only on the server did we push an error code. But consistency between client and server is probably worthwhile so, fix the 1.2 code to match for now. Change-Id: I17952c72048697dc66eacf0f144a66ced9cb3be8 Reviewed-on: https://boringssl-review.googlesource.com/12260 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-14 13:02:50 +00:00
bool fail_cert_callback = false;
Test that client cipher preferences are enforced. Change-Id: I6e760cfd785c0c5688da6f7d3d3092a8add40409 Reviewed-on: https://boringssl-review.googlesource.com/4070 Reviewed-by: Adam Langley <agl@google.com>
2015-03-16 19:16:23 +00:00
std::string cipher;
Test the interaction of SSL_CB_HANDSHAKE_DONE and False Start. Based on whether -false-start is passed, we expect SSL_CB_HANDSHAKE_DONE to or not to fire. Also add a flag that asserts SSL_CB_HANDSHAKE_DONE does *not* fire in any False Start test where the handshake fails after SSL_connect returns. Change-Id: I6c5b960fff15e297531e15b16abe0b98be95bec8 Reviewed-on: https://boringssl-review.googlesource.com/4212 Reviewed-by: Adam Langley <agl@google.com>
2015-04-03 00:57:35 +01:00
bool handshake_never_done = false;
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
int export_early_keying_material = 0;
Add tests for SSL_export_keying_material. Change-Id: Ic4d3ade08aa648ce70ada9981e894b6c1c4197c6 Reviewed-on: https://boringssl-review.googlesource.com/4215 Reviewed-by: Adam Langley <agl@google.com>
2015-04-03 09:06:36 +01:00
int export_keying_material = 0;
std::string export_label;
std::string export_context;
bool use_export_context = false;
Add SSL_get_tls_unique. SSL_get_tls_unique returns the tls-unique channel-binding value as defined in https://tools.ietf.org/html/rfc5929#section-3.1. Change-Id: Id9644328a7db8a91cf3ff0deee9dd6ce0d3e00ba Reviewed-on: https://boringssl-review.googlesource.com/4984 Reviewed-by: Adam Langley <agl@google.com>
2015-06-03 17:57:23 +01:00
bool tls_unique = false;
Don't put sessions from renegotiations in the cache. Rather than rely on Chromium to query SSL_initial_handshake_complete in the callback (which didn't work anyway because the callback is called afterwards), move the logic into BoringSSL. BoringSSL already enforces that clients never offer resumptions on renegotiation (it wouldn't work well anyway as client session cache lookup is external), so it's reasonable to also implement in-library that sessions established on a renegotiation are not cached. Add a bunch of tests that new_session_cb is called when expected. BUG=501418 Change-Id: I42d44c82b043af72b60a0f8fdb57799e20f13ed5 Reviewed-on: https://boringssl-review.googlesource.com/5171 Reviewed-by: Adam Langley <agl@google.com>
2015-06-18 23:36:15 +01:00
bool expect_ticket_renewal = false;
bool expect_no_session = false;
Adding support for draft 21 as a TLS 1.3 variant. Change-Id: I46686aea9b68105cfe70a11db0e88052781e179c Reviewed-on: https://boringssl-review.googlesource.com/22164 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> Reviewed-by: Steven Valdez <svaldez@google.com>
2017-10-11 17:29:36 +01:00
bool expect_ticket_supports_early_data = false;
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
bool expect_accept_early_data = false;
bool expect_reject_early_data = false;
Check early ALPN before offering 0-RTT. We enforce that servers don't send bogus ALPN values, so consumers may assume that SSL_get0_alpn_selected won't have anything terribly weird. To maintain that invariant in the face of folks whose ALPN preferences change (consider a persisted session cache), we should decline to offer 0-RTT if early_alpn would have been rejected by the check anyway. Change-Id: Ic3a9ba4041d5d4618742eb05e27033525d96ade1 Reviewed-on: https://boringssl-review.googlesource.com/22067 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>
2017-10-17 20:48:46 +01:00
bool expect_no_offer_early_data = false;
Add a test for the ticket callback. Change-Id: I7b2a4f617bd8d49c86fdaaf45bf67e0170bbd44f Reviewed-on: https://boringssl-review.googlesource.com/5230 Reviewed-by: Adam Langley <agl@google.com>
2015-06-16 19:16:23 +01:00
bool use_ticket_callback = false;
bool renew_ticket = false;
Enabling 0-RTT on new Session Tickets. This adds support for setting 0-RTT mode on tickets minted by BoringSSL, allowing for testing of the initial handshake knowledge. BUG=76 Change-Id: Ic199842c03b5401ef122a537fdb7ed9e9a5c635a Reviewed-on: https://boringssl-review.googlesource.com/12740 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-07 20:29:45 +00:00
bool enable_early_data = false;
Implement experimental alternate encoding of TLS 1.3. TLS 1.3 deployment is currently blocked by buggy middleboxes throughout the ecosystem. As an experiment to better understand these bugs and the problems they are causing, implement TLS 1.3 variants with alternate encodings. These are still the same protocol, only encoded slightly differently. We will use what we learn from these experiments to guide the TLS 1.3 deployment strategy and proposals to the IETF, if any. These experiments only target the basic 1-RTT TLS 1.3 handshake. Based on what we learn from this experiment, we may try future variations to explore 0-RTT and HelloRetryRequest. When enabled, the server supports all TLS 1.3 variants while the client is configured to use a particular variant. Change-Id: I532411d1abc41314dc76acce0246879b754b4c61 Reviewed-on: https://boringssl-review.googlesource.com/17327 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-06-13 17:45:25 +01:00
int tls13_variant = 0;
Implement custom extensions. This change mirrors upstream's custom extension API because we have some internal users that depend on it. Change-Id: I408e442de0a55df7b05c872c953ff048cd406513 Reviewed-on: https://boringssl-review.googlesource.com/5471 Reviewed-by: Adam Langley <agl@google.com>
2015-07-31 02:10:13 +01:00
bool enable_client_custom_extension = false;
bool enable_server_custom_extension = false;
bool custom_extension_skip = false;
bool custom_extension_fail_add = false;
Server-side OCSP stapling support. This is a simpler implementation than OpenSSL's, lacking responder IDs and request extensions support. This mirrors the client implementation already present. Change-Id: I54592b60e0a708bfb003d491c9250401403c9e69 Reviewed-on: https://boringssl-review.googlesource.com/5700 Reviewed-by: Adam Langley <agl@google.com>
2015-08-12 11:47:11 +01:00
std::string ocsp_response;
Add tests for bidirectional shutdown. Now that it even works at all (type = 0 bug aside), add tests for it. Test both close_notify being received before and after SSL_shutdown is called. In the latter case, have the peer send some junk to be ignored to test that works. Also test that SSL_shutdown fails on unclean shutdown and that quiet shutdowns ignore it. BUG=526437 Change-Id: Iff13b08feb03e82f21ecab0c66d5f85aec256137 Reviewed-on: https://boringssl-review.googlesource.com/5769 Reviewed-by: Adam Langley <agl@google.com>
2015-08-30 03:56:45 +01:00
bool check_close_notify = false;
bool shim_shuts_down = false;
Wait for CertificateStatus message to verify certificate. Applications may require the stapled OCSP response in order to verify the certificate within the verification callback. Change-Id: I8002e527f90c3ce7b6a66e3203c0a68371aac5ec Reviewed-on: https://boringssl-review.googlesource.com/5730 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2015-08-18 12:21:54 +01:00
bool verify_fail = false;
bool verify_peer = false;
Add tests for SSL_VERIFY_PEER_IF_NO_OBC and fix TLS 1.3. Also mirror the structure of the TLS 1.2 and TLS 1.3 code a bit. Change-Id: I7b34bf30de63fa0bd47a39a90570846fb2314ad5 Reviewed-on: https://boringssl-review.googlesource.com/17539 Reviewed-by: David Benjamin <davidben@google.com>
2017-07-01 15:50:56 +01:00
bool verify_peer_if_no_obc = false;
Wait for CertificateStatus message to verify certificate. Applications may require the stapled OCSP response in order to verify the certificate within the verification callback. Change-Id: I8002e527f90c3ce7b6a66e3203c0a68371aac5ec Reviewed-on: https://boringssl-review.googlesource.com/5730 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2015-08-18 12:21:54 +01:00
bool expect_verify_result = false;
Add server-side support for Signed Certificate Timestamps. Change-Id: Ifa44fef160fc9d67771eed165f8fc277f28a0222 Reviewed-on: https://boringssl-review.googlesource.com/5840 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2015-09-09 13:44:55 +01:00
std::string signed_cert_timestamps;
Unbreak SSL_total_renegotiations. The logic to update that got removed in https://boringssl-review.googlesource.com/4825. Add tests. Change-Id: Idc550e8fa3ce6f69a76fa65d7651adde281edba6 Reviewed-on: https://boringssl-review.googlesource.com/6220 Reviewed-by: Matt Braithwaite <mab@google.com> Reviewed-by: Adam Langley <alangley@gmail.com> Reviewed-by: Adam Langley <agl@google.com>
2015-10-13 00:49:00 +01:00
int expect_total_renegotiations = 0;
Add SSL_set_renegotiate_mode. Add a slightly richer API. Notably, one can configure ssl_renegotiate_once to only accept the first renego. Also, this API doesn't repeat the mistake I made with SSL_set_reject_peer_renegotiations which is super-confusing with the negation. Change-Id: I7eb5d534e3e6c553b641793f4677fe5a56451c71 Reviewed-on: https://boringssl-review.googlesource.com/6221 Reviewed-by: Adam Langley <agl@google.com>
2015-10-13 00:54:18 +01:00
bool renegotiate_once = false;
bool renegotiate_freely = false;
Add ssl_renegotiate_ignore. This option causes clients to ignore HelloRequest messages completely. This can be suitable in cases where a server tries to perform concurrent application data and handshake flow, e.g. because they are trying to “renew” symmetric keys. Change-Id: I2779f7eff30d82163f2c34a625ec91dc34fab548 Reviewed-on: https://boringssl-review.googlesource.com/6431 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2015-11-03 21:34:10 +00:00
bool renegotiate_ignore = false;
Allow renego and config shedding to coexist more smoothly. Chrome needs to support renegotiation at TLS 1.2 + HTTP/1.1, but we're free to shed the handshake configuration at TLS 1.3 or HTTP/2. Rather than making config shedding implicitly disable renegotiation, make the actual shedding dependent on a combination of the two settings. If config shedding is enabled, but so is renegotiation (including whether we are a client, etc.), leave the config around. If the renegotiation setting gets disabled again after the handshake, re-evaluate and shed the config then. Bug: 123 Change-Id: Ie833f413b3f15b8f0ede617991e3fef239d4a323 Reviewed-on: https://boringssl-review.googlesource.com/27904 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Matt Braithwaite <mab@google.com>
2018-05-01 22:14:27 +01:00
bool forbid_renegotiation_after_handshake = false;
Change SignatureAndHashAlgorithm to SignatureScheme in Go. TLS 1.3 defines a new SignatureScheme uint16 enum that is backwards compatible on the wire with TLS1.2's SignatureAndHashAlgorithm. This change updates the go testing code to use a single signatureAlgorithm enum (instead of 2 separate signature and hash enums) in preparation for TLS 1.3. It also unifies all the signing around this new scheme, effectively backporting the change to TLS 1.2. For now, it does not distinguish signature algorithms between 1.2 and 1.3 (RSA-PSS instead of RSA-PKCS1, ECDSA must match curve types). When the C code is ready make a similar change, the Go code will be updated to match. [Originally written by nharper, tweaked significantly by davidben.] Change-Id: If9a315c4670755089ac061e4ec254ef3457a00de Reviewed-on: https://boringssl-review.googlesource.com/8450 Reviewed-by: David Benjamin <davidben@google.com>
2016-06-21 23:19:24 +01:00
int expect_peer_signature_algorithm = 0;
Move curve check out of tls12_check_peer_sigalg. The current check has two problems: - It only runs on the server, where there isn't a curve list at all. This was a mistake in https://boringssl-review.googlesource.com/1843 which flipped it from client-only to server-only. - It only runs in TLS 1.2, so one could bypass it by just negotiating TLS 1.1. Upstream added it as part of their Suite B mode, which requires 1.2. Move it elsewhere. Though we do not check the entire chain, leaving that to the certificate verifier, signatures made by the leaf certificate are made by the SSL/TLS stack, so it's reasonable to check the curve as part of checking suitability of a leaf. Change-Id: I7c12f2a32ba946a20e9ba6c70eff23bebcb60bb2 Reviewed-on: https://boringssl-review.googlesource.com/6414 Reviewed-by: Adam Langley <agl@google.com>
2015-11-02 17:11:35 +00:00
bool p384_only = false;
Test all supported curves (including those off by default). Change-Id: I54b2b354ab3d227305f829839e82e7ae7292fd7d Reviewed-on: https://boringssl-review.googlesource.com/6774 Reviewed-by: Adam Langley <agl@google.com>
2015-12-19 01:55:44 +00:00
bool enable_all_curves = false;
Add SSL_get_curve_id and SSL_get_dhe_group_size. This replaces the old key_exchange_info APIs and does not require the caller be aware of the mess around SSL_SESSION management. They currently have the same bugs around renegotiation as before, but later work to fix up SSL_SESSION tracking will fix their internals. For consistency with the existing functions, I've kept the public API at 'curve' rather than 'group' for now. I think it's probably better to have only one name with a single explanation in the section header rather than half and half. (I also wouldn't be surprised if the IETF ends up renaming 'group' again to 'key exchange' at some point. We'll see what happens.) Change-Id: I8e90a503bc4045d12f30835c86de64ef9f2d07c8 Reviewed-on: https://boringssl-review.googlesource.com/8565 Reviewed-by: Adam Langley <agl@google.com>
2016-06-30 19:55:33 +01:00
int expect_curve_id = 0;
Add tests for the old client cert callback. Also add no-certificate cases to the state machine coverage tests. Change-Id: I88a80df6f3ea69aabc978dd356abcb9e309e156f Reviewed-on: https://boringssl-review.googlesource.com/7417 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-10 14:15:01 +00:00
bool use_old_client_cert_callback = false;
Adding a method to change the initial DTLS retransmission timer value. This allows an application to override the default of 1 second, which is what's instructed in RFC 6347 but is not an absolute requirement. Change-Id: I0bbb16e31990fbcab44a29325b6ec7757d5789e5 Reviewed-on: https://boringssl-review.googlesource.com/7930 Reviewed-by: David Benjamin <davidben@google.com>
2016-05-11 03:30:28 +01:00
int initial_timeout_duration_ms = 0;
Add test for |SSL_get_client_CA_list|. Change-Id: Ibea6a9d52b000876740097f98c6891db4772371b Reviewed-on: https://boringssl-review.googlesource.com/14008 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>
2017-02-28 21:45:39 +00:00
std::string use_client_ca_list;
std::string expected_client_ca_list;
Add SSL_send_fatal_alert. WebRTC want to be able to send a random alert. Add an API for this. Change-Id: Id3113d68f25748729fd9e9a91dbbfa93eead12c3 Reviewed-on: https://boringssl-review.googlesource.com/8950 Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> 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-07-26 23:03:08 +01:00
bool send_alert = false;
Add tests for SSL_peek. SSL_peek works fine for us, but OpenSSL 1.1.0 regressed this (https://github.com/openssl/openssl/issues/1563), and we don't have tests either. Fix this. SSL_peek can handle all weird events that SSL_read can, so use runner and tell bssl_shim to do a SSL_peek + SSL_peek + SSL_read instead of SSL_read. Then add tests for all the events we may discover. Change-Id: I9e8635e3ca19653a02a883f220ab1332d4412f98 Reviewed-on: https://boringssl-review.googlesource.com/11090 Reviewed-by: Adam Langley <agl@google.com>
2016-09-19 18:08:16 +01:00
bool peek_then_read = false;
Implement draft-davidben-tls-grease-01. This GREASEs cipher suites, groups, and extensions. For now, we'll always place them in a hard-coded position. We can experiment with more interesting strategies later. If we add new ciphers and curves, presumably we prefer them over current ones, so place GREASE values at the front. This prevents implementations from parsing only the first value and ignoring the rest. Add two new extensions, one empty and one non-empty. Place the empty one in front (IBM WebSphere can't handle trailing empty extensions) and the non-empty one at the end. Change-Id: If2e009936bc298cedf2a7a593ce7d5d5ddbb841a Reviewed-on: https://boringssl-review.googlesource.com/11241 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-09-03 02:35:25 +01:00
bool enable_grease = false;
Add tests for very large handshake messages. OpenSSL recently had a regression here (CVE-2016-6309). We're fine, but so that we stay that way, add some tests. Change-Id: I244d7ff327b7aad550f86408c5e5e65e6d1babe5 Reviewed-on: https://boringssl-review.googlesource.com/11321 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-09-27 00:57:53 +01:00
int max_cert_list = 0;
Add tests which modify the shim ticket. The existing tests for this codepath require us to reconfigure the shim. This will not work when TLS 1.3 cipher configuration is detached from the old cipher language. It also doesn't hit codepaths like sessions containing a TLS 1.3 version but TLS 1.2 cipher. Instead, add some logic to the runner to rewrite tickets and build tests out of that. Change-Id: I57ac5d49c3069497ed9aaf430afc65c631014bf6 Reviewed-on: https://boringssl-review.googlesource.com/12024 Reviewed-by: Adam Langley <agl@google.com>
2016-11-01 17:58:25 +00:00
std::string ticket_key;
Forbid using exporters during a renego. They will get very confused about which key they're using. Any caller using exporters must either (a) leave renegotiation off or (b) be very aware of when renegotiations happen anyway. (You need to somehow coordinate with the peer about which epoch's exporter to use.) Change-Id: I921ad01ac9bdc88f3fd0f8283757ce673a47ec75 Reviewed-on: https://boringssl-review.googlesource.com/12003 Reviewed-by: Adam Langley <agl@google.com>
2016-11-01 23:45:06 +00:00
bool use_exporter_between_reads = false;
Detach TLS 1.3 cipher configuration from the cipher language. TLS 1.3 ciphers are now always enabled and come with a hard-coded preference order. BUG=110 Change-Id: Idd9cb0d75fb6bf2676ecdee27d88893ff974c4a3 Reviewed-on: https://boringssl-review.googlesource.com/12025 Reviewed-by: Adam Langley <agl@google.com>
2016-10-31 23:20:42 +00:00
int expect_cipher_aes = 0;
int expect_cipher_no_aes = 0;
Add runner tests which send intermediate certificates. Certificate chain with intermediate taken from Chromium's tests. Though it doesn't really matter because the runner tests don't verify certificates. BUG=70 Change-Id: I46fd1d4be0f371b5bfd43370b97d2c8053cfad60 Reviewed-on: https://boringssl-review.googlesource.com/12261 CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Steven Valdez <svaldez@chromium.org> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com>
2016-11-15 01:16:54 +00:00
std::string expect_peer_cert_file;
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
int resumption_delay = 0;
Cut down on some redundant flags. We have fancy -on-initial and -on-resume prefixes now that can apply to every flag. Change-Id: I6195a97f663ebc94db320ca35889c213c700a976 Reviewed-on: https://boringssl-review.googlesource.com/19666 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-08-24 07:01:37 +01:00
bool retain_only_sha256_client_cert = false;
bool expect_sha256_client_cert = false;
Add a test for renegotiation on busy write buffer. The write path for TLS is going to need some work. There are some fiddly cases when there is a write in progress. Start adding tests to cover this logic. Later I'm hoping we can extend this flag so it drains the unfinished write and thus test the interaction of read/write paths in 0-RTT. (We may discover 1-RTT keys while we're in the middle of writing data.) Change-Id: Iac2c417e4b5e84794fb699dd7cbba26a883b64ef Reviewed-on: https://boringssl-review.googlesource.com/13049 Reviewed-by: Adam Langley <agl@google.com>
2017-01-02 04:19:22 +00:00
bool read_with_unfinished_write = false;
Report TLS 1.3 as supporting secure renegotiation. TLS 1.3 doesn't support renegotiation in the first place, but so callers don't report TLS 1.3 servers as missing it, always report it as (vacuously) protected against this bug. BUG=chromium:680281 Change-Id: Ibfec03102b2aec7eaa773c331d6844292e7bb685 Reviewed-on: https://boringssl-review.googlesource.com/13046 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-03 15:49:28 +00:00
bool expect_secure_renegotiation = false;
bool expect_no_secure_renegotiation = false;
Test SSL_set_max_send_fragment. This gives coverage over needing to fragment something over multiple records. Change-Id: I2373613608ef669358d48f4e12f68577fa5a40dc Reviewed-on: https://boringssl-review.googlesource.com/13101 Reviewed-by: Adam Langley <agl@google.com>
2017-01-06 21:19:28 +00:00
int max_send_fragment = 0;
int read_size = 0;
TLS 1.3 sessions should not be added to the server session cache. Fix this and add a test. Otherwise enabling TLS 1.3 will cause a server to blow through its session cache. Change-Id: I67edbc468faedfd94a6c30cf842af085a6543b50 Reviewed-on: https://boringssl-review.googlesource.com/13501 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>
2017-01-28 06:39:29 +00:00
bool expect_session_id = false;
bool expect_no_session_id = false;
Export server-side ticket_age skew. We'll measure this value to guide what tolerance to use in the 0-RTT anti-replay mechanism. This also fixes a bug where we were previously minting ticket_age_add-less tickets on the server. Add a check to reject all those tickets. BUG=113 Change-Id: I68e690c0794234234e0d0500b4b9a7f79aea641e Reviewed-on: https://boringssl-review.googlesource.com/14068 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>
2017-03-03 20:05:56 +00:00
int expect_ticket_age_skew = 0;
Test the behavior of running SSL_do_handshake twice in a row. BUG=185 Change-Id: I4ce6735ca78cd687538a8c0fdbd78ee97b93585c Reviewed-on: https://boringssl-review.googlesource.com/14382 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-26 21:13:51 +01:00
bool no_op_extra_handshake = false;
bool handshake_twice = false;
Add an option to allow unknown ALPN protocols. We received an external request to add an option to undo the check added in 3e51757de2bf9beef7d249f22d255e4dd9ddb012. Change-Id: Ifdd4b07705f2fa3d781d775d5cd139ea72d36734 Reviewed-on: https://boringssl-review.googlesource.com/14644 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-04-04 18:52:36 +01:00
bool allow_unknown_alpn_protos = false;
Support Ed25519 in TLS. This only works at TLS 1.2 and above as, before TLS 1.2, there is no way to advertise support for Ed25519 or negotiate the correct signature algorithm. Add tests for this accordingly. For now, this is disabled by default on the verifying side but may be enabled per SSL_CTX. Notably, projects like Chromium which use an external verifier may need changes elsewhere before they can enable it. (On the signing side, we can assume that if the caller gave us an Ed25519 certificate, they mean for us to use it.) BUG=187 Change-Id: Id25b0a677dcbe205ddd26d8dbba11c04bb520756 Reviewed-on: https://boringssl-review.googlesource.com/14450 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com>
2017-03-28 21:38:29 +01:00
bool enable_ed25519 = false;
Add async certificate verification callback. This also serves as a certificate verification callback for CRYPTO_BUFFER-based consumers. Remove the silly SSL_CTX_i_promise_to_verify_certs_after_the_handshake placeholder. Bug: 54, chromium:347402 Change-Id: I4c6b445cb9cd7204218acb2e5d1625e6f37aff6f Reviewed-on: https://boringssl-review.googlesource.com/17964 Reviewed-by: David Benjamin <davidben@google.com>
2017-07-11 21:13:10 +01:00
bool use_custom_verify_callback = false;
Fix a bug in and test the message callback. reuse_message and V2ClientHellos each caused messages to be double-reported. Change-Id: I8722a3761ede272408ac9cf8e1b2ce383911cc6f Reviewed-on: https://boringssl-review.googlesource.com/18764 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>
2017-08-01 23:38:41 +01:00
std::string expect_msg_callback;
Add an option for False Start without ALPN. We can probably do this globally at this point since the cipher requirements are much more restrict than they were in the beginning. (Firefox, in particular, has done so far a while.) For now add a flag since some consumer wanted this. I'll see about connecting it to a Chrome field trial after our breakage budget is no longer reserved for TLS 1.3. Change-Id: Ib61dd5aae2dfd48b56e79873a7f3061a7631a5f8 Reviewed-on: https://boringssl-review.googlesource.com/23725 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>
2017-12-01 18:05:12 +00:00
bool allow_false_start_without_alpn = false;
Implement TLS 1.3 anti-downgrade signal. Change-Id: Ib4739350948ec339457d993daef582748ed8f100 Reviewed-on: https://boringssl-review.googlesource.com/30924 Commit-Queue: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: David Benjamin <davidben@google.com>
2018-08-13 15:54:48 +01:00
bool ignore_tls13_downgrade = false;
bool expect_tls13_downgrade = false;
Add tests for split handshakes. This change adds a couple of focused tests to ssl_test.cc, but also programmically duplicates many runner tests in a split-handshake mode. Change-Id: I9dafc8a394581e5daf1318722e1015de82117fd9 Reviewed-on: https://boringssl-review.googlesource.com/25388 Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2018-01-26 17:17:53 +00:00
bool handoff = false;
Add an API to disable RSA-PSS for certificates. Chrome uses the platform certificate verifier and thus cannot reliably expect PSS signatures to work in all configurations. Add an API for the consumer to inform BoringSSL of this ability. We will then adjust our advertisements accordingly. Note that, because TLS 1.2 does not have the signature_algorithms_cert extension, turning off TLS 1.3 and using this API will stop advertising RSA-PSS. I believe this is the correct behavior given the semantics of that code point. The tests check the various combinations here, as well as checking that the peer never sends signature_algorithms_cert identical to signature_algorithms. Bug: 229 Change-Id: I8c33a93efdc9252097e3899425b49548fc42a93a Reviewed-on: https://boringssl-review.googlesource.com/27488 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-04-08 18:59:25 +01:00
bool no_rsa_pss_rsae_certs = false;
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
bool use_ocsp_callback = false;
bool set_ocsp_in_callback = false;
bool decline_ocsp_callback = false;
bool fail_ocsp_callback = false;
Preliminary support for compressed certificates. This change adds server-side support for compressed certificates. (Although some definitions for client-side support are included in the headers, there's no code behind them yet.) Change-Id: I0f98abf0b782b7337ddd014c58e19e6b8cc5a3c2 Reviewed-on: https://boringssl-review.googlesource.com/27964 Reviewed-by: David Benjamin <davidben@google.com>
2018-05-02 17:06:48 +01:00
bool install_cert_compression_algs = false;
Option to reverify certs on resumption. Works in the 1.3 and 1.2 client handshakes, not implemented on the server for now. Creates an SSL_CTX option to reverify the server certificate on session resumption. Reverification only runs the client's certificate verify callback. Adds new states to the client handshakes: state_reverify_server_certificate in TLS 1.2, and state_server_certificate_reverify in TLS 1.3. Adds a negative test to make sure that by default we don't verify the certificate on resumption, and positive tests that make sure we do when the new option is set. Change-Id: I3a47ff3eacb3099df4db4c5bc57f7c801ceea8f1 Bug: chromium:347402 Reviewed-on: https://boringssl-review.googlesource.com/29984 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>
2018-08-10 18:28:47 +01:00
bool reverify_on_resume = false;
Ask shim whether it supports split handshakes. The runner currently expects split handshake tests to work is GOOS is "linux", but that includes Android, which the shim doesn't support. Rather than try to align these two conditions, have the runner ask the shim whether it supports split handshakes or not. Change-Id: I7bea0d94142c4b6ee42b8f54c67b8611da93feb3 Reviewed-on: https://boringssl-review.googlesource.com/30204 Reviewed-by: Matt Braithwaite <mab@google.com> 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>
2018-08-01 16:29:48 +01:00
bool is_handshaker_supported = false;
shim: perform split handshakes in a separate binary. The new binary, called |handshaker|, allows split-handshakes to be tested using shim and handshaker binaries built at different revisions. The shim now proxies traffic to the handshaker during the split handshake. The handoff and handback steps serialize additional state about the test being performed, and its results. The proxy and handshaker make heavy use of Unix-isms, and so split-handshake tests are now restricted to Linux. Change-Id: I048f0540c3978a31b3e573e00da17caf41a8059e Reviewed-on: https://boringssl-review.googlesource.com/29348 Reviewed-by: Adam Langley <agl@google.com>
2018-06-23 02:53:05 +01:00
bool handshaker_resume = false;
std::string handshaker_path;
Work around a JDK 11 TLS 1.3 bug. JDK 11 shipped with a TLS 1.3 implementation enabled by default. Unfortunately, that implementation does not work and fails to send the SNI extension on resumption. See https://bugs.openjdk.java.net/browse/JDK-8211806. This means servers which enable TLS 1.3 will see JDK 11 clients work on the first connection and then fail on all subsequent connections. Add SSL_set_jdk11_workaround which configures a workaround to fingerprint JDK 11 and disable TLS 1.3 with the faulty clients. JDK 11 also implemented the downgrade signal, which means that connections that trigger the workaround also must not send the downgrade signal. Unfortunately, the downgrade signal's security properties are sensitive to the existence of any unmarked TLS 1.2 ServerHello paths. To salvage this, pick a new random downgrade marker for this scenario and modify the client to treat it as an alias of the standard one. Per the link above, JDK 11.0.2 will fix this bug. Hopefully the workaround can be retired sometime after it is released. Change-Id: I0627609a8cadf7cc214073eb7f1e880acdf613ef Reviewed-on: https://boringssl-review.googlesource.com/c/33284 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com>
2018-11-19 21:49:56 +00:00
bool jdk11_workaround = false;
shim: perform split handshakes in a separate binary. The new binary, called |handshaker|, allows split-handshakes to be tested using shim and handshaker binaries built at different revisions. The shim now proxies traffic to the handshaker during the split handshake. The handoff and handback steps serialize additional state about the test being performed, and its results. The proxy and handshaker make heavy use of Unix-isms, and so split-handshake tests are now restricted to Linux. Change-Id: I048f0540c3978a31b3e573e00da17caf41a8059e Reviewed-on: https://boringssl-review.googlesource.com/29348 Reviewed-by: Adam Langley <agl@google.com>
2018-06-23 02:53:05 +01:00
int argc;
char **argv;
shim: move |TestState| and |TestConfig| to their own files. This makes |TestState| and |TestConfig| accessible outside bssl_shim.cc, as well as the functions SetupCtx() and NewSSL(), which become methods on |TestConfig|. A whole mess of callbacks move in order to support this change. Along the way, some bits of global state are moved (e.g. the global test clock) and made self-initializing. This helps with creating a separate binary to perform split handshakes. Change-Id: I39b00a1819074882353f5f04ed01312916f3cccb Reviewed-on: https://boringssl-review.googlesource.com/29345 Commit-Queue: Matt Braithwaite <mab@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: David Benjamin <davidben@google.com>
2018-06-22 23:53:19 +01:00
bssl::UniquePtr<SSL_CTX> SetupCtx(SSL_CTX *old_ctx) const;
bssl::UniquePtr<SSL> NewSSL(SSL_CTX *ssl_ctx, SSL_SESSION *session,
bool is_resume,
std::unique_ptr<TestState> test_state) const;
Move configuration into a dedicated TestConfig struct. This removes some duplicate code in parsing command-line flags and, more importantly, makes configuration available when constructing the SSL_CTX and avoids a number of globals. Change-Id: I26e2d2285b732f855a2c82752bc8e0db480c3b30 Reviewed-on: https://boringssl-review.googlesource.com/1502 Reviewed-by: Adam Langley <agl@google.com>
2014-08-12 00:51:50 +01:00
};
Adding support for sending early data on the client. BUG=76 Change-Id: If58a73da38e46549fd55f84a9104e2dfebfda43f Reviewed-on: https://boringssl-review.googlesource.com/14164 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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-03-09 19:56:07 +00:00
bool ParseConfig(int argc, char **argv, TestConfig *out_initial,
TestConfig *out_resume, TestConfig *out_retry);
Move configuration into a dedicated TestConfig struct. This removes some duplicate code in parsing command-line flags and, more importantly, makes configuration available when constructing the SSL_CTX and avoids a number of globals. Change-Id: I26e2d2285b732f855a2c82752bc8e0db480c3b30 Reviewed-on: https://boringssl-review.googlesource.com/1502 Reviewed-by: Adam Langley <agl@google.com>
2014-08-12 00:51:50 +01:00
shim: move |TestState| and |TestConfig| to their own files. This makes |TestState| and |TestConfig| accessible outside bssl_shim.cc, as well as the functions SetupCtx() and NewSSL(), which become methods on |TestConfig|. A whole mess of callbacks move in order to support this change. Along the way, some bits of global state are moved (e.g. the global test clock) and made self-initializing. This helps with creating a separate binary to perform split handshakes. Change-Id: I39b00a1819074882353f5f04ed01312916f3cccb Reviewed-on: https://boringssl-review.googlesource.com/29345 Commit-Queue: Matt Braithwaite <mab@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: David Benjamin <davidben@google.com>
2018-06-22 23:53:19 +01:00
bool SetTestConfig(SSL *ssl, const TestConfig *config);
const TestConfig *GetTestConfig(const SSL *ssl);
bool LoadCertificate(bssl::UniquePtr<X509> *out_x509,
bssl::UniquePtr<STACK_OF(X509)> *out_chain,
const std::string &file);
bssl::UniquePtr<EVP_PKEY> LoadPrivateKey(const std::string &file);
Move configuration into a dedicated TestConfig struct. This removes some duplicate code in parsing command-line flags and, more importantly, makes configuration available when constructing the SSL_CTX and avoids a number of globals. Change-Id: I26e2d2285b732f855a2c82752bc8e0db480c3b30 Reviewed-on: https://boringssl-review.googlesource.com/1502 Reviewed-by: Adam Langley <agl@google.com>
2014-08-12 00:51:50 +01:00
#endif // HEADER_TEST_CONFIG
Reference in New Issue Copy Permalink