summaryrefslogtreecommitdiffstats
path: root/sys/i386
diff options
context:
space:
mode:
authorkib <kib@FreeBSD.org>2012-09-05 13:18:51 +0000
committerkib <kib@FreeBSD.org>2012-09-05 13:18:51 +0000
commitdac91f5998c1d33695196e636176f5634af60f74 (patch)
tree4e5e06d435f26a7ff60ca89f3247cc53bec9401b /sys/i386
parent71dbd73468d207cc6328627d0f16d719bad326c8 (diff)
downloadFreeBSD-src-dac91f5998c1d33695196e636176f5634af60f74.zip
FreeBSD-src-dac91f5998c1d33695196e636176f5634af60f74.tar.gz
Add support for new Intel on-CPU Bull Mountain random number
generator, found on IvyBridge and supposedly later CPUs, accessible with RDRAND instruction. From the Intel whitepapers and articles about Bull Mountain, it seems that we do not need to perform post-processing of RDRAND results, like AES-encryption of the data with random IV and keys, which was done for Padlock. Intel claims that sanitization is performed in hardware. Make both Padlock and Bull Mountain random generators support code covered by kernel config options, for the benefit of people who prefer minimal kernels. Also add the tunables to disable hardware generator even if detected. Reviewed by: markm, secteam (simon) Tested by: bapt, Michael Moll <kvedulv@kvedulv.de> MFC after: 3 weeks
Diffstat (limited to 'sys/i386')
-rw-r--r--sys/i386/conf/GENERIC2
1 files changed, 2 insertions, 0 deletions
diff --git a/sys/i386/conf/GENERIC b/sys/i386/conf/GENERIC
index b542e1c..74829b8 100644
--- a/sys/i386/conf/GENERIC
+++ b/sys/i386/conf/GENERIC
@@ -305,6 +305,8 @@ device wpi # Intel 3945ABG wireless NICs.
# Pseudo devices.
device loop # Network loopback
device random # Entropy device
+options PADLOCK_RNG # VIA Padlock RNG
+options IVY_RNG # Intel Bull Mountain RNG
device ether # Ethernet support
device vlan # 802.1Q VLAN support
device tun # Packet tunnel.
OpenPOWER on IntegriCloud