<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/crypto, branch OpenSSL_1_1_1e</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_1e</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_1e'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2020-03-17T13:59:29Z</updated>
<entry>
<title>Update copyright year</title>
<updated>2020-03-17T13:59:29Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2020-03-17T13:59:29Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=e7ff223a20697e5a401d2d9bb7a75e699ed46633'/>
<id>urn:sha1:e7ff223a20697e5a401d2d9bb7a75e699ed46633</id>
<content type='text'>
Reviewed-by: Paul Yang &lt;kaishen.yy@antfin.com&gt;
(Merged from https://github.com/openssl/openssl/pull/11344)
</content>
</entry>
<entry>
<title>Code to thread-safety in ChangeCipherState</title>
<updated>2020-03-13T23:11:45Z</updated>
<author>
<name>Benjamin Kaduk</name>
<email>bkaduk@akamai.com</email>
</author>
<published>2020-01-24T21:44:27Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=44bad9cbf7daa5ff7dd201e0c61e684b2e2eb971'/>
<id>urn:sha1:44bad9cbf7daa5ff7dd201e0c61e684b2e2eb971</id>
<content type='text'>
The server-side ChangeCipherState processing stores the new cipher
in the SSL_SESSION object, so that the new state can be used if
this session gets resumed.  However, writing to the session is only
thread-safe for initial handshakes, as at other times the session
object may be in a shared cache and in use by another thread at the
same time.  Reflect this invariant in the code by only writing to
s-&gt;session-&gt;cipher when it is currently NULL (we do not cache sessions
with no cipher).  The code prior to this change would never actually
change the (non-NULL) cipher value in a session object, since our
server enforces that (pre-TLS-1.3) resumptions use the exact same
cipher as the initial connection, and non-abbreviated renegotiations
have produced a new session object before we get to this point.
Regardless, include logic to detect such a condition and abort the
handshake if it occurs, to avoid any risk of inadvertently using
the wrong cipher on a connection.

Reviewed-by: Tomas Mraz &lt;tmraz@fedoraproject.org&gt;
(Merged from https://github.com/openssl/openssl/pull/10943)

(cherry picked from commit 2e3ec2e1578977fca830a47fd7f521e290540e6d)
</content>
</entry>
<entry>
<title>Revert "Stop accepting certificates signed using SHA1 at security level 1"</title>
<updated>2020-03-11T14:56:05Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2020-03-09T09:05:27Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=63fa6f2e4ba7641fd5f10c70eaa0c3a4b42e124c'/>
<id>urn:sha1:63fa6f2e4ba7641fd5f10c70eaa0c3a4b42e124c</id>
<content type='text'>
This reverts commit 68436f0a8964e911eb4f864bc8b31d7ca4d29585.

The OMC did not vote in favour of backporting this to 1.1.1, so this
change should be reverted.

Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/11282)
</content>
</entry>
<entry>
<title>crypto/ec/curve448/eddsa.c: fix EBCDIC platforms</title>
<updated>2020-03-05T16:33:35Z</updated>
<author>
<name>Patrick Steuer</name>
<email>patrick.steuer@de.ibm.com</email>
</author>
<published>2020-03-03T12:29:03Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=ded6741604e7f622dc278f6b24c0b47432b75325'/>
<id>urn:sha1:ded6741604e7f622dc278f6b24c0b47432b75325</id>
<content type='text'>
Signed-off-by: Patrick Steuer &lt;patrick.steuer@de.ibm.com&gt;

Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/11229)

(cherry picked from commit af7f656cd91d99d62567e2b20c61f07cb4d81d0b)
</content>
</entry>
<entry>
<title>aes-s390x.pl: fix stg offset caused by typo in perlasm</title>
<updated>2020-03-05T16:24:43Z</updated>
<author>
<name>Patrick Steuer</name>
<email>patrick.steuer@de.ibm.com</email>
</author>
<published>2020-03-03T16:40:07Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=1d5359316949b9320f73ec74ec619714e356d716'/>
<id>urn:sha1:1d5359316949b9320f73ec74ec619714e356d716</id>
<content type='text'>
Signed-off-by: Patrick Steuer &lt;patrick.steuer@de.ibm.com&gt;

Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/11234)

