<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl, branch OpenSSL_1_0_2k</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_0_2k</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_0_2k'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2017-01-26T13:22:36Z</updated>
<entry>
<title>Prepare for 1.0.2k release</title>
<updated>2017-01-26T13:22:36Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2017-01-26T13:22:36Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=081314d07705aa58912845c213a48414d8f616a9'/>
<id>urn:sha1:081314d07705aa58912845c213a48414d8f616a9</id>
<content type='text'>
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
</content>
</entry>
<entry>
<title>Update CHANGES and NEWS for new release</title>
<updated>2017-01-26T11:02:44Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2017-01-24T16:34:40Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=06f87e9685bb2faa033f682aa66b70059e398f71'/>
<id>urn:sha1:06f87e9685bb2faa033f682aa66b70059e398f71</id>
<content type='text'>
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
</content>
</entry>
<entry>
<title>Better check of DH parameters in TLS data</title>
<updated>2017-01-26T10:56:29Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2017-01-26T10:47:36Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=918d8eadb35746456fd1a9d4e219c63ff706173e'/>
<id>urn:sha1:918d8eadb35746456fd1a9d4e219c63ff706173e</id>
<content type='text'>
When the client reads DH parameters from the TLS stream, we only
checked that they all are non-zero.  This change updates the check
as follows:

    check that p is odd
    check that 1 &lt; g &lt; p - 1

Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
</content>
</entry>
<entry>
<title>bn/asm/x86_64-mont5.pl: fix carry bug in bn_sqr8x_internal.</title>
<updated>2017-01-26T10:55:03Z</updated>
<author>
<name>Andy Polyakov</name>
<email>appro@openssl.org</email>
</author>
<published>2017-01-21T20:30:49Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=760d04342a495ee86bf5adc71a91d126af64397f'/>
<id>urn:sha1:760d04342a495ee86bf5adc71a91d126af64397f</id>
<content type='text'>
CVE-2017-3732

Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
</content>
</entry>
<entry>
<title>crypto/evp: harden RC4_MD5 cipher.</title>
<updated>2017-01-26T10:55:03Z</updated>
<author>
<name>Andy Polyakov</name>
<email>appro@openssl.org</email>
</author>
<published>2017-01-18T23:17:30Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=51d009043670a627d6abe66894126851cf3690e9'/>
<id>urn:sha1:51d009043670a627d6abe66894126851cf3690e9</id>
<content type='text'>
Originally a crash in 32-bit build was reported CHACHA20-POLY1305
cipher. The crash is triggered by truncated packet and is result
of excessive hashing to the edge of accessible memory (or bogus
MAC value is produced if x86 MD5 assembly module is involved). Since
hash operation is read-only it is not considered to be exploitable
beyond a DoS condition.

Thanks to Robert Święcki for report.

CVE-2017-3731

Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
</content>
</entry>
<entry>
<title>Fix error handling in compute_key, BN_CTX_get can return NULL</title>
<updated>2017-01-24T17:27:10Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2016-12-22T12:51:27Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=8957adda165f77589090627d6563796331c0c94b'/>
<id>urn:sha1:8957adda165f77589090627d6563796331c0c94b</id>
<content type='text'>
Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/2132)
(cherry picked from commit 7928ee4d685b727619555bc1ec0aee805f6fc8c4)
</content>
</entry>
<entry>
<title>Fix a ssl session leak due to OOM in lh_SSL_SESSION_insert</title>
<updated>2017-01-24T14:07:33Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2016-12-22T19:17:29Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=cb00d4ff17eae9c4e489409f5d12bff76c110be1'/>
<id>urn:sha1:cb00d4ff17eae9c4e489409f5d12bff76c110be1</id>
<content type='text'>
- s == NULL can mean c is a new session *or* lh_insert was
  unable to create a hash entry.
- use lh_SSL_SESSION_retrieve to check for this error condition.
- If it happens simply remove the extra reference again.

Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/2138)
(cherry picked from commit 38088ce9934a90d4aea486edbff864f3935342e6)
</content>
</entry>
<entry>
<title>Fix SSL_VERIFY_CLIENT_ONCE</title>
<updated>2017-01-23T14:13:14Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2016-11-22T17:37:34Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=e203f493f6387ab14c3b4d9c1b668e9d199e8ec3'/>
<id>urn:sha1:e203f493f6387ab14c3b4d9c1b668e9d199e8ec3</id>
<content type='text'>
The flag SSL_VERIFY_CLIENT_ONCE is documented as follows:

  B&lt;Server mode:&gt; only request a client certificate on the initial TLS/SSL
  handshake. Do not ask for a client certificate again in case of a
  renegotiation. This flag must be used together with SSL_VERIFY_PEER.

  B&lt;Client mode:&gt; ignored

But the implementation actually did nothing. After the server sends its
ServerKeyExchange message, the code was checking s-&gt;session-&gt;peer to see if
it is NULL. If it was set then it did not ask for another client
certificate. However s-&gt;session-&gt;peer will only be set in the event of a
resumption, but a ServerKeyExchange message is only sent in the event of a
full handshake (i.e. no resumption).

The documentation suggests that the original intention was for this to
have an effect on renegotiation, and resumption doesn't come into it.

The fix is to properly check for renegotiation, not whether there is already
a client certificate in the session.

As far as I can tell this has been broken for a *long* time.

Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/1984)</content>
</entry>
<entry>
<title>Add missing va_end</title>
<updated>2017-01-20T18:37:52Z</updated>
<author>
<name>Rich Salz</name>
<email>rsalz@openssl.org</email>
</author>
<published>2017-01-20T18:37:52Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=149e98dc5fe9ef172d12f329292e9d356705b646'/>
<id>urn:sha1:149e98dc5fe9ef172d12f329292e9d356705b646</id>
<content type='text'>
Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/2267)</content>
</entry>
<entry>
<title>Fix DSA parameter generation control error</title>
<updated>2017-01-20T07:30:41Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2017-01-18T15:19:26Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=16f013fa709b283b53ffd1b665f395137623f9f0'/>
<id>urn:sha1:16f013fa709b283b53ffd1b665f395137623f9f0</id>
<content type='text'>
When setting the digest parameter for DSA parameter generation, the
signature MD was set instead of the parameter generation one.
Fortunately, that's also the one that was used for parameter
generation, but it ultimately meant the parameter generator MD and the
signature MD would always be the same.

Fixes github issue #2016

Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/2250)
(cherry picked from commit 8a05c4d3b5a1bfb9193ea24e71735e11de7168d2)
</content>
</entry>
</feed>
