<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/test/ct/log_list_missing_section.cnf, branch master</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=master</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2026-10-09T20:39:34Z</updated>
<entry>
<title>crypto/ct/ct_log.c: handle negative returns when loading a log store</title>
<updated>2026-10-09T20:39:34Z</updated>
<author>
<name>Mounir IDRASSI</name>
<email>mounir.idrassi@idrix.fr</email>
</author>
<published>2026-09-05T23:40:39Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=05902ff40b3251e2a913a24a60268263e18fe2c3'/>
<id>urn:sha1:05902ff40b3251e2a913a24a60268263e18fe2c3</id>
<content type='text'>
CTLOG_STORE_load_file() treats a negative CONF_parse_list() return as
success, even when the callback failed to allocate the log name.

Check for non-positive parser returns so internal errors produce the
documented 0 return value, preserving the existing invalid-entry handling.

Add a regression using the existing allocation failure framework and a
configuration referencing a missing log section. Loading must return 0
both normally and when allocations fail. Return -1 from the test on
unexpected success so ADD_MFAIL_NO_CHECK_TEST cannot mask the failure.

Resolves: https://github.com/openssl/openssl/issues/32703
References: 70073f3e3aeb "Treat boolean functions as booleans"
Complements: 68efafc51378 "Add checks on sk_TYPE_push() returned value"
Complements: e57036f2bf81 "Fix some memory error handling in CT"
Assisted-by: Codex:gpt-6-astra
Reviewed-by: Saša Nedvědický &lt;sashan@openssl.org&gt;
Reviewed-by: Frederik Wedel-Heinen &lt;fwh.openssl@gmail.com&gt;
Reviewed-by: Eugene Syromiatnikov &lt;esyr@openssl.org&gt;
Merge-date: Fri Oct  9 20:40:44 2026
Merged-from: https://github.com/openssl/openssl/pull/32704
</content>
</entry>
</feed>
