summaryrefslogtreecommitdiff
path: root/lib/libcrypto/crypto
diff options
context:
space:
mode:
authorTheo de Raadt <deraadt@cvs.openbsd.org>2014-06-02 15:08:39 +0000
committerTheo de Raadt <deraadt@cvs.openbsd.org>2014-06-02 15:08:39 +0000
commitf3baf6550c815e427dd00bc1c3ee8669876143cd (patch)
treea1d72f4e034e7821a8277bf97e0bbfab81029cba /lib/libcrypto/crypto
parent3b319829ab83ba7e0e5c0bc28bdb7c9aa6c81e1a (diff)
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/libcrypto/crypto')
-rw-r--r--lib/libcrypto/crypto/Makefile4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/libcrypto/crypto/Makefile b/lib/libcrypto/crypto/Makefile
index 9acf6701c53..1e2ce774d3b 100644
--- a/lib/libcrypto/crypto/Makefile
+++ b/lib/libcrypto/crypto/Makefile
@@ -1,4 +1,4 @@
-# $OpenBSD: Makefile,v 1.37 2014/05/25 17:29:51 tedu Exp $
+# $OpenBSD: Makefile,v 1.38 2014/06/02 15:08:38 deraadt Exp $
LIB= crypto
@@ -133,7 +133,7 @@ SRCS+= eng_table.c eng_pkey.c eng_fat.c eng_all.c
SRCS+= tb_rsa.c tb_dsa.c tb_ecdsa.c tb_dh.c tb_ecdh.c tb_rand.c tb_store.c
SRCS+= tb_cipher.c tb_digest.c tb_pkmeth.c tb_asnmth.c
SRCS+= eng_openssl.c eng_cnf.c eng_dyn.c hw_cryptodev.c
-SRCS+= eng_rsax.c eng_rdrand.c
+SRCS+= eng_rsax.c
# XXX unnecessary? handled in EVP now...
# SRCS+= eng_aesni.c # local addition