Bug 857765

Summary: rngd should be run by default
Product: [Fedora] Fedora Reporter: H. Peter Anvin <hpa>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: amit.shah, jcapik, jgarzik, johannbg, lnykryn, metherid, mschmidt, msekleta, notting, plautrba, systemd-maint, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: systemd-195-13.fc18 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-11 14:22:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description H. Peter Anvin 2012-09-16 23:25:45 UTC 
Description of problem:
Running Fedora 18 Alpha with updates on an Ivy Bridge system, rngd is not started by default.

Per FESCo decision it should be run by default:

https://fedoraproject.org/wiki/Features/rngd_default_on

Version-Release number of selected component (if applicable):
rng-tools-4-1.fc18.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install rng-tools on an Ivy Bridge system or any other system with a hardware RNG
2. ps ax | grep rngd
   observe it is not running
3. service rngd start
   observe it can be started  
  
Actual results:
rngd run by default

Expected results:
rngd available, but not on by default

Additional info:
Comment 1 H. Peter Anvin 2012-12-07 21:04:03 UTC 
rngd is still disabled by default in Fedora 18 Beta.
Comment 2 Michal Schmidt 2012-12-10 13:16:26 UTC 
added rngd.service to the default presets:
http://pkgs.fedoraproject.org/cgit/systemd.git/commit/?h=f18
Comment 3 Lennart Poettering 2013-01-11 13:35:02 UTC 
hpa, out of curiosity: why is this done in a userspace component rather than inside the kernel?
Comment 4 H. Peter Anvin 2013-01-11 23:41:42 UTC 
Long, sordid reasons -- short answer: some of the operations involved (FIPS test, whitening) are complex and considered too heavyweight to be done in kernel space.
Comment 5 Zbigniew Jędrzejewski-Szmek 2014-12-10 15:18:31 UTC 
*** Bug 893342 has been marked as a duplicate of this bug. ***