<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/crypto/encode_decode, branch feature/evp_skey</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=feature%2Fevp_skey</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=feature%2Fevp_skey'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2025-08-12T18:15:50Z</updated>
<entry>
<title>Fix missing unlock in decoder_pkey.c</title>
<updated>2025-08-12T18:15:50Z</updated>
<author>
<name>Neil Horman</name>
<email>nhorman@openssl.org</email>
</author>
<published>2025-08-10T21:55:15Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=c0527256d2e6a148931e1d8b9b0ff4af7564caae'/>
<id>urn:sha1:c0527256d2e6a148931e1d8b9b0ff4af7564caae</id>
<content type='text'>
We hit an assertion failure during a call to CRYPTO_THREAD_read_lock
during memfail testing.

This was caused by us attempting to take a read lock in the same thread
that already held the same lock for writing resulting in an EBUSY
return.

This occured because we triggered a memory failure path in
DECODER_new_for_pkey, which never unlocked a write lock we were holding.

Fix it by ensuring the lock is released in the error path.

Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Reviewed-by: Saša Nedvědický &lt;sashan@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/28216)
</content>
</entry>
<entry>
<title>crypto: use array memory (re)allocation routines</title>
<updated>2025-08-08T16:22:10Z</updated>
<author>
<name>Eugene Syromiatnikov</name>
<email>esyr@openssl.org</email>
</author>
<published>2025-07-17T13:17:38Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=7867bf1523bcb12796a5d9c3c7fe598837591991'/>
<id>urn:sha1:7867bf1523bcb12796a5d9c3c7fe598837591991</id>
<content type='text'>
Co-Authored-by: Alexandr Nedvedicky &lt;sashan@openssl.org&gt;
Signed-off-by: Eugene Syromiatnikov &lt;esyr@openssl.org&gt;

Reviewed-by: Saša Nedvědický &lt;sashan@openssl.org&gt;
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
Reviewed-by: Paul Dale &lt;ppzgs1@gmail.com&gt;
Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/28059)
</content>
</entry>
<entry>
<title>libapps + libcrypto: Silence warnings on Win64 builds</title>
<updated>2025-07-02T15:26:26Z</updated>
<author>
<name>Tomas Mraz</name>
<email>tomas@openssl.org</email>
</author>
<published>2025-06-11T08:48:01Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=bb86c43fa88ce485b13f94514dddb08ce8f60280'/>
<id>urn:sha1:bb86c43fa88ce485b13f94514dddb08ce8f60280</id>
<content type='text'>
Reviewed-by: Saša Nedvědický &lt;sashan@openssl.org&gt;
Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/27806)
</content>
</entry>
<entry>
<title>decoders: Fix prioritization of decoders via property query</title>
<updated>2025-07-01T17:06:57Z</updated>
<author>
<name>Daniel Van Geest</name>
<email>daniel.vangeest@cryptonext-security.com</email>
</author>
<published>2025-06-23T11:45:59Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=60775e31123e6ef66a7cf86f199289d6e250dceb'/>
<id>urn:sha1:60775e31123e6ef66a7cf86f199289d6e250dceb</id>
<content type='text'>
When a property query string was used, it was not being applied to decoders.
When multiple providers supporting the same algorithm were loaded, it was
undefined which provider would be used when decoding a key, even when a
propquery string was provided.  This fix scores decoder instances based on
property query matching and selects the highest scored decoder instance when
building the decoder chain.

The fake_rsa test provider is updated to support basic encoding and decoding.
A test is added using the fake_rsa provider to ensure that property query
strings are respected when loading decoders.

