From marquess at opensslfoundation.org Thu Jan 19 17:25:06 2017 From: marquess at opensslfoundation.org (Steve Marquess) Date: Thu, 19 Jan 2017 12:25:06 -0500 Subject: [openssl-announce] Akamai sponsors TLS 1.3 In-Reply-To: <1a7e4a62-465b-5af4-dfd8-c4481d65c11c@opensslfoundation.org> References: <1a7e4a62-465b-5af4-dfd8-c4481d65c11c@opensslfoundation.org> Message-ID: Many companies use OpenSSL, relatively few of them support it. I'm pleased to announce that Akamai (https://www.akamai.com/) has expanded its already substantial presence in the latter category. Akamai has contractually committed to funding implementation of TLS 1.3 in OpenSSL. That is something we were going to do anyway, an initiative that has been delayed by the major overhaul leading up to the 1.1 release. But, by contracting us to perform that implementation Akamai accomplishes two things: 1) A known schedule (with a key deadline of 2017-04-05). Left to our own devices and the usual resource contentions we would have taken longer; by funding us for a specific deliverable and schedule Akamai ensures a result that meets their own needs. 2) Significant financial support for OpenSSL, funding we would not otherwise have received which will be used for long term support of OpenSSL. While not technically a donation (because payment is contingent on specific deliverables) the end effect is the same, as we would have eventually done a comparable TLS 1.3 implementation anyway. Thank you Akamai for your well-considered initiative to both address your own business requirements and support OpenSSL and the OpenSSL user community at the same time; a win-win situation all around. -Steve M. -- Steve Marquess OpenSSL Software Foundation 20-22 Wenlock Road London N1 7GU United Kingdom +44 1785508015 +1 301 874 2571 direct marquess at opensslfoundation.org stevem at openssl.org From openssl at openssl.org Mon Jan 23 21:08:50 2017 From: openssl at openssl.org (OpenSSL) Date: Mon, 23 Jan 2017 21:08:50 +0000 (GMT) Subject: [openssl-announce] Forthcoming OpenSSL releases Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Forthcoming OpenSSL releases ============================ The OpenSSL project team would like to announce the forthcoming release of OpenSSL versions 1.0.2k, 1.1.0d. These releases will be made available on 26th January 2017 between approximately 1300-1700 UTC. They will fix several security defects with maximum severity "moderate". Please see the following page for further details of severity levels: https://www.openssl.org/policies/secpolicy.html Please also note that, as per our previous announcements, support for 1.0.1 ended on 31st December 2016. Yours The OpenSSL Project Team -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCAAGBQJYhk6JAAoJEAEKUEB8TIy9LZIH/0nJUa7i/rUZTG2laUZmtcVa K7kmYAG7EQd836eoSLvbC4DAbZL/fpQwGMSdvbNNmsgaLvyLS4fO5VaiT7gWptBz 2QKnwCr32Ixn59USbpHth+EqpzwKl3nOJcNZlGJ5Pid2Q0SKY8Bw8gMx3hVzEoAi d6X4cD71wkigBV41yb7iQ7upRzBvGFWN8qnvSBf9hLPetOq4Dw0imcZT165wYrIC vFiLV5WexU4J5iGdUeWVF6CMw7duExeuY/Ii0mBQ/d/DsWz0S9KnOyN5MANYGkbZ 2y4i6zgPtNrprHoYXPDkBpjRaEuW/WtVEEMCmd49mkYNZkDnuF6ViaKP3UMfWDs= =GksO -----END PGP SIGNATURE----- From openssl at openssl.org Thu Jan 26 14:01:36 2017 From: openssl at openssl.org (OpenSSL) Date: Thu, 26 Jan 2017 14:01:36 +0000 Subject: [openssl-announce] OpenSSL version 1.0.2k published Message-ID: <20170126140136.GA22894@openssl.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 OpenSSL version 1.0.2k released =============================== OpenSSL - The Open Source toolkit for SSL/TLS https://www.openssl.org/ The OpenSSL project team is pleased to announce the release of version 1.0.2k of our open source toolkit for SSL/TLS. For details of changes and known issues see the release notes at: https://www.openssl.org/news/openssl-1.0.2-notes.html OpenSSL 1.0.2k is available for download via HTTP and FTP from the following master locations (you can find the various FTP mirrors under https://www.openssl.org/source/mirror.html): * https://www.openssl.org/source/ * ftp://ftp.openssl.org/source/ The distribution file name is: o openssl-1.0.2k.tar.gz Size: 5309236 SHA1 checksum: 5f26a624479c51847ebd2f22bb9f84b3b44dcb44 SHA256 checksum: 6b3977c61f2aedf0f96367dcfb5c6e578cf37e7b8d913b4ecb6643c3cb88d8c0 The checksums were calculated using the following commands: openssl sha1 openssl-1.0.2k.tar.gz openssl sha256 openssl-1.0.2k.tar.gz Yours, The OpenSSL Project Team. -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJYifggAAoJENnE0m0OYESRHWUIAJXlSdrySe40QGFuOfSUQya0 iWTa0PcIPCPjSaM1Rige1BMSwTVhWwNmdimAyG94I1/y6uAoJzFsfNs4xSPlsGGO 9pdAiqeu9GAnJ3z4H/mkasUAmzXkemeWt5dN9KdANbT7HAg+ROKmthrmWiffftoU x+sGZ/lThIfKIYf+Ch5EmM4VFuCU9gG6YTwlUSKQAcnmcPt1AVrGlSxyVTx1Ahku Pl3iYbQors6vfBlh4BZZnxh7NJW4WRpJ77+1OH8xaOobJQMDZ5VQqnPMIIbbMLoM MAJz7T0nfzTaQ8Yzwv078qNPuwzeumI92NGybETbOI8zThHdEffsOegBaHqV+Jk= =KDh3 -----END PGP SIGNATURE----- From openssl at openssl.org Thu Jan 26 14:02:01 2017 From: openssl at openssl.org (OpenSSL) Date: Thu, 26 Jan 2017 14:02:01 +0000 Subject: [openssl-announce] OpenSSL version 1.1.0d published Message-ID: <20170126140201.GA22932@openssl.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 OpenSSL version 1.1.0d released =============================== OpenSSL - The Open Source toolkit for SSL/TLS https://www.openssl.org/ The OpenSSL project team is pleased to announce the release of version 1.1.0d of our open source toolkit for SSL/TLS. For details of changes and known issues see the release notes at: https://www.openssl.org/news/openssl-1.1.0-notes.html OpenSSL 1.1.0d is available for download via HTTP and FTP from the following master locations (you can find the various FTP mirrors under https://www.openssl.org/source/mirror.html): * https://www.openssl.org/source/ * ftp://ftp.openssl.org/source/ The distribution file name is: o openssl-1.1.0d.tar.gz Size: 5201626 SHA1 checksum: f423e9253ad8a8617fc9fb3562788a9fa066d46f SHA256 checksum: 7d5ebb9e89756545c156ff9c13cf2aa6214193b010a468a3bc789c3c28fe60df The checksums were calculated using the following commands: openssl sha1 openssl-1.1.0d.tar.gz openssl sha256 openssl-1.1.0d.tar.gz Yours, The OpenSSL Project Team. -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJYifVEAAoJENnE0m0OYESRcPYH/AqSYRJDURNli0/PhHa45ynT eXGk5v44l0q/TBqHOiUjPEAE6ctMe+Dg2Bw+2UI5msGZDyD+alksUrf94OzFMIll UC3FPAyAAIxu/DNyL/tRyGwBqOyHrzvKzwl+yGnOtzQ/a9/la79KCSTUMheDDBgk 2LiPoGi35wfNpJ+jBr/ucPto15+dWQfTMxX8aeYWkdVjUGGcO4XmAuqpIo5Jl7gw szSzpgvLB55sRZ8o6edU9knoIGRad+TH9JjfKAIzAIUH5BWaALmswQUMWhKTQkpX jHosHsLUPBLqqPJtmlLr1T7bHXGqz3fvQF0/lHYKA9eQDm0Owd0izeJlsiqaCac= =WZYB -----END PGP SIGNATURE----- From openssl at openssl.org Thu Jan 26 14:04:46 2017 From: openssl at openssl.org (OpenSSL) Date: Thu, 26 Jan 2017 14:04:46 +0000 Subject: [openssl-announce] OpenSSL Security Advisory Message-ID: <20170126140446.GA24451@openssl.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 OpenSSL Security Advisory [26 Jan 2017] ======================================== Truncated packet could crash via OOB read (CVE-2017-3731) ========================================================= Severity: Moderate If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k This issue was reported to OpenSSL on 13th November 2016 by Robert ?wi?cki of Google. The fix was developed by Andy Polyakov of the OpenSSL development team. Bad (EC)DHE parameters cause a client crash (CVE-2017-3730) =========================================================== Severity: Moderate If a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this can result in the client attempting to dereference a NULL pointer leading to a client crash. This could be exploited in a Denial of Service attack. OpenSSL 1.1.0 users should upgrade to 1.1.0d This issue does not affect OpenSSL version 1.0.2. Note that this issue was fixed prior to it being recognised as a security concern. This means the git commit with the fix does not contain the CVE identifier. The relevant fix commit can be identified by commit hash efbe126e3. This issue was reported to OpenSSL on 14th January 2017 by Guido Vranken. The fix was developed by Matt Caswell of the OpenSSL development team. BN_mod_exp may produce incorrect results on x86_64 (CVE-2017-3732) ================================================================== Severity: Moderate There is a carry propagating bug in the x86_64 Montgomery squaring procedure. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. For example this can occur by default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very similar to CVE-2015-3193 but must be treated as a separate problem. OpenSSL 1.1.0 users should upgrade to 1.1.0d OpenSSL 1.0.2 users should upgrade to 1.0.2k This issue was reported to OpenSSL on 15th January 2017 by the OSS-Fuzz project. The fix was developed by Andy Polyakov of the OpenSSL development team. Montgomery multiplication may produce incorrect results (CVE-2016-7055) ======================================================================= Severity: Low This issue was previously fixed in 1.1.0c and covered in security advisory https://www.openssl.org/news/secadv/20161110.txt OpenSSL 1.0.2k users should upgrade to 1.0.2k Note ==== Support for version 1.0.1 ended on 31st December 2016. Support for versions 0.9.8 and 1.0.0 ended on 31st December 2015. Those versions are no longer receiving security updates. References ========== URL for this Security Advisory: https://www.openssl.org/news/secadv/20170126.txt Note: the online version of the advisory may be updated with additional details over time. For details of OpenSSL severity classifications please see: https://www.openssl.org/policies/secpolicy.html -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJYifonAAoJENnE0m0OYESRnhYH/1ldFYDEZ894DleZfjRrZulX OQkEH7w6v+D6YFp8i2v6rJaDq8caOPEhzupQCxPcqYitBUnww9UzUvYJ77aBV0CG DQ3UvE9XeEn5D7MGAGq/ut5Z5WpvlYL7n7PaciX751vpTsWTBKfGecQ8YV0aT6y+ 7V7vHz6NVFnuTQDMUYs9C9aTsCDTNy3Bl84d7gYyoDWXUXds5k008g9LFRI4YQ8l +4z+GXRVcvAFr6fKH94Yq1RMAp6cJi0RDkyuwcGhSOUwVfSLTN8+i2v4xqzKgsx1 q2qPo3+7uederE5ZaNZScl0xAzEilotxLQyy9XSVx/DDXHz0in1500qxgxNFELU= =12E/ -----END PGP SIGNATURE-----