summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/engine/engine.h
diff options
context:
space:
mode:
authorderaadt <>2014-06-02 15:08:38 +0000
committerderaadt <>2014-06-02 15:08:38 +0000
commit5df353beff71ba1f1e84cd691ef3edf892aa5311 (patch)
tree9705407a292ffa9e8df2ed301da2accffe5268ad /src/lib/libcrypto/engine/engine.h
parent599c6f06ff6ff9ca9526b1c08abb02d14f3501c4 (diff)
downloadopenbsd-5df353beff71ba1f1e84cd691ef3edf892aa5311.tar.gz
openbsd-5df353beff71ba1f1e84cd691ef3edf892aa5311.tar.bz2
openbsd-5df353beff71ba1f1e84cd691ef3edf892aa5311.zip
A few months back there was a big community fuss regarding direct-use
of the intel RDRAND instruction. Consensus was RDRAND should probably only be used as an additional source of entropy in a mixer. Guess which library bends over backwards to provide easy access to RDRAND? Yep. Guess which applications are using this support? Not even one... but still, this is being placed as a trap for someone. Send this support straight to the abyss. ok kettenis
Diffstat (limited to 'src/lib/libcrypto/engine/engine.h')
-rw-r--r--src/lib/libcrypto/engine/engine.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/lib/libcrypto/engine/engine.h b/src/lib/libcrypto/engine/engine.h
index 5c2f7b0527..e99ad750e4 100644
--- a/src/lib/libcrypto/engine/engine.h
+++ b/src/lib/libcrypto/engine/engine.h
@@ -320,7 +320,6 @@ void ENGINE_load_padlock(void);
320#endif 320#endif
321void ENGINE_load_cryptodev(void); 321void ENGINE_load_cryptodev(void);
322void ENGINE_load_rsax(void); 322void ENGINE_load_rsax(void);
323void ENGINE_load_rdrand(void);
324void ENGINE_load_builtin_engines(void); 323void ENGINE_load_builtin_engines(void);
325 324
326/* Get and set global flags (ENGINE_TABLE_FLAG_***) for the implementation 325/* Get and set global flags (ENGINE_TABLE_FLAG_***) for the implementation