openssl/ssl, branch OpenSSL_1_0_2l

Ignore -rle and -comp when compiled with OPENSSL_NO_COMP.

2017-05-25T11:36:45Z

Fixes make test when configured with no-comp. Reviewed-by: Kurt Roeckx Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/3545)

Copy custom extension flags in a call to SSL_set_SSL_CTX()

2017-05-10T13:06:58Z

The function SSL_set_SSL_CTX() can be used to swap the SSL_CTX used for a connection as part of an SNI callback. One result of this is that the s->cert structure is replaced. However this structure contains information about any custom extensions that have been loaded. In particular flags are set indicating whether a particular extension has been received in the ClientHello. By replacing the s->cert structure we lose the custom extension flag values, and it appears as if a client has not sent those extensions. SSL_set_SSL_CTX() should copy any flags for custom extensions that appear in both the old and the new cert structure. Fixes #2180 Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/3427)

Additional check to handle BAD SSL_write retry

2017-04-11T16:17:54Z

Reviewed-by: Matt Caswell Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/3122)

Guard last few debugging printfs in libssl

2017-03-23T13:47:41Z

Fixes #2542 Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/3018)

Fix BAD CCS alert in DTLS

2017-03-21T16:23:33Z

Set the correct variable, and then actually send the alert! Found by, and fix suggested by, Raja Ashok. Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/3009)

Avoid a mem leak on error

2017-03-21T09:53:02Z

An internal error path could result in a memory leak. Also remove some redundant code. Reviewed-by: Richard Levitte (Merged from https://github.com/openssl/openssl/pull/3003)

Fix DTLSv1_listen() sequence numbers

2017-03-13T13:08:01Z

DTLSv1_listen() is stateless. We never increment the record read sequence while listening, and we reflect the incoming record's sequence number in our write sequence. The logic for doing the write sequence reflection was *after* we had finished processing the incoming ClientHello and before we write the ServerHello. In the normal course of events this is fine. However if we need to write an early alert during ClientHello processing (e.g. no shared cipher), then we haven't done the write sequence reflection yet. This means the alert gets written with the wrong sequence number (it will just be set to whatever value we left it in the last time we wrote something). If the sequence number is less than expected then the client will believe that the incoming alert is a retransmit and will therefore drop it, causing the client to hang waiting for a response from the server. Fixes #2886 Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/2915)

Revert "Use the callbacks from the SSL object instead of the SSL_CTX object"

2017-03-11T10:19:20Z

This shouldn't have been applied to the 1.0.2 branch. This reverts commit 5247c0388610bfdcc8f44b777d75ab681120753d. Reviewed-by: Tim Hudson (Merged from https://github.com/openssl/openssl/pull/2907)

Use the callbacks from the SSL object instead of the SSL_CTX object

2017-03-10T21:34:15Z

... in functions dealing with the SSL object rather than the context. Reviewed-by: Rich Salz Reviewed-by: Richard Levitte (Merged from https://github.com/openssl/openssl/pull/2870) (cherry picked from commit d61461a7525322d188f9c6e3f90cfc93916cc636)

Avoid questionable use of the value of a pointer

2017-03-10T20:57:59Z

that refers to space deallocated by a call to the free function in tls_decrypt_ticket. Reviewed-by: Matt Caswell Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/2897) (cherry picked from commit 13ed1afa923f4ffb553e389de08f26e9ce84e8a2)