summaryrefslogtreecommitdiffstats
path: root/lib/libcrypto/doc/engine.pod
diff options
context:
space:
mode:
authorbcook <bcook@openbsd.org>2015-06-19 06:05:11 +0000
committerbcook <bcook@openbsd.org>2015-06-19 06:05:11 +0000
commit9b08b2044f70fb2b1351755a86e57b1ab331448c (patch)
tree70bd16bd727740982bf27606a1ac8997d8a61b90 /lib/libcrypto/doc/engine.pod
parentsync (diff)
downloadwireguard-openbsd-9b08b2044f70fb2b1351755a86e57b1ab331448c.tar.xz
wireguard-openbsd-9b08b2044f70fb2b1351755a86e57b1ab331448c.zip
Disable ENGINE_load_dynamic (dynamic engine support).
We do not build, test or ship any dynamic engines, so we can remove the dynamic engine loader as well. This leaves a stub initialization function in its place. ok beck@, reyk@, miod@
Diffstat (limited to 'lib/libcrypto/doc/engine.pod')
-rw-r--r--lib/libcrypto/doc/engine.pod8
1 files changed, 4 insertions, 4 deletions
diff --git a/lib/libcrypto/doc/engine.pod b/lib/libcrypto/doc/engine.pod
index 4a6ee591386..578a7023713 100644
--- a/lib/libcrypto/doc/engine.pod
+++ b/lib/libcrypto/doc/engine.pod
@@ -309,11 +309,11 @@ consideration is whether any/all available ENGINE implementations should be
made visible to OpenSSL - this is controlled by calling the various "load"
functions, eg.
- /* Make the "dynamic" ENGINE available */
- void ENGINE_load_dynamic(void);
- ...
/* Make ALL ENGINE implementations bundled with OpenSSL available */
- void ENGINE_load_builtin_engines(void);
+ ENGINE_load_builtin_engines();
+
+Note that ENGINE_load_dynamic(void) is a placeholder and does not enable
+dynamic engine loading support.
Having called any of these functions, ENGINE objects would have been
dynamically allocated and populated with these implementations and linked