- Jan 06, 2017
-
-
Kurt Roeckx authored
Reviewed-by:Rich Salz <rsalz@openssl.org> GH: #2182
-
Kurt Roeckx authored
Reviewed-by: -
Kurt Roeckx authored
Reviewed-by: -
Kurt Roeckx authored
Reviewed-by: -
Kurt Roeckx authored
Reviewed-by: -
Matt Caswell authored
Reviewed-by:
-
Matt Caswell authored
This variable represents the index of the cert within the chain, so give it a name that better represents that. Reviewed-by:
-
Matt Caswell authored
Reviewed-by:
-
Matt Caswell authored
al can be used uninitialised in an error path. Reviewed-by:
-
Matt Caswell authored
Reviewed-by:
-
Matt Caswell authored
We remove the separate CertificateStatus message for TLSv1.3, and instead send back the response in the appropriate Certificate message extension. Reviewed-by:
-
Matt Caswell authored
Also updates TLSProxy to be able to understand the format and parse the contained extensions. Reviewed-by:
-
Matt Caswell authored
Continuing from the previous commit we also need to extend the extensions framework to supply the Certificate we just read during parsing. Reviewed-by:
-
Matt Caswell authored
The Certificate message in TLS1.3 has an extensions block for each Certificate. Therefore we need to extend tls_construct_extensions() to pass in the certificate we are working on. We also pass in the position in the chain (with 0 being the first certificate). Reviewed-by:
-
- Jan 05, 2017
-
-
Dr. Stephen Henson authored
BIO_seek and BIO_tell can cause problems with evp_test.c on some platforms. Avoid them by using a temporary memory BIO to store key PEM data. Reviewed-by:
Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2183)
-
- Jan 04, 2017
-
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
- Jan 01, 2017
-
-
Dr. Stephen Henson authored
Reviewed-by: -
Dr. Stephen Henson authored
Reviewed-by:
-
- Dec 30, 2016
-
-
Matt Caswell authored
We need a new API for TLSv1.3 sig algs Reviewed-by:
Tim Hudson <tjh@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2160)
-
Matt Caswell authored
Reviewed-by:
-
Matt Caswell authored
This macro has a typo in it which makes it unusable. This issue was already fixed in 1.0.2 in commit 75fdee04 , but the same fix was not applied to other branches. Reviewed-by:
-
- Dec 29, 2016
-
-
Richard Levitte authored
These tests depend on there being at least one protocol version below TLSv1.3 enabled. Reviewed-by:
Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2144)
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Matt Caswell authored
The CT tests in test_sslmessages require EC to be available, therefore we must skip these if no-ec Reviewed-by:
-
Matt Caswell authored
Reviewed-by:
-
Matt Caswell authored
Previously we were omitting the extension information from ext_defs if the association no- option was defined. This doesn't work because the indexes into the table are no longer valid. Reviewed-by:
-
Matt Caswell authored
The previous commit fixed a bug where the EC point formats extensions did not appear in the ServerHello. This should have been caught by 70-test_sslmessages but that test never tries an EC ciphersuite. This updates the test to do that. Reviewed-by:
-
Matt Caswell authored
This should be sent in the ServerHello if a EC based ciphersuite is negotiated. The relevant flag to do this was missed off in the recent extensions refactor. Fixes GitHub Issue #2133 Reviewed-by:
-
Markus Triska authored
Reviewed-by:
-
- Dec 25, 2016
-
-
Andy Polyakov authored
Reviewed-by:
-
- Dec 22, 2016
-
-
Todd Short authored
Reviewed-by:
-
- Dec 21, 2016
-
-
Richard Levitte authored
We should move it back to the BORINGTEST build when we are approaching interoperability. Reviewed-by:
Kurt Roeckx <kurt@openssl.org> Reviewed-by:
-
- Dec 20, 2016
-
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
For now, checking that the size is non-zero will suffice. Reviewed-by:
-
