<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/Configure, branch OpenSSL_1_1_1j</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_1j</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_1j'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2021-02-16T15:17:22Z</updated>
<entry>
<title>Update copyright year</title>
<updated>2021-02-16T15:17:22Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2021-02-16T15:04:45Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=2b2e3106fc57b810d91221aef4c4c39a8afd97c3'/>
<id>urn:sha1:2b2e3106fc57b810d91221aef4c4c39a8afd97c3</id>
<content type='text'>
Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
</content>
</entry>
<entry>
<title>configdata.pm: Better display of enabled/disabled options</title>
<updated>2021-02-07T06:20:39Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2021-02-05T14:00:17Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=a2a76471ee2ef7ed434fbc51c8e115052dad39e6'/>
<id>urn:sha1:a2a76471ee2ef7ed434fbc51c8e115052dad39e6</id>
<content type='text'>
The options listed in the array @disablables are regular expressions.
For most of them, it's not visible, but there are a few.

However, configdata.pm didn't quite treat them that way, which meant
that the few that are visibly regular expressions, there's a
difference between that and the corresponding the key in %disabled,
which is never a regular expression.

To correctly display the enabled and disabled options with --dump,
we must therefore go through a bit of Perl gymnastics to get the
output correct enough, primarly so that disabled features don't look
enabled.

Fixes #13790

Reviewed-by: Paul Dale &lt;pauli@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/14081)
</content>
</entry>
<entry>
<title>Fix -static builds</title>
<updated>2021-01-14T09:35:16Z</updated>
<author>
<name>Todd Short</name>
<email>tshort@akamai.com</email>
</author>
<published>2020-09-02T20:57:46Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=cfd7225fbb9507b2e443a494459bdaab5236d29d'/>
<id>urn:sha1:cfd7225fbb9507b2e443a494459bdaab5236d29d</id>
<content type='text'>
Pull in check from #10878
Move disabling of pic, threads and statics up higher before they
are checked.

Fixes #12772

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/12773)
</content>
</entry>
<entry>
<title>Configure: Check source and build dir equality a little more thoroughly</title>
<updated>2020-07-02T16:56:33Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2020-07-01T08:06:59Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=a98fa843b8ab00e8f3b966a1f5321aaffe805100'/>
<id>urn:sha1:a98fa843b8ab00e8f3b966a1f5321aaffe805100</id>
<content type='text'>
'absolutedir' does a thorough job ensuring that we have a "real" path
to both source and build directory, unencumbered by symbolic links.
However, that isn't enough on case insensitive file systems on Unix
flavored platforms, where it's possible to stand in, for example,
/PATH/TO/Work/openssl, and then do this:

    perl ../../work/openssl/Configure

... and thereby having it look like the source directory and the build
directory aren't the same.

We solve this by having a closer look at the computed source and build
directories, and making sure they are exactly the same strings if they
are in fact the same directory.

This is especially important when making symbolic links based on this
directories, but may have other ramifications as well.

Fixes #12323

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

(cherry picked from commit 610e2b3b7019b11d97f1dcda13575254a2c65c3d)
</content>
</entry>
<entry>
<title>Fix egd and devrandom source configs</title>
<updated>2020-05-20T12:49:09Z</updated>
<author>
<name>Bernd Edlinger</name>
<email>bernd.edlinger@hotmail.de</email>
</author>
<published>2020-05-17T00:08:56Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=5f10fce37b234807c39d6b1b6440585b84b68b65'/>
<id>urn:sha1:5f10fce37b234807c39d6b1b6440585b84b68b65</id>
<content type='text'>
./config --with-rand-seed=egd

need to defines OPENSSL_RAND_SEED_EGD and OPENSSL_NO_EGD
so get rid of OPENSSL_NO_EGD (compiles but I did not really test EGD)

./config --with-rand-seed=devrandom

does not work since wait_random_seeded works under the assumption
that OPENSSL_RAND_SEED_GETRANDOM is supposed to be enabled as well,
that is usually the case, but not when only devrandom is enabled.
Skip the wait code in this special case.

Reviewed-by: Paul Dale &lt;paul.dale@oracle.com&gt;
(Merged from https://github.com/openssl/openssl/pull/11848)

(cherry picked from commit ddec332f329a432a45c0131d83f3bfb46114532b)
</content>
</entry>
<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>Configure: use $list_separator_re only for defines and includes</title>
<updated>2020-01-13T08:04:19Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2020-01-09T13:49:53Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=5f6343dea1233deb6d762e24e0e0d3d795b9513d'/>
<id>urn:sha1:5f6343dea1233deb6d762e24e0e0d3d795b9513d</id>
<content type='text'>
This regexp was used a bit too uncontrolled, which had it split flag
values where it should not have.

Fixes #10792

Reviewed-by: Paul Dale &lt;paul.dale@oracle.com&gt;
(Merged from https://github.com/openssl/openssl/pull/10793)

(cherry picked from commit bbe486cf6154df3d3aaedbae6c5b82d4ed31a5f8)
</content>
</entry>
<entry>
<title>Configuration: compute openssl_other_defines and related info later</title>
<updated>2019-12-18T18:38:39Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2019-12-04T09:39:24Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=a53a694c575308e1511878f3466e9d01cda6ac3a'/>
<id>urn:sha1:a53a694c575308e1511878f3466e9d01cda6ac3a</id>
<content type='text'>
The computation of macros and configdata.pm related data from %disabled
was done much too early, leaving later disablings without real support.

Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/10565)
</content>
</entry>
<entry>
<title>Disable devcryptoeng on newer OpenBSD versions</title>
<updated>2019-12-18T18:38:39Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2019-12-03T23:10:04Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=2b5827df6d6a4db4e190114a31540b413376b1e5'/>
<id>urn:sha1:2b5827df6d6a4db4e190114a31540b413376b1e5</id>
<content type='text'>
It's reported that /dev/crypto support has been dropped in OpenBSD 5.7.

Fixes #10552

Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/10565)
</content>
</entry>
<entry>
<title>Configure: Make --strict-warnings meaningful with MSVC cl</title>
<updated>2019-11-05T21:51:12Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2019-10-29T12:37:54Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=53a5e9b561d0cc1c1c9a7ab9b0dbc91dd5e3623a'/>
<id>urn:sha1:53a5e9b561d0cc1c1c9a7ab9b0dbc91dd5e3623a</id>
<content type='text'>
We also add this to our x86_64 builds on appveyor

(cherry picked from commit b4a7b4ec4acc712b1f22a83966ac986b510f25d8)

Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/10365)
</content>
</entry>
</feed>
