diff options
| author | deraadt <> | 2014-06-02 15:08:38 +0000 |
|---|---|---|
| committer | deraadt <> | 2014-06-02 15:08:38 +0000 |
| commit | 63bcac43aa0d6361864d2102a9cbe8ec910b763e (patch) | |
| tree | 9705407a292ffa9e8df2ed301da2accffe5268ad /src/lib/libcrypto/engine/engine.h | |
| parent | d2de3e4a6a6d90f03cb37fabd7d46d44ccb2660e (diff) | |
| download | openbsd-63bcac43aa0d6361864d2102a9cbe8ec910b763e.tar.gz openbsd-63bcac43aa0d6361864d2102a9cbe8ec910b763e.tar.bz2 openbsd-63bcac43aa0d6361864d2102a9cbe8ec910b763e.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 '')
| -rw-r--r-- | src/lib/libcrypto/engine/engine.h | 1 |
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 |
| 321 | void ENGINE_load_cryptodev(void); | 321 | void ENGINE_load_cryptodev(void); |
| 322 | void ENGINE_load_rsax(void); | 322 | void ENGINE_load_rsax(void); |
| 323 | void ENGINE_load_rdrand(void); | ||
| 324 | void ENGINE_load_builtin_engines(void); | 323 | void 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 |
