Branch: refs/heads/master
Home:
https://github.com/openssl/openssl
Commit: 3720c946f095d4f35f04f61cf6efa8b84e26fc7c
https://github.com/openssl/openssl/commit/3720c946f095d4f35f04f61cf6efa8b84e26fc7c
Author: Viktor Dukhovni <
openss...@dukhovni.org>
Date: 2025-12-05 (Fri, 05 Dec 2025)
Changed paths:
M crypto/ml_dsa/ml_dsa_key.c
M crypto/ml_kem/ml_kem.c
M doc/man7/EVP_PKEY-ML-DSA.pod
M doc/man7/EVP_PKEY-ML-KEM.pod
M include/openssl/
core_names.h.in
M providers/implementations/encode_decode/encode_key2any.c
M providers/implementations/encode_decode/
encode_key2any.inc.in
M providers/implementations/encode_decode/ml_dsa_codecs.c
M providers/implementations/encode_decode/ml_kem_codecs.c
M providers/implementations/include/prov/ml_dsa_codecs.h
M providers/implementations/include/prov/ml_kem_codecs.h
M test/evp_extra_test.c
M util/perl/OpenSSL/
paramnames.pm
Log Message:
-----------
Per-key encoding formats for ML-KEM and ML-DSA
We support selection of ML-KEM and ML-DSA key formats on input and
output at the provider level, these are essentially global defaults,
in effect for the lifetime of the process.
Unfortunately, the JAVA interface in openssl-jostle needs to be able to
output a specific key in seed-only form. To that end, this PR
introduces a new "output-formats" PKEY encoding parameter, that can be used
with OSSL_ENCODER_CTX_set_params(3) when encoding a key to PKCS#8, after
using OSSL_ENCODER_CTX_new_for_key(3), rather than i2d_PrivateKey(3),
i2d_PKCS8PrivateKey(3) or PEM equivalents.
Reviewed-by: Tomas Mraz <
to...@openssl.org>
Reviewed-by: Eugene Syromiatnikov <
es...@openssl.org>
Reviewed-by: Neil Horman <
nho...@openssl.org>
Reviewed-by: Paul Dale <
paul...@oracle.com>
(Merged from
https://github.com/openssl/openssl/pull/29206)
Commit: bf236e07afbd235d609f057eb50c92d1d2ee5008
https://github.com/openssl/openssl/commit/bf236e07afbd235d609f057eb50c92d1d2ee5008
Author: Viktor Dukhovni <
openss...@dukhovni.org>
Date: 2025-12-05 (Fri, 05 Dec 2025)
Changed paths:
M CHANGES.md
M crypto/encode_decode/decoder_lib.c
M crypto/encode_decode/decoder_pkey.c
M crypto/encode_decode/encoder_lib.c
M crypto/encode_decode/encoder_local.h
M crypto/encode_decode/encoder_pkey.c
M doc/man3/OSSL_DECODER_CTX.pod
M doc/man3/OSSL_DECODER_CTX_new_for_pkey.pod
M doc/man3/OSSL_ENCODER_CTX.pod
M doc/man3/OSSL_ENCODER_CTX_new_for_pkey.pod
M include/openssl/decoder.h
M include/openssl/encoder.h
M test/endecode_test.c
M test/evp_extra_test.c
M util/libcrypto.num
Log Message:
-----------
Clarify/fix encoder/decoder context docs and code
In was premature to make OSSL_(EN|DE)CODER_CTX_[sg]et_finalized() be
public interfaces. Forunately, these have not yet appeared outside the
"master" branch, so we can still retract them.
Also, in the case of decoders, the implementation failed to take into
account that the context was duplicated before it was returned to the
user, and the duplicated copy failed to copy the "finalized" field.
This commit also renames "finalized" to "frozen", because
finalisation is a misleading term in this context, it suggests
resource reclamation during garbage collection or deallocation,
not marking a structure partly immutable.
Reviewed-by: Tomas Mraz <
to...@openssl.org>
Reviewed-by: Eugene Syromiatnikov <
es...@openssl.org>
Reviewed-by: Neil Horman <
nho...@openssl.org>
Reviewed-by: Paul Dale <
paul...@oracle.com>
(Merged from
https://github.com/openssl/openssl/pull/29206)
Compare:
https://github.com/openssl/openssl/compare/21069c983bc3...bf236e07afbd
To unsubscribe from these emails, change your notification settings at
https://github.com/openssl/openssl/settings/notifications