summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/ERR_load_crypto_strings.3
diff options
context:
space:
mode:
authortb <>2023-07-21 09:04:23 +0000
committertb <>2023-07-21 09:04:23 +0000
commitf3f431c8f6134c5d325ede30963e2f1edd9a0718 (patch)
treea06a9f51ed23a061b5e6a00600a42d86ad37ce11 /src/lib/libcrypto/man/ERR_load_crypto_strings.3
parent0fa0e5b768255277d5110ebe72faab0818b80b86 (diff)
downloadopenbsd-f3f431c8f6134c5d325ede30963e2f1edd9a0718.tar.gz
openbsd-f3f431c8f6134c5d325ede30963e2f1edd9a0718.tar.bz2
openbsd-f3f431c8f6134c5d325ede30963e2f1edd9a0718.zip
Provide a bunch of always failing ENGINE API
This commit adds a few symbols under OPENSSL_NO_ENGINE. They will be used after the main ENGINE code is disabled in the next bump. The ecosystem is mostly prepared for dealing with a libcrypto compiled with OPENSSL_NO_ENGINE. There are a few stragglers like M2Crypto, dovecot and the latest apr-util release (fixed in their development branch). To avoid intrusive patching in these ports, we need to keep a bunch of ENGINE symbols around despite adding OPENSSL_NO_ENGINE. This of course meant patching some other ports, but that was way easier. ok jsing
Diffstat (limited to 'src/lib/libcrypto/man/ERR_load_crypto_strings.3')
0 files changed, 0 insertions, 0 deletions