Date: Sat, 02 Jan 2016 20:48:05 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 205800] random device not loaded; using insecure entropy Message-ID: <bug-205800-8-7f0oZwHMUo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205800-8@https.bugs.freebsd.org/bugzilla/> References: <bug-205800-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205800 Marie Helene Kvello-Aune <marieheleneka@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marieheleneka@gmail.com --- Comment #3 from Marie Helene Kvello-Aune <marieheleneka@gmail.com> --- I'm seeing this as well, on a Xeon D 1520 (http://ark.intel.com/products/87038/Intel-Xeon-Processor-D-1520-6M-Cache-2= _20-GHz), supermicro X10SDV-4C-TLN2F mainboard. (http://www.supermicro.nl/products/motherboard/xeon/d/X10SDV-4C-TLN2F.cfm)= =20 (uname -a: FreeBSD saturn 10.2-STABLE FreeBSD 10.2-STABLE #0 r293044: Sat J= an=20 2 01:35:51 CET 2016 root@saturn:/usr/obj/usr/src/sys/GENERIC amd64) Not seeing it in FreeBSD 11-CURRENT running in vmware on a Xeon E5-1650v3. (this is using random: fast provider: "Intel Secure Key RNG" ) Seeing it on bare metal 10-STABLE running on a Xeon E5-1620v2. All CPUs support "Secure Key". Will install 11-current on the Xeon D and se= e if it works as expected then. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205800-8-7f0oZwHMUo>