Reviewed-by: Paul Dale &lt;ppzgs1@gmail.com&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/27876)
</content>
</entry>
<entry>
<title>Copyright year updates</title>
<updated>2025-03-12T13:35:59Z</updated>
<author>
<name>openssl-machine</name>
<email>openssl-machine@openssl.org</email>
</author>
<published>2025-03-12T13:35:59Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=0c679f556669e32499a827a081afe3bcf973c9ad'/>
<id>urn:sha1:0c679f556669e32499a827a081afe3bcf973c9ad</id>
<content type='text'>
Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
Release: yes
</content>
</entry>
<entry>
<title>Further decoder tuning possibly better perf</title>
<updated>2025-03-01T15:04:09Z</updated>
<author>
<name>Viktor Dukhovni</name>
<email>openssl-users@dukhovni.org</email>
</author>
<published>2025-02-27T17:17:08Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=31b5f3f38225e0b694bd564e8e77d9fefb51ff65'/>
<id>urn:sha1:31b5f3f38225e0b694bd564e8e77d9fefb51ff65</id>
<content type='text'>
- The decoder should consider fewer options based on
  more precise tracking of the desired input type
  (DER, PVK, MSBLOB), algorithm (RSA, EC, ...),
  input structure (SPKI, P8, ...).

How much this affects actual use-cases is harder to estimate, we'll just
have to run before/after perf tests.

Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/26927)
</content>
</entry>
<entry>
<title>Encoder : Fix floating pointer when OSSL_ENCODER_to_data() is called</title>
<updated>2025-02-27T01:04:14Z</updated>
<author>
<name>slontis</name>
<email>shane.lontis@oracle.com</email>
</author>
<published>2025-02-25T06:03:38Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=c2f4d7aae1c7c726eb1f8226d3d454dfd9754758'/>
<id>urn:sha1:c2f4d7aae1c7c726eb1f8226d3d454dfd9754758</id>
<content type='text'>
twice.

Fixes #26862

This only happens when using the FIPS provider, since it needs to export
the key.

Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
Reviewed-by: Paul Dale &lt;ppzgs1@gmail.com&gt;
Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Reviewed-by: Viktor Dukhovni &lt;viktor@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/26891)
</content>
</entry>
<entry>
<title>Use better data type info in decoders</title>
<updated>2025-02-26T14:13:57Z</updated>
<author>
<name>Viktor Dukhovni</name>
<email>openssl-users@dukhovni.org</email>
</author>
<published>2025-02-25T07:17:02Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=44a64029c3c5357c5b32dbe45b7f55ab7866ad3f'/>
<id>urn:sha1:44a64029c3c5357c5b32dbe45b7f55ab7866ad3f</id>
<content type='text'>
The decoders in some cases failed to capture or propagate
information about what is being decoded, causing more work
happen to try unrelated decoders as a fallback.

We now try harder to keep track of the expected object (private key or
public key, if known), and the algorithm determined from the OID of a
PKCS8 object or SPKI.  This leads in many cases to fewer decoder
invocations.  With so many more algorithms now, trying every decoder
is increasingly best avoided.

Reviewed-by: Dmitry Belyavskiy &lt;beldmit@gmail.com&gt;
Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/26892)
</content>
</entry>
<entry>
<title>More consistent ML-KEM key checks</title>
<updated>2025-02-19T22:59:22Z</updated>
<author>
<name>Viktor Dukhovni</name>
<email>openssl-users@dukhovni.org</email>
</author>
<published>2025-02-18T07:42:41Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=a4465bf694ea4505c544a96f2cfb329d86e8b711'/>
<id>urn:sha1:a4465bf694ea4505c544a96f2cfb329d86e8b711</id>
<content type='text'>
- Cross-check seed `z` value on import as well as load.
- In import/load When re-generating from a seed, check hash of any
  explicit private key when both provided.
- Avoid leak of expanded key encoding when load fails.

Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/26812)
</content>
</entry>
<entry>
<title>Reject import of private keys that fail PCT</title>
<updated>2025-02-14T09:50:59Z</updated>
<author>
<name>Viktor Dukhovni</name>
<email>openssl-users@dukhovni.org</email>
</author>
<published>2025-02-06T09:07:11Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=2ea9903c160fe4212b07ec8af630071e35098ceb'/>
<id>urn:sha1:2ea9903c160fe4212b07ec8af630071e35098ceb</id>
<content type='text'>
- Also added a provider "validate" method that wraps the PCT test.

Reviewed-by: Shane Lontis &lt;shane.lontis@oracle.com&gt;
Reviewed-by: Tim Hudson &lt;tjh@openssl.org&gt;
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/26656)
</content>
</entry>
</feed>
