Bug 1012626
| Summary: | [FIPS140] dracut-fip updates needed for certification | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Steve Grubb <sgrubb> | |
| Component: | dracut | Assignee: | Harald Hoyer <harald> | |
| Status: | CLOSED ERRATA | QA Contact: | Marian Ganisin <mganisin> | |
| Severity: | high | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 6.5 | CC: | borgan, dracut-maint-list, ebenes, jrieden, mganisin, notting, omoris, sforsber, tlavigne, tmraz | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | dracut-004-330.el6 | Doc Type: | Enhancement | |
| Doc Text: |
Feature:
A file marker /etc/system-fips should be present, if the rpm package dracut-fips is installed.
Reason:
We need have a stable file location for fips product determination. NIST has new requirements that causes us to need to define the FIPS module as the crypto system + the dracut-fips package. Libraries and applications will need to look for the presence of the file to know that this is a FIPS product rather than an ordinary product.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1014284 (view as bug list) | Environment: | ||
| Last Closed: | 2013-11-21 21:58:29 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 968473 | |||
|
Description
Steve Grubb
2013-09-26 18:15:36 UTC
The modules that were added in 6.5 are: gcm(aes) cts(cbc(aes) gcm(aes-aesni) ctr(aes-aesni) cts(cbc(aes-aesni)) changed the file from /etc/redhat-fips to /etc/system-fips dracut-004-330.el6 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-1674.html |