<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/util/perl, 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-07-23T15:55:07Z</updated>
<entry>
<title>Reject unknown TLS 1.3 ServerHello extensions</title>
<updated>2026-07-23T15:55:07Z</updated>
<author>
<name>Mounir IDRASSI</name>
<email>mounir.idrassi@idrix.fr</email>
</author>
<published>2026-05-05T10:30:49Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=3e4f7e77208138174ce50f0403ce6b947cb1d509'/>
<id>urn:sha1:3e4f7e77208138174ce50f0403ce6b947cb1d509</id>
<content type='text'>
TLS 1.3 does not permit clients to ignore unknown extensions in ServerHello
or HelloRetryRequest. Add a validation pass for these messages so fully
unknown extension types fail early with unsupported_extension.

Keep the existing ignore behavior for other extension contexts and leave
TLS 1.2 ServerHello processing unchanged. Add TLSProxy coverage for the
TLS 1.3 ServerHello case.

Correct the unknown-extension path in tls_collect_extensions(). Collection
still runs before the new TLS 1.3 validation, and verify_extension()
returns success with thisex == NULL for fully unknown extension types.
The previous idx calculation used invalid pointer arithmetic on NULL in
that path. Map unknown extensions explicitly outside the built-in extension
range instead, preserving the existing ignore semantics while avoiding
undefined behavior.

Update the truncated HRR ECH corruption vector to keep testing malformed
ECH length after the new unknown-extension validation. The old 0xdddd bytes
were only padding to preserve the replacement length, but they now trigger
the unknown-extension check before the ECH parser. Use a known HRR cookie
extension as padding so the test still reaches the intended
SSL_R_LENGTH_MISMATCH path.

