summaryrefslogtreecommitdiffstats
path: root/lib/libssl/src/crypto/perlasm/x86asm.pl
diff options
context:
space:
mode:
authorderaadt <deraadt@openbsd.org>2014-06-02 15:08:37 +0000
committerderaadt <deraadt@openbsd.org>2014-06-02 15:08:37 +0000
commit1cdc2ead0725c40cbbda34f52f4a488f09f52669 (patch)
tree7d3cee2b23dfabb03ac07d3fccc1d2207839f0ba /lib/libssl/src/crypto/perlasm/x86asm.pl
parentRename more variables for readability and consistency. (diff)
downloadwireguard-openbsd-1cdc2ead0725c40cbbda34f52f4a488f09f52669.tar.xz
wireguard-openbsd-1cdc2ead0725c40cbbda34f52f4a488f09f52669.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 'lib/libssl/src/crypto/perlasm/x86asm.pl')
-rw-r--r--lib/libssl/src/crypto/perlasm/x86asm.pl8
1 files changed, 0 insertions, 8 deletions
diff --git a/lib/libssl/src/crypto/perlasm/x86asm.pl b/lib/libssl/src/crypto/perlasm/x86asm.pl
index d74d1992f8d..5916ea4f893 100644
--- a/lib/libssl/src/crypto/perlasm/x86asm.pl
+++ b/lib/libssl/src/crypto/perlasm/x86asm.pl
@@ -130,14 +130,6 @@ sub ::pclmulqdq
{ &::generic("pclmulqdq",@_); }
}
-sub ::rdrand
-{ my ($dst)=@_;
- if ($dst =~ /(e[a-dsd][ixp])/)
- { &::data_byte(0x0f,0xc7,0xf0|$regrm{$dst}); }
- else
- { &::generic("rdrand",@_); }
-}
-
# label management
$lbdecor="L"; # local label decoration, set by package
$label="000";