summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/Symbols.list
diff options
context:
space:
mode:
authortb <>2024-03-02 10:35:32 +0000
committertb <>2024-03-02 10:35:32 +0000
commita3c990bc8f1fde064c43ffefb311482cb87ecd54 (patch)
tree935205f7c56a42128fa412c247899647f6609756 /src/lib/libcrypto/Symbols.list
parent277f3edd9b1ca36d2165db8f849130e82cb63991 (diff)
downloadopenbsd-a3c990bc8f1fde064c43ffefb311482cb87ecd54.tar.gz
openbsd-a3c990bc8f1fde064c43ffefb311482cb87ecd54.tar.bz2
openbsd-a3c990bc8f1fde064c43ffefb311482cb87ecd54.zip
Remove X509V3_EXT extensibility API
You used to be able to define your own X.509 extension handlers. Great. Even greater: the verifier would ignore any custom extensions. So this was only ever useful for serialization and deserialization. In other words, almost entirely pointless. The API was also unused except for a hack in kore-acme, which was fixed recently. ok jsing
Diffstat (limited to 'src/lib/libcrypto/Symbols.list')
-rw-r--r--src/lib/libcrypto/Symbols.list4
1 files changed, 0 insertions, 4 deletions
diff --git a/src/lib/libcrypto/Symbols.list b/src/lib/libcrypto/Symbols.list
index f27d1fbffd..48af5219af 100644
--- a/src/lib/libcrypto/Symbols.list
+++ b/src/lib/libcrypto/Symbols.list
@@ -2493,13 +2493,9 @@ X509V3_EXT_CRL_add_conf
2493X509V3_EXT_CRL_add_nconf 2493X509V3_EXT_CRL_add_nconf
2494X509V3_EXT_REQ_add_conf 2494X509V3_EXT_REQ_add_conf
2495X509V3_EXT_REQ_add_nconf 2495X509V3_EXT_REQ_add_nconf
2496X509V3_EXT_add
2497X509V3_EXT_add_alias
2498X509V3_EXT_add_conf 2496X509V3_EXT_add_conf
2499X509V3_EXT_add_list
2500X509V3_EXT_add_nconf 2497X509V3_EXT_add_nconf
2501X509V3_EXT_add_nconf_sk 2498X509V3_EXT_add_nconf_sk
2502X509V3_EXT_cleanup
2503X509V3_EXT_conf 2499X509V3_EXT_conf
2504X509V3_EXT_conf_nid 2500X509V3_EXT_conf_nid
2505X509V3_EXT_d2i 2501X509V3_EXT_d2i