<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/include/internal, 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>2019-09-27T21:58:12Z</updated>
<entry>
<title>Fix header file include guard names</title>
<updated>2019-09-27T21:58:12Z</updated>
<author>
<name>Dr. Matthias St. Pierre</name>
<email>Matthias.St.Pierre@ncp-e.com</email>
</author>
<published>2019-09-27T21:58:12Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=fbbfd128c9aa884216ace8c63be9071b3b690bee'/>
<id>urn:sha1:fbbfd128c9aa884216ace8c63be9071b3b690bee</id>
<content type='text'>
Make the include guards consistent by renaming them systematically according
to the naming conventions below

The public header files (in the 'include/openssl' directory) are not changed
in 1.1.1, because it is a stable release.

For the private header files files, the guard names try to match the path
specified in the include directives, with all letters converted to upper case
and '/' and '.' replaced by '_'. An extra 'OSSL_' is added as prefix.

Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/9681)
</content>
</entry>
<entry>
<title>Reorganize local header files</title>
<updated>2019-09-27T21:58:06Z</updated>
<author>
<name>Dr. Matthias St. Pierre</name>
<email>Matthias.St.Pierre@ncp-e.com</email>
</author>
<published>2019-09-27T21:58:06Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=b5acbf914833a83368e51766de4cf2e2074a9436'/>
<id>urn:sha1:b5acbf914833a83368e51766de4cf2e2074a9436</id>
<content type='text'>
Apart from public and internal header files, there is a third type called
local header files, which are located next to source files in the source
directory. Currently, they have different suffixes like

  '*_lcl.h', '*_local.h', or '*_int.h'

This commit changes the different suffixes to '*_local.h' uniformly.

Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/9681)
</content>
</entry>
<entry>
<title>Update copyright year</title>
<updated>2019-09-10T12:56:40Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2019-09-10T12:56:40Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=1cb7eff45b4a213f216c779c291d8622f9a84170'/>
<id>urn:sha1:1cb7eff45b4a213f216c779c291d8622f9a84170</id>
<content type='text'>
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/9847)
</content>
</entry>
<entry>
<title>drbg: ensure fork-safety without using a pthread_atfork handler</title>
<updated>2019-09-09T16:09:06Z</updated>
<author>
<name>Dr. Matthias St. Pierre</name>
<email>Matthias.St.Pierre@ncp-e.com</email>
</author>
<published>2019-05-27T19:03:09Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=1b0fe00e2704b5e20334a16d3c9099d1ba2ef1be'/>
<id>urn:sha1:1b0fe00e2704b5e20334a16d3c9099d1ba2ef1be</id>
<content type='text'>
When the new OpenSSL CSPRNG was introduced in version 1.1.1,
it was announced in the release notes that it would be fork-safe,
which the old CSPRNG hadn't been.

The fork-safety was implemented using a fork count, which was
incremented by a pthread_atfork handler. Initially, this handler
was enabled by default. Unfortunately, the default behaviour
had to be changed for other reasons in commit b5319bdbd095, so
the new OpenSSL CSPRNG failed to keep its promise.

This commit restores the fork-safety using a different approach.
It replaces the fork count by a fork id, which coincides with
the process id on UNIX-like operating systems and is zero on other
operating systems. It is used to detect when an automatic reseed
after a fork is necessary.

To prevent a future regression, it also adds a test to verify that
the child reseeds after fork.

CVE-2019-1549

Reviewed-by: Paul Dale &lt;paul.dale@oracle.com&gt;
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/9802)
</content>
</entry>
<entry>
<title>Fix Typos</title>
<updated>2019-07-31T17:48:30Z</updated>
<author>
<name>Antoine Cœur</name>
<email>coeur@gmx.fr</email>
</author>
<published>2019-07-02T14:29:29Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=a5c83db4ae3b3a94cdb88658280c36b6a74377ef'/>
<id>urn:sha1:a5c83db4ae3b3a94cdb88658280c36b6a74377ef</id>
<content type='text'>
CLA: trivial

Reviewed-by: Paul Dale &lt;paul.dale@oracle.com&gt;
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/9295)
</content>
</entry>
<entry>
<title>Add value_barriers in constant time select functions</title>
<updated>2019-07-18T14:02:20Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2019-06-21T19:26:19Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=7fab4310409189767e86b9d2f5fa6d3fa3fd6270'/>
<id>urn:sha1:7fab4310409189767e86b9d2f5fa6d3fa3fd6270</id>
<content type='text'>
The barriers prevent the compiler from narrowing down the
possible value range of the mask and ~mask in the select
statements, which avoids the recognition of the select
and turning it into a conditional load or branch.

Reviewed-by: Tomas Mraz &lt;tmraz@fedoraproject.org&gt;
Reviewed-by: Kurt Roeckx &lt;kurt@roeckx.be&gt;
(Merged from https://github.com/openssl/openssl/pull/9217)

(cherry picked from commit 04edd688b3727835f9b2c7cca7e4c963bf3ed2ba)
</content>
</entry>
<entry>
<title>Fix a C++ comment in the refcount.h</title>
<updated>2019-07-17T12:17:45Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2019-07-15T19:10:59Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=8d64f00fd91f83e36017d7517c9e6d9fd98f6237'/>
<id>urn:sha1:8d64f00fd91f83e36017d7517c9e6d9fd98f6237</id>
<content type='text'>
Although in a false-conditional code section gcc-4.8.4 flagged this with
a C90 warning :-(

include/internal/refcount.h:108:7: error: C++ style comments are not allowed in ISO C90 [-Werror]
       // under Windows CE we still have old-style Interlocked* functions

Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/9388)
</content>
</entry>
<entry>
<title>Add regenerated header files</title>
<updated>2019-07-02T08:06:15Z</updated>
<author>
<name>Dr. Matthias St. Pierre</name>
<email>Matthias.St.Pierre@ncp-e.com</email>
</author>
<published>2019-07-01T15:57:35Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=3003d2dba996d16e47c8bc70a23c70b3d394fb7c'/>
<id>urn:sha1:3003d2dba996d16e47c8bc70a23c70b3d394fb7c</id>
<content type='text'>
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
Reviewed-by: Nicola Tuveri &lt;nic.tuv@gmail.com&gt;
(Merged from https://github.com/openssl/openssl/pull/9281)
</content>
</entry>
<entry>
<title>Update copyright year</title>
<updated>2019-05-28T12:49:38Z</updated>
<author>
<name>Richard Levitte</name>
<email>richard@levitte.org</email>
</author>
<published>2019-05-28T12:49:38Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=35fd99538aada41d28955c1d20ca289693448e70'/>
<id>urn:sha1:35fd99538aada41d28955c1d20ca289693448e70</id>
<content type='text'>
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/9034)
</content>
</entry>
<entry>
<title>Rework DSO API conditions and configuration option</title>
<updated>2019-04-10T05:50:17Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2019-04-01T04:40:33Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=5fba3afad01707f4a8856a35500de007a8a256ec'/>
<id>urn:sha1:5fba3afad01707f4a8856a35500de007a8a256ec</id>
<content type='text'>
'no-dso' is meaningless, as it doesn't get any macro defined.
Therefore, we remove all checks of OPENSSL_NO_DSO.  However, there may
be some odd platforms with no DSO scheme.  For those, we generate the
internal macro DSO_NONE aand use it.

Reviewed-by: Paul Dale &lt;paul.dale@oracle.com&gt;
(Merged from https://github.com/openssl/openssl/pull/8622)
</content>
</entry>
</feed>
