- 23 Nov, 2016 9 commits
-
-
Matt Caswell authored
After the client processes the server's initial flight in TLS1.3 it may respond with either an encrypted, or an unencrypted alert. We needed to teach TLSProxy about this so that it didn't issue spurious warnings. Reviewed-by:Rich Salz <rsalz@openssl.org>
-
Matt Caswell authored
In one case we weren't always sending an unexpected message alert if we don't get what we expect. Reviewed-by: -
Matt Caswell authored
There is a set of miscellaneous processing for OCSP, CT etc at the end of the ServerDone processing. In TLS1.3 we don't have a ServerDone, so this needs to move elsewhere. Reviewed-by: -
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
The previous commit had a dummy payload for the Finished data. This commit fills it in with a real value. Reviewed-by: -
Matt Caswell authored
This is a major overhaul of the TLSv1.3 state machine. Currently it still looks like TLSv1.2. This commit changes things around so that it starts to look a bit less like TLSv1.2 and bit more like TLSv1.3. After this commit we have: ClientHello + key_share ----> ServerHello +key_share {CertificateRequest*} {Certificate*} {CertificateStatus*} <---- {Finished} {Certificate*} {CertificateVerify*} {Finished} ----> [ApplicationData] <---> [Application Data] Key differences between this intermediate position and the final TLSv1.3 position are: - No EncryptedExtensions message yet - No server side CertificateVerify message yet - CertificateStatus still exists as a separate message - A number of the messages are still in the TLSv1.2 format - Still running on the TLSv1.2 record layer Reviewed-by: -
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
TLSv1.3 has a NewSessionTicket message, but it is *completely* different to the TLSv1.2 one and may as well have been called something else. This commit removes the old style NewSessionTicket from TLSv1.3. We will have to add the new style one back in later. Reviewed-by: -
Matt Caswell authored
Commit 94ed2c67 dropped a ! operator by mistake, which causes extended master secret connections to fail. This puts in back. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
- 22 Nov, 2016 1 commit
-
-
Richard Levitte authored
Reviewed-by:
-
- 21 Nov, 2016 3 commits
-
-
Kurt Roeckx authored
b6d5ba1a forgot to update some linux arches. Reviewed-by:
-
Todd Short authored
When configured with "no-mdc2 enable-crypto-mdebug" the evp_test will leak memory due to skipped tests, and error out. Also fix a skip condition Reviewed-by:
-
Kurt Roeckx authored
This reverts commit 4880672a . Fixes: #1903 Reviewed-by:
Matt Caswell <matt@openssl.org> GH: #1931
-
- 20 Nov, 2016 1 commit
-
-
Dr. Stephen Henson authored
Reviewed-by:
-
- 18 Nov, 2016 5 commits
-
-
Robert Scheck authored
Reviewed-by:
-
Robert Scheck authored
Reviewed-by:
-
Robert Scheck authored
Reviewed-by:
-
Beat Bolli authored
In the X509_NAME_get_index_by_NID.pod example, the initialized variable is called "loc", but the one used in the for loop is called "lastpos". Make the names match. CLA: trivial Reviewed-by:
-
Beat Bolli authored
CLA: trivial Since 99d63d46 ("Move manpages to man[1357] structure.", 2016-10-26), the location of the pod files has changed. Reviewed-by:
-
- 17 Nov, 2016 21 commits
-
-
Kurt Roeckx authored
It's called with 0 when it's already locked, with 1 when it's not. Reviewed-by:
Andy Polyakov <appro@openssl.org> Reviewed-by:
-
Kurt Roeckx authored
Reviewed-by:
-
Dr. Stephen Henson authored
Reviewed-by: -
Andy Polyakov authored
In non-__KERNEL__ context 32-bit-style __ARMEB__/__ARMEL__ macros were set in arm_arch.h, which is shared between 32- and 64-bit builds. Since it's not included in __KERNEL__ case, we have to adhere to official 64-bit pre-defines, __AARCH64EB__/__AARCH64EL__. [If we are to share more code, it would need similar adjustment.] Reviewed-by:
-
Matt Caswell authored
We should use the macro for testing if we are using TLSv1.3 rather than checking s->version directly. Reviewed-by: -
Nicola Tuveri authored
Calling EVP_PKEY_CTX_new_id(curve_NID, NULL) causes an error for most curves that are implemented through the EC low-level API, and in the last commit we call it for every curve to avoid treating X25519 as a special case. Last commit code already handles correctly this failure, but does not remove these events from the thread error queue, thus some false-positive warnings are printed at the end of execution. This commit ensures that the error queue is clean, without flushing other errors. Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Nicola Tuveri authored
Reviewed-by:
-
Dr. Stephen Henson authored
Reviewed-by: -
Dr. Stephen Henson authored
Reviewed-by: -
Dr. Stephen Henson authored
Reviewed-by: -
FdaSilvaYY authored
Both strdup or malloc failure should raise à err. Reviewed-by:
-
