TLS/SSL and crypto library. http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_0_1f 2014-01-06T14:35:04Z 2014-01-06T14:35:04Z Dr. Stephen Henson steve@openssl.org 2014-01-06T14:35:04Z urn:sha1:197e0ea817ad64820789d86711d55ff50d71f631 2014-01-06T13:33:27Z Dr. Stephen Henson steve@openssl.org 2014-01-06T13:33:27Z urn:sha1:c776a3f398b1fd0d59e9247c0c4c6b79f5692b33 2014-01-04T14:00:44Z Dr. Stephen Henson steve@openssl.org 2014-01-04T13:50:52Z urn:sha1:25c9fa6026e6a200a291bc4fd3464718aae9775e The flag SSL_OP_MSIE_SSLV2_RSA_PADDING hasn't done anything since OpenSSL 0.9.7h but deleting it will break source compatibility with any software that references it. Restore it but #define to zero. (cherry picked from commit b17d6b8d1d49fa4732deff17cfd1833616af0d9c) 2014-01-02T15:12:48Z Dr. Stephen Henson steve@openssl.org 2013-12-24T18:17:00Z urn:sha1:f3dcc8411e518fb0835c7d72df4a58718205260d When sending an invalid version number alert don't change the version number to the client version if a session is already established. Thanks to Marek Majkowski for additional analysis of this issue. PR#3191 2013-12-20T23:12:18Z Dr. Stephen Henson steve@openssl.org 2013-12-20T15:26:50Z urn:sha1:34628967f1e65dc8f34e000f0f5518e21afbfc7b For DTLS we might need to retransmit messages from the previous session so keep a copy of write context in DTLS retransmission buffers instead of replacing it after sending CCS. CVE-2013-6450. 2013-12-19T21:04:28Z Dr. Stephen Henson steve@openssl.org 2013-12-19T14:37:39Z urn:sha1:ca989269a2876bae79393bd54c3e72d49975fc75 When deciding whether to use TLS 1.2 PRF and record hash algorithms use the version number in the corresponding SSL_METHOD structure instead of the SSL structure. The SSL structure version is sometimes inaccurate. Note: OpenSSL 1.0.2 and later effectively do this already. (CVE-2013-6449) 2013-12-18T13:26:10Z Dr. Stephen Henson steve@openssl.org 2013-12-14T13:55:48Z urn:sha1:0294b2be5f4c11e60620c0018674ff0e17b14238 Partial mitigation of PR#3200 2013-12-08T13:23:14Z Dr. Stephen Henson steve@openssl.org 2013-12-08T13:13:29Z urn:sha1:60df657b3a72065c0df0349abf228d7399e20bac 2013-11-06T14:40:01Z Dr. Stephen Henson steve@openssl.org 2013-11-06T14:38:28Z urn:sha1:ddfe486e4c4869ac73fd8556cb6c64324c86621d Enable PSK ciphersuites with AES or DES3 in FIPS mode. (cherry picked from commit e0ffd129c16af90eb5e2ce54e57832c0046d1aaf) 2013-11-01T22:44:20Z Robin Seggelmann seggelmann@fh-muenster.de 2012-05-09T17:28:41Z urn:sha1:025f7dbdd18f8392f5bd58143b113ab6a0716f7a PR: 2808 With DTLS/SCTP the SCTP extension SCTP-AUTH is used to protect DATA and FORWARD-TSN chunks. The key for this extension is derived from the master secret and changed with the next ChangeCipherSpec, whenever a new key has been negotiated. The following Finished then already uses the new key. Unfortunately, the ChangeCipherSpec and Finished are part of the same flight as the ClientKeyExchange, which is necessary for the computation of the new secret. Hence, these messages are sent immediately following each other, leaving the server very little time to compute the new secret and pass it to SCTP before the finished arrives. So the Finished is likely to be discarded by SCTP and a retransmission becomes necessary. To prevent this issue, the Finished of the client is still sent with the old key. (cherry picked from commit 9fb523adce6fd6015b68da2ca8e4ac4900ac2be2) (cherry picked from commit b9ef52b07897f249a9fa44943dba33fba8fb2721)