<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/util/wrap.pl.in, branch dependabot/github_actions/actions/setup-python-7</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=dependabot%2Fgithub_actions%2Factions%2Fsetup-python-7</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=dependabot%2Fgithub_actions%2Factions%2Fsetup-python-7'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2026-02-19T08:49:54Z</updated>
<entry>
<title>Fix unit tests when run under fuzz builds</title>
<updated>2026-02-19T08:49:54Z</updated>
<author>
<name>Neil Horman</name>
<email>nhorman@openssl.org</email>
</author>
<published>2026-02-18T19:35:22Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=619a0fe71825e1f9c4fb7d3a67f8b6a227386e36'/>
<id>urn:sha1:619a0fe71825e1f9c4fb7d3a67f8b6a227386e36</id>
<content type='text'>
PR https://github.com/openssl/openssl/pull/30045

Fixed an oss-fuzz failure that occured because we feed random data into
the pkcs12 kdf, which sometimes results in a huge iteration count, that
leads to timeouts in oss-fuzz.

The fix was to simply limit the number of iterations that we go through
during derivation.  This breaks the kdf of course, but it doesn't really
matter during fuzzing, because we don't expect random input data to
produce reasonable results, so no harm, no foul.

except.

We also, in our CI, build our fuzzer tests and run them through our
regular CI unit tests, during which we both provide valid data, and
expect valid results, and pr 30045 breaks that expectation.

The conventional wisdom is to simply skip unit tests that break under
these sorts of conditions (we do this for things like
70-test_quic_record.t already).

however, the tests that broke here are 25_test_x509, 30_test_evp,
80_test_pkcs12, and 90_test_store_cases.  It seems like we would want to
keep testing those unless we absolutely have to skip them.

So instead, lets indicate that we are running the unit tests with an
environment variable, and check that variable when we have an
UNSAFE_FOR_PRODUCTION build, skiping the iteration clamp in pkcs12kdf if
it is.  This allows us to continue running these unit tests, while still
getting the oss-fuzz runs to pass.

Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Reviewed-by: Norbert Pocs &lt;norbertp@openssl.org&gt;
MergeDate: Thu Feb 19 08:49:56 2026
(Merged from https://github.com/openssl/openssl/pull/30070)
</content>
</entry>
<entry>
<title>Clear util dir from engines</title>
<updated>2025-12-04T12:32:18Z</updated>
<author>
<name>Norbert Pocs</name>
<email>norbertp@openssl.org</email>
</author>
<published>2025-11-20T16:59:16Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=9626fb450977cc9bf57c7a13d2fce2ac1f5b7ec0'/>
<id>urn:sha1:9626fb450977cc9bf57c7a13d2fce2ac1f5b7ec0</id>
<content type='text'>
Signed-off-by: Norbert Pocs &lt;norbertp@openssl.org&gt;

Reviewed-by: Paul Yang &lt;paulyang.inf@gmail.com&gt;
Reviewed-by: Eugene Syromiatnikov &lt;esyr@openssl.org&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Reviewed-by: Saša Nedvědický &lt;sashan@openssl.org&gt;
Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/29305)
</content>
</entry>
<entry>
<title>Split arguments taking quotes into account</title>
<updated>2025-06-04T15:33:48Z</updated>
<author>
<name>Viktor Dukhovni</name>
<email>openssl-users@dukhovni.org</email>
</author>
<published>2025-06-01T02:47:15Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=287bbb28b09e930a8691efc92a5087bb951edb6b'/>
<id>urn:sha1:287bbb28b09e930a8691efc92a5087bb951edb6b</id>
<content type='text'>
CA.pl supports interpolating multiple arguments into the executed
commands.  Previously these were evaluated by a shell, which supported
quoting of values that contain whitespace, backslashes, ...

With a shell no longer used (avoid command injection), backwards
compatibility requires some similar functionality.  The code now handles
double and single-quoted strings (shell-style word splitting), but not
parameter expansion ($foo remains unexpanded) or command substitution
(`cmd` and $(cmd) remain unexpanded).

On Windows system(@LIST) does not correctly preserve argv, do our
own quoting instead and use system(&lt;$quoted_cmd&gt;).

Reviewed-by: Tom Cosgrove &lt;tom.cosgrove@arm.com&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/27432)
</content>
</entry>
<entry>
<title>jitter: add a new provider containing a jitter entropy source alone</title>
<updated>2024-07-31T04:44:51Z</updated>
<author>
<name>Dimitri John Ledkov</name>
<email>dimitri.ledkov@surgut.co.uk</email>
</author>
<published>2024-07-10T14:39:01Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=b28b3128048a83ba036c9d8a789badac9b1a2804'/>
<id>urn:sha1:b28b3128048a83ba036c9d8a789badac9b1a2804</id>
<content type='text'>
This entropy source can be used instead of SEED-SRC. Sample
openssl.cnf configuration is provided. It is built as a separate
provider, because it is likely to require less frequent updates than
fips provider. The same build likely can span multiple generations of
FIPS 140 standard revisions.

