openssl, branch openssl-3.2.5

Prepare for release of 3.2.5

2025-07-01T12:06:25Z

Reviewed-by: Matt Caswell Reviewed-by: Neil Horman Release: yes

make update

2025-07-01T12:06:23Z

Reviewed-by: Matt Caswell Reviewed-by: Neil Horman Release: yes

Copyright year updates

2025-07-01T12:04:53Z

Reviewed-by: Matt Caswell Reviewed-by: Neil Horman Release: yes

dd 32-news

2025-07-01T11:46:06Z

Reviewed-by: Matt Caswell Release: yes (Merged from https://github.com/openssl/openssl/pull/27930)

fix: msg callback in dtls1_do_write that incorrectly shows message (like a certificate) that spans over multiple fragments.

2025-06-30T10:25:59Z

Reviewed-by: Paul Yang Reviewed-by: Tomas Mraz Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/27811) (cherry picked from commit de5a619aa015e7c8648e415975e5e2b722b2cbf7)

Fix nullpointer dereference in OSSL_PARAM_merge

2025-06-30T10:14:33Z

OSSL_PARAM_merge contained an error, where a nullpointer was dereferenced when both parameter arrays ended with the same key Reviewed-by: Tomas Mraz Reviewed-by: Tim Hudson Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/27910) (cherry picked from commit 63cb8f99a13fdc4c7c3b1e88d66a3ff70b72e642)

Better lookup for openssl executable

2025-06-30T09:43:34Z

Fixes #27891 Reviewed-by: Tomas Mraz Reviewed-by: Neil Horman Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/27895) (cherry picked from commit fa0c67a28a5a7d6ebeae7cb14d036780485e2fcd)

Fix exit code for s_time when -new command line switch specified

2025-06-20T19:44:13Z

When operating with the -new switch in apps/openssl s_time, we neglect to set the exit code properly, and so the app exits with a code of 1 rather than 0 as expected Fixes #27856 Reviewed-by: Tomas Mraz Reviewed-by: Dmitry Belyavskiy (Merged from https://github.com/openssl/openssl/pull/27857) (cherry picked from commit b6ff5598539bf91608246ed81b4b534cbea6539d)

Fix buggy stringop-overflow error on s390

2025-06-20T15:01:18Z

Despite some recent changes to our s390 builds, we're still seeing errors due to some stringop-overflow warnings: https://github.com/openssl/openssl/actions/runs/15748518222/job/44389197443 It appears to be caused because the static analysis that gcc preforms in gcc 12 (the version of the compiler on our s390 runner), fails to infer the proper sizes of the buffer on which we do the reverse memcpy in swap_copy(), resulting in warnings, which on --strict-warnings builds, breaks us. Fix it by using inlen rather than outlen to limit the copy length, adjusting it if need be to match the size of the output buffer in le_copy(). This allows the compiler to properly infer the array length constraints and suppress the warnings. Reviewed-by: Tomas Mraz Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/27864) (cherry picked from commit 837592dcd994a22a7c8d08bf3cf421f6b2e51280)

Avoid potential double close of client_skt in sslecho

2025-06-20T14:45:26Z

The server_running variable is declared as volatile and some comments in the code are mentioning about implementing CTRL+C handler in the future. In the client handling loop, the client_skt is closed at the end of the loop if server_running is true. If (future) CTRL+C handler changes server_running to false at this time. The next accept will not happen and the exit clean up code will close client_skt for the second time. This patch fixes this potential double close by setting client_skt back to -1 after closing it. Reviewed-by: Tomas Mraz Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/27405) (cherry picked from commit 48e3fe08639d84bd557c0d5248f5600f2fb1f7de)