summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/x86cpuid.pl
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/x86cpuid.pl
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/x86cpuid.pl')
-rw-r--r--src/lib/libcrypto/x86cpuid.pl12
1 files changed, 0 insertions, 12 deletions
diff --git a/src/lib/libcrypto/x86cpuid.pl b/src/lib/libcrypto/x86cpuid.pl
index 169036d53d..47df147a83 100644
--- a/src/lib/libcrypto/x86cpuid.pl
+++ b/src/lib/libcrypto/x86cpuid.pl
@@ -257,18 +257,6 @@ for (@ARGV) { $sse2=1 if (/-DOPENSSL_IA32_SSE2/); }
257 &ret (); 257 &ret ();
258&function_end_B("OPENSSL_atomic_add"); 258&function_end_B("OPENSSL_atomic_add");
259 259
260&function_begin_B("OPENSSL_ia32_rdrand");
261 &mov ("ecx",8);
262&set_label("loop");
263 &rdrand ("eax");
264 &jc (&label("break"));
265 &loop (&label("loop"));
266&set_label("break");
267 &cmp ("eax",0);
268 &cmove ("eax","ecx");
269 &ret ();
270&function_end_B("OPENSSL_ia32_rdrand");
271
272&initseg("OPENSSL_cpuid_setup"); 260&initseg("OPENSSL_cpuid_setup");
273 261
274&asm_finish(); 262&asm_finish();