diff options
author | deraadt <> | 2014-06-02 15:08:38 +0000 |
---|---|---|
committer | deraadt <> | 2014-06-02 15:08:38 +0000 |
commit | 5df353beff71ba1f1e84cd691ef3edf892aa5311 (patch) | |
tree | 9705407a292ffa9e8df2ed301da2accffe5268ad /src/lib/libcrypto/perlasm/x86asm.pl | |
parent | 599c6f06ff6ff9ca9526b1c08abb02d14f3501c4 (diff) | |
download | openbsd-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/perlasm/x86asm.pl')
-rw-r--r-- | src/lib/libcrypto/perlasm/x86asm.pl | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/src/lib/libcrypto/perlasm/x86asm.pl b/src/lib/libcrypto/perlasm/x86asm.pl index d74d1992f8..5916ea4f89 100644 --- a/src/lib/libcrypto/perlasm/x86asm.pl +++ b/src/lib/libcrypto/perlasm/x86asm.pl | |||
@@ -130,14 +130,6 @@ sub ::pclmulqdq | |||
130 | { &::generic("pclmulqdq",@_); } | 130 | { &::generic("pclmulqdq",@_); } |
131 | } | 131 | } |
132 | 132 | ||
133 | sub ::rdrand | ||
134 | { my ($dst)=@_; | ||
135 | if ($dst =~ /(e[a-dsd][ixp])/) | ||
136 | { &::data_byte(0x0f,0xc7,0xf0|$regrm{$dst}); } | ||
137 | else | ||
138 | { &::generic("rdrand",@_); } | ||
139 | } | ||
140 | |||
141 | # label management | 133 | # label management |
142 | $lbdecor="L"; # local label decoration, set by package | 134 | $lbdecor="L"; # local label decoration, set by package |
143 | $label="000"; | 135 | $label="000"; |