diff options
author | tb <> | 2025-03-09 15:29:56 +0000 |
---|---|---|
committer | tb <> | 2025-03-09 15:29:56 +0000 |
commit | b04c2a1d799fe2ea8751349ab1dc4a8b551ce48d (patch) | |
tree | d09836f242ff268513c1c5d3722c69747b19c32e /src/lib/libssl/ssl_both.c | |
parent | 5e452fbcbaa85718d1cafb0f047a72e9825b28a0 (diff) | |
download | openbsd-b04c2a1d799fe2ea8751349ab1dc4a8b551ce48d.tar.gz openbsd-b04c2a1d799fe2ea8751349ab1dc4a8b551ce48d.tar.bz2 openbsd-b04c2a1d799fe2ea8751349ab1dc4a8b551ce48d.zip |
Align CRYPTO_set_mem*_functions with OpenSSL 1.1
CRYPTO_set_mem_ex_functions() was renamed to CRYPTO_set_mem_functions(),
replacing the latter while also correcting the arguments for the free
pointer. The backstory is that a commit that was never compiled was fixed
the wrong way an hour later (both committed without review, obviously),
and here we are, still cleaning up the mess 23 years later.
We carry patches in cjose and stunnel for this; dovecot and links+ have
autoconf checks and will adapt. Oh, and then there's the mariadb
configure time insanity passing wrong function pointers...
ok jsing
Diffstat (limited to 'src/lib/libssl/ssl_both.c')
0 files changed, 0 insertions, 0 deletions