openssl/doc, branch openssl-3.2

doc: Discuss calling X509_verify_cert in cert_verify_callback

2025-11-24T18:23:05Z

Using SSL_CTX_set_cert_verify_callback but still calling X509_verify_cert is useful if applications want to dynamically configure the X509_STORE_CTX, or postprocess the result, in a way that does not quite fit the somewhat unpredictable behavior of the SSL_CTX_set_verify callback. (In my experience, applications rarely realize it is called multiple times. It's also too late at that point to reconfigure the X509_STORE_CTX as verification has already started.) There is one note in the docs that the callback needs to stash the verify result with X509_STORE_CTX_set_error, but it is not immediately obvious that X509_verify_cert will do so, or that it is the built-in behavior. Add a paragraph discussing this. Reviewed-by: Tim Hudson Reviewed-by: Viktor Dukhovni Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/28960) (cherry picked from commit 069181d7f39beaae22bfa67bcba3c5fe93acafd4)

doc/man3/X509_STORE_get0_param.pod: mention how to free the returned objects

2025-11-24T18:14:56Z

It is not entirely obvious from the description how the objects returned by X509_STORE_get1_all_certs() are supposed to be freed, explicitly mention the relevant call, and provide a reference to DEFINE_STACK_OF(3). Signed-off-by: Eugene Syromiatnikov Reviewed-by: Norbert Pocs Reviewed-by: Dmitry Belyavskiy (Merged from https://github.com/openssl/openssl/pull/29016)

Correct information about the default value of the -md parameter

2025-11-21T13:51:17Z

of the openssl cms command. Reviewed-by: Tomas Mraz Reviewed-by: Dmitry Belyavskiy Reviewed-by: Paul Dale Reviewed-by: Neil Horman (Merged from https://github.com/openssl/openssl/pull/29175) (cherry picked from commit 2a7b058429938e40e20882a80bc5d2f426b145b8)

doc/man3/OPENSSL_malloc.pod: mention rationale for OPENSSL_cleanse()

2025-11-21T13:37:18Z

It was not entirely clear from the sole description, what is the reason for preferring OPENSSL_cleanse() over memset(). Add a note about situations in which OPENSSL_cleanse() should be chosen. Signed-off-by: Eugene Syromiatnikov Reviewed-by: Dmitry Belyavskiy Reviewed-by: Paul Dale Reviewed-by: Richard Levitte Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/29174) (cherry picked from commit 768468f40e810ceef00b1c3b7cac05beaa1d8f8c)

DOC: fix description of '-self_test_oninstall'

2025-11-21T13:34:43Z

CLA: trivial Reviewed-by: Paul Dale Reviewed-by: Eugene Syromiatnikov (Merged from https://github.com/openssl/openssl/pull/29168) (cherry picked from commit 978cb1f9d1fb895f51feeee4cf700cf07a063e01)

Document when OSSL_ENC/DECODER_CTX_set* functions shouldn't be used

2025-11-13T11:20:55Z

Reviewed-by: Dmitry Belyavskiy Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/29122) (cherry picked from commit c22facc35038085407e457bada85efffab3c3f2a)

Note about different exclusion of GREASE extensions

2025-11-13T11:09:50Z

Different SSL_client_hello_* functions have different behavior in regards to GREASE extensions. Fixes #27580 Reviewed-by: Matt Caswell Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/29066) (cherry picked from commit 657b01241feeb23a53378920bf33d59505532ba8)

Properly error out when AEAD Algorithms are used with Encrypted Data

2025-11-10T19:42:27Z

Encrypted Data does not support AEAD algorithms. If you wish to use AEAD algorithms you will have to use a CMS_AuthEnvelopedData structure. Therefore, when AEAD algorithms are used with CMS_EncryptedData_set1_key will now return an error. Fixes: #28607 Reviewed-by: Paul Dale Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/28711) (cherry picked from commit 86344acb02eb3718b0491b9915846667c55c95ff)

Copyright year updates

2025-09-30T13:03:21Z

Reviewed-by: Neil Horman Reviewed-by: Saša Nedvědický Release: yes

Correct the documentation for OPENSSL_sk_find

2025-09-24T10:28:15Z

Since April of 2023 with commit eb0935f, these functions have not sorted the stack if it was not sorted. The documentation was noti changed at the time to reflect this changed behaviour. This corrects the documentation to reflect the current behaviour of these functions Reviewed-by: Paul Dale Reviewed-by: Matt Caswell Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/28578) (cherry picked from commit 07e70f951e7c4618b4a275d60f7410f77999f92a)