(cherry picked from commit 7b2ce4a6e817e4385ff77fea0c6e349294c7b756)
</content>
</entry>
<entry>
<title>This works around a gcc-9 crash</title>
<updated>2020-03-05T15:04:36Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2020-03-04T10:42:17Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=bf42b99ed4057e1877f72a0c2e7b445f5ee5d750'/>
<id>urn:sha1:bf42b99ed4057e1877f72a0c2e7b445f5ee5d750</id>
<content type='text'>
It happens when configured with ./config -ftest-coverage

see: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94029

Reviewed-by: Tomas Mraz &lt;tmraz@fedoraproject.org&gt;
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/11246)
</content>
</entry>
<entry>
<title>Fix comment placement in ecp_nistp256.ci</title>
<updated>2020-02-27T23:41:26Z</updated>
<author>
<name>Scott Arciszewski</name>
<email>58194612+scottarc@users.noreply.github.com</email>
</author>
<published>2020-02-24T20:29:12Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=93c50f46809bc0bd6c39e8445a4140c034a4320d'/>
<id>urn:sha1:93c50f46809bc0bd6c39e8445a4140c034a4320d</id>
<content type='text'>
CLA: trivial

Reviewed-by: Shane Lontis &lt;shane.lontis@oracle.com&gt;
Reviewed-by: Matthias St. Pierre &lt;Matthias.St.Pierre@ncp-e.com&gt;
(Merged from https://github.com/openssl/openssl/pull/11175)

(cherry picked from commit c590be6f12d0b725863961e41bc64a81c8cf30d6)
</content>
</entry>
<entry>
<title>Teach more BIOs how to handle BIO_CTRL_EOF</title>
<updated>2020-02-20T17:02:31Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2020-01-24T16:07:51Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=22623e0cc26a11908253206a721873d4101cd466'/>
<id>urn:sha1:22623e0cc26a11908253206a721873d4101cd466</id>
<content type='text'>
Reviewed-by: Tomas Mraz &lt;tmraz@fedoraproject.org&gt;
Reviewed-by: Dmitry Belyavskiy &lt;beldmit@gmail.com&gt;
(Merged from https://github.com/openssl/openssl/pull/10882)
</content>
</entry>
<entry>
<title>Detect EOF while reading in libssl</title>
<updated>2020-02-20T17:02:30Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2020-01-17T17:39:19Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=db943f43a60d1b5b1277e4b5317e8f288e7a0a3a'/>
<id>urn:sha1:db943f43a60d1b5b1277e4b5317e8f288e7a0a3a</id>
<content type='text'>
If we hit an EOF while reading in libssl then we will report an error
back to the application (SSL_ERROR_SYSCALL) but errno will be 0. We add
an error to the stack (which means we instead return SSL_ERROR_SSL) and
therefore give a hint as to what went wrong.

Contains a partial fix for #10880

Reviewed-by: Tomas Mraz &lt;tmraz@fedoraproject.org&gt;
Reviewed-by: Dmitry Belyavskiy &lt;beldmit@gmail.com&gt;
(Merged from https://github.com/openssl/openssl/pull/10882)
</content>
</entry>
<entry>
<title>Do not silently truncate files on perlasm errors</title>
<updated>2020-02-17T02:21:27Z</updated>
<author>
<name>David Benjamin</name>
<email>davidben@google.com</email>
</author>
<published>2020-02-17T02:21:27Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=218e740f850f77c9f2720d56886eab166d1a6727'/>
<id>urn:sha1:218e740f850f77c9f2720d56886eab166d1a6727</id>
<content type='text'>
If one of the perlasm xlate drivers crashes, OpenSSL's build will
currently swallow the error and silently truncate the output to however
far the driver got. This will hopefully fail to build, but better to
check such things.

Handle this by checking for errors when closing STDOUT (which is a pipe
to the xlate driver).

This is the OpenSSL 1.1.1 version of
https://github.com/openssl/openssl/pull/10883 and
https://github.com/openssl/openssl/pull/10930.

Reviewed-by: Mark J. Cox &lt;mark@awe.com&gt;
Reviewed-by: Paul Dale David Benjamin &lt;davidben@google.com&gt;
(Merged from https://github.com/openssl/openssl/pull/10931)
</content>
</entry>
</feed>