Note that rand-instances currently chain from public/private instances
to primary, prior to consuming the seed. Thus currently a unique ESV
needs to be obtained, and resue of jitterentropy.a certificate is not
possible as is. Separately a patch will be sent to allow for
unchaining public/private RAND instances for the purpose of reusing
ESV.

Also I do wonder if it makes sense to create a fips variant of stock
SEED-SRC entropy source, which in addition to using getrandom() also
verifies that the kernel is operating in FIPS mode and thus is likely
a validated entropy source. As in on Linux, check that
/proc/sys/crypto/fips_enabled is set to 1, and similar checks on
Windows / MacOS and so on.

Reviewed-by: Shane Lontis &lt;shane.lontis@oracle.com&gt;
Reviewed-by: Paul Dale &lt;pauli@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/24844)
</content>
</entry>
<entry>
<title>Fix util/wrap.pl.in for VMS usage</title>
<updated>2023-03-08T11:29:22Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2023-03-01T15:27:50Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=1939ee7f252ffebd91c29384db4133290489e026'/>
<id>urn:sha1:1939ee7f252ffebd91c29384db4133290489e026</id>
<content type='text'>
In the name of consistency, make sure that this same script is used
across more platforms, in this case VMS.  This removes the need for
util/local_shlib.com.in and util/unlocal_shlib.com.in, which were
under-used anyway.

Reviewed-by: Dmitry Belyavskiy &lt;beldmit@gmail.com&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/20415)
</content>
</entry>
<entry>
<title>util/wrap.pl.in: Use parentheses so `kill` gets all its arguments</title>
<updated>2022-09-15T06:42:23Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2022-09-14T05:07:41Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=ef6d6e452dc57ef4a55d7a6ec0693be650009bb5'/>
<id>urn:sha1:ef6d6e452dc57ef4a55d7a6ec0693be650009bb5</id>
<content type='text'>
In perl, this may be ambiguous:

    fn (expr1), expr2

Is the comma (which may be `=&gt;` just as well in this case) a separator
between arguments to `fn`, or is it the comma operator, separating the
expressions `fn(expr1)` and `expr2`?  It appears that in this particular
case, perl takes the existing parentheses to mean the latter.  When the
former was intended, extra parentheses are required.

Fixes #19209

Reviewed-by: Dmitry Belyavskiy &lt;beldmit@gmail.com&gt;
Reviewed-by: Paul Dale &lt;pauli@openssl.org&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/19211)
</content>
</entry>
<entry>
<title>util/wrap.pl.in: If the subprocess died with a signal, let's re-signal it</title>
<updated>2022-08-23T23:35:39Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2022-08-22T16:40:54Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=bf16ee4f95c31a66e76056c691f25a0d2b4a39c4'/>
<id>urn:sha1:bf16ee4f95c31a66e76056c691f25a0d2b4a39c4</id>
<content type='text'>
A simple 'kill' of the same signal on our own process should do it.
This will allow the shell that this is running under to catch it
properly, and output something if it usually does that.

Fixes #19041

Reviewed-by: Dmitry Belyavskiy &lt;beldmit@gmail.com&gt;
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
Reviewed-by: Paul Dale &lt;pauli@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/19042)
</content>
</entry>
<entry>
<title>util: add -fips option to wrap.pl to make using the FIPS provider easier</title>
<updated>2021-07-06T08:14:08Z</updated>
<author>
<name>Pauli</name>
<email>pauli@openssl.org</email>
</author>
<published>2021-07-01T02:48:30Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=4e20d04ee0e7be2061c1e5d2c2c8d714b7923c89'/>
<id>urn:sha1:4e20d04ee0e7be2061c1e5d2c2c8d714b7923c89</id>
<content type='text'>
Without this option, I find I need to figure out which environment variables
point where which wastes effort.

Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/15966)
</content>
</entry>
<entry>
<title>Make util/wrap.pl work better on VMS</title>
<updated>2021-06-18T07:08:16Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2021-06-16T08:32:43Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=0eed845ce2d76a1f2d8882cb32e1d36c30236d5e'/>
<id>urn:sha1:0eed845ce2d76a1f2d8882cb32e1d36c30236d5e</id>
<content type='text'>
Perl's system() on VMS needs to have the command line properly fixed
up, even with arguments passed in list form.  We arrange that by
having util/wrap.pl use the same command line fixups as OpenSSL::Test.

As a consequence, util/wrap.pl needs to be generated, to easily pick
up data from configdata.pm.  This also removes yet another file
copying hack from the build file templates.

Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/15791)
</content>
</entry>
</feed>