Reviewed-by: Andrew Dinh &lt;andrewd@openssl.org&gt;
Reviewed-by: Daniel Kubec &lt;kubec@openssl.foundation&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.foundation&gt;
MergeDate: Thu Jul 23 15:55:09 2026
(Merged from https://github.com/openssl/openssl/pull/31086)
</content>
</entry>
<entry>
<title>test: include PID in valgrind log file names</title>
<updated>2026-07-20T09:06:53Z</updated>
<author>
<name>Nikola Pajkovsky</name>
<email>nikolap@openssl.org</email>
</author>
<published>2026-07-15T07:51:51Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=d00cf645c1d631299843d7dda3a21f24ef5848f8'/>
<id>urn:sha1:d00cf645c1d631299843d7dda3a21f24ef5848f8</id>
<content type='text'>
Append the %p (process ID) placeholder to valgrind's --log-file in
both app() and test(). When a test spawns multiple processes sharing
the same result index, they previously wrote to the same log file and
clobbered each other's output. Using %p gives each process its own
log, so no valgrind findings are lost.

Signed-off-by: Nikola Pajkovsky &lt;nikolap@openssl.org&gt;

Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
Reviewed-by: Paul Dale &lt;paul.dale@oracle.com&gt;
Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
MergeDate: Mon Jul 20 09:07:07 2026
(Merged from https://github.com/openssl/openssl/pull/31961)
</content>
</entry>
<entry>
<title>test: don't depend on DTLS alert delivery in sslrecords test</title>
<updated>2026-07-18T12:53:09Z</updated>
<author>
<name>Jakub Zelenka</name>
<email>jakub.zelenka@openssl.foundation</email>
</author>
<published>2026-07-12T13:02:35Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=d8bf6cdd4849925c30e4f1911c7acb49cb34b702'/>
<id>urn:sha1:d8bf6cdd4849925c30e4f1911c7acb49cb34b702</id>
<content type='text'>
The unknown-record-type tests (tests 5 and 6) inferred failure of a DTLS
connection from TLSProxy's socket-teardown timing ($proxy_start_success == 0).
This relied on the client's fatal alert reaching the peer before the client
closes its socket, which is a race: DTLS alerts are best-effort and are never
retransmitted (RFC 6347 section 4.2.7 / RFC 9147 section 5.10), and after the
s_client shutdown drain was skipped for datagram protocols the alert can be
lost during teardown, making the test flaky.

Verify instead what is actually under test: that the DTLS client rejected the
unrecognised record type, i.e. that s_client exited with a failure. This is a
deterministic, local decision that does not depend on the alert being observed
by the peer. Keep the alert observation as a best-effort diagnostic note.

Capture the s_client exit status in TLSProxy (previously discarded after
waitpid) and expose it via a new clientexit accessor.

Assisted-by: Claude:claude-opus-4-8

Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.foundation&gt;
MergeDate: Sat Jul 18 12:53:26 2026
(Merged from https://github.com/openssl/openssl/pull/31927)
</content>
</entry>
<entry>
<title>Integrate mfail functionality to fuzz tests</title>
<updated>2026-07-15T16:01:30Z</updated>
<author>
<name>Jakub Zelenka</name>
<email>jakub.zelenka@openssl.foundation</email>
</author>
<published>2026-04-28T17:22:46Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=dca561d4cdb84c7e813e9b28352928edd5b2cfd8'/>
<id>urn:sha1:dca561d4cdb84c7e813e9b28352928edd5b2cfd8</id>
<content type='text'>
Run the fuzz corpora under mfail in addition to the normal path, so the
existing inputs also exercise malloc-failure handling. The fuzz.pl harness
sizes the mfail runs to a time budget and, on a leak, bisects down to the
exact file and injection point. Adds a budgeted asan/ubsan CI job to run it.

Assisted-by: Claude:claude-opus-4-6

Reviewed-by: Nikola Pajkovsky &lt;nikolap@openssl.org&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.foundation&gt;
MergeDate: Wed Jul 15 16:01:43 2026
(Merged from https://github.com/openssl/openssl/pull/30944)
</content>
</entry>
<entry>
<title>Drop Windows-on-Itanium (VC-WIN64I) support.</title>
<updated>2026-07-10T17:39:24Z</updated>
<author>
<name>Bob Beck</name>
<email>beck@openssl.org</email>
</author>
<published>2026-06-18T20:58:39Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=10b5f9f8978cb4721b195bda93d0acbcb525e053'/>
<id>urn:sha1:10b5f9f8978cb4721b195bda93d0acbcb525e053</id>
<content type='text'>
Similar to Windows CE, Windows Itanium has not had a
toolchain to work on it since VS 2010, and Windows
server 2008 was the last thing that ran on it.

This does *not* change the other (linux, HPUX) targets
which have modern toolchain support, and likely even still
run these days.

While never letting go seems noble when you won't share
the door you're floating on, the time has come.

Reviewed-by: Milan Broz &lt;mbroz@openssl.org&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.foundation&gt;
Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
MergeDate: Fri Jul 10 17:39:39 2026
(Merged from https://github.com/openssl/openssl/pull/31913)
</content>
</entry>
<entry>
<title>Fix typos</title>
<updated>2026-07-08T10:45:09Z</updated>
<author>
<name>Dimitri Papadopoulos</name>
<email>3234522+DimitriPapadopoulos@users.noreply.github.com</email>
</author>
<published>2026-07-04T08:32:44Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=1860496d861e9ea92c1ac41ac0543c3f49d2353f'/>
<id>urn:sha1:1860496d861e9ea92c1ac41ac0543c3f49d2353f</id>
<content type='text'>
Found by typos[1].

[1] https://github.com/crate-ci/typos

CLA: trivial

Reviewed-by: Shane Lontis &lt;shane.lontis@oracle.com&gt;
Reviewed-by: Paul Dale &lt;paul.dale@oracle.com&gt;
Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
Reviewed-by: Norbert Pocs &lt;norbertp@openssl.org&gt;
Reviewed-by: Eugene Syromiatnikov &lt;esyr@openssl.org&gt;
MergeDate: Wed Jul  8 10:46:01 2026
(Merged from https://github.com/openssl/openssl/pull/31858)
</content>
</entry>
<entry>
<title>preserve stack thunks across sk_TYPE_dup</title>
<updated>2026-06-25T12:12:29Z</updated>
<author>
<name>Nikola Pajkovsky</name>
<email>nikolap@openssl.org</email>
</author>
<published>2026-05-20T06:51:07Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=a1e4bd14e59e62943fe048b944eac894cd0d8489'/>
<id>urn:sha1:a1e4bd14e59e62943fe048b944eac894cd0d8489</id>
<content type='text'>
ensure typed stack duplicates keep their compare, copy, and free thunks so
later operations do not call typed callbacks through erased void * function
pointer signatures.

Signed-off-by: Nikola Pajkovsky &lt;nikolap@openssl.org&gt;

Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
Reviewed-by: Milan Broz &lt;mbroz@openssl.org&gt;
MergeDate: Thu Jun 25 12:12:48 2026
(Merged from https://github.com/openssl/openssl/pull/31523)
</content>
</entry>
<entry>
<title>util: set thunks for sk_${nametype}_new(_reserve)</title>
<updated>2026-06-25T12:12:29Z</updated>
<author>
<name>Nikola Pajkovsky</name>
<email>nikolap@openssl.org</email>
</author>
<published>2026-05-19T13:42:47Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=30db55ac33cf6b815067149c233f45e4199df9b0'/>
<id>urn:sha1:30db55ac33cf6b815067149c233f45e4199df9b0</id>
<content type='text'>
call OPENSSL_sk_set_thunks for sk_${nametype}_new and
sk_${nametype}_new_reserve, and wrap the long generated stack
constructor and deep-copy macros across multiple lines so the nested
thunk setup is easier to read and maintain.

Signed-off-by: Nikola Pajkovsky &lt;nikolap@openssl.org&gt;

Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
Reviewed-by: Milan Broz &lt;mbroz@openssl.org&gt;
MergeDate: Thu Jun 25 12:12:46 2026
(Merged from https://github.com/openssl/openssl/pull/31523)
</content>
</entry>
<entry>
<title>stack: use a copy thunk for typed stack deep copies</title>
<updated>2026-05-20T15:53:32Z</updated>
<author>
<name>Nikola Pajkovsky</name>
<email>nikolap@openssl.org</email>
</author>
<published>2026-05-12T06:49:31Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=b1389437f56ace99f2a59a8a78fbf3f69b487d34'/>
<id>urn:sha1:b1389437f56ace99f2a59a8a78fbf3f69b487d34</id>
<content type='text'>
typed safestack wrappers pass type-specific copy callbacks such as
TYPE *(*)(const TYPE *) to OPENSSL_sk_deep_copy().  The generic stack code
then called those callbacks through OPENSSL_sk_copyfunc,
void *(*)(const void *), which is an incompatible function pointer type and
triggers UBSan.

Add an OPENSSL_sk_copyfunc_thunk and store it on typed stacks, mirroring the
existing compare/free thunk pattern.  Generated safestack helpers now install
a per-type copy thunk when constructing a stack, and internal_copy() uses that
thunk when deep-copying typed stacks.  This preserves the generic stack API
while ensuring typed copy callbacks are invoked through their real signature.

Fixes: https://github.com/openssl/project/issues/1951
Signed-off-by: Nikola Pajkovsky &lt;nikolap@openssl.org&gt;

Reviewed-by: Eugene Syromiatnikov &lt;esyr@openssl.org&gt;
Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
MergeDate: Wed May 20 15:53:45 2026
(Merged from https://github.com/openssl/openssl/pull/31151)
</content>
</entry>
<entry>
<title>providers/implementation: Generate header includes for .inc files</title>
<updated>2026-05-18T07:03:29Z</updated>
<author>
<name>Norbert Pocs</name>
<email>norbertp@openssl.org</email>
</author>
<published>2026-05-07T14:00:10Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=c662dfbc63c5b7685c9fef6882f1fa9e501a635c'/>
<id>urn:sha1:c662dfbc63c5b7685c9fef6882f1fa9e501a635c</id>
<content type='text'>
Make these headers self contained even as they are .inc files. This
approach makes it a lot easier to achieve self contained files and
protects from include reorders. (where the .inc can get above the
dependent headers)

Signed-off-by: Norbert Pocs &lt;norbertp@openssl.org&gt;

Reviewed-by: Saša Nedvědický &lt;sashan@openssl.org&gt;
Reviewed-by: Nikola Pajkovsky &lt;nikolap@openssl.org&gt;
MergeDate: Mon May 18 07:03:48 2026
(Merged from https://github.com/openssl/openssl/pull/31153)
</content>
</entry>
</feed>
