summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/engine/eng_all.c
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/eng_all.c
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/eng_all.c')
-rw-r--r--src/lib/libcrypto/engine/eng_all.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/src/lib/libcrypto/engine/eng_all.c b/src/lib/libcrypto/engine/eng_all.c
index f318ea69c4..fd36594a0b 100644
--- a/src/lib/libcrypto/engine/eng_all.c
+++ b/src/lib/libcrypto/engine/eng_all.c
@@ -76,9 +76,6 @@ void ENGINE_load_builtin_engines(void)
76#ifndef OPENSSL_NO_RSAX 76#ifndef OPENSSL_NO_RSAX
77 ENGINE_load_rsax(); 77 ENGINE_load_rsax();
78#endif 78#endif
79#ifndef OPENSSL_NO_RDRAND
80 ENGINE_load_rdrand();
81#endif
82 ENGINE_load_dynamic(); 79 ENGINE_load_dynamic();
83#ifndef OPENSSL_NO_STATIC_ENGINE 80#ifndef OPENSSL_NO_STATIC_ENGINE
84#ifndef OPENSSL_NO_HW 81#ifndef OPENSSL_NO_HW