Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 417271 (RHEL5.1-DiskEnc)

Summary: RHEL 5.2 Full Disk Encryption Tracker
Product: Red Hat Enterprise Linux 5 Reporter: Daniel Riek <riek>
Component: distributionAssignee: Daniel Riek <riek>
Status: CLOSED CURRENTRELEASE QA Contact: Daniel Riek <riek>
Severity: high Docs Contact:
Priority: high    
Version: 5.2CC: agk, cbolz, codezilla, c.shoemaker, degts, dgunchev, duck, jim, karsten, kzak, mbroz, pjones, pknirsch, redhat-bugzilla, riek, sfolkwil, theo_nra
Target Milestone: ---Keywords: FutureFeature, Tracking
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-02 16:05:53 UTC Type: ---
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: 211247, 229865, 326611, 360071, 360621    
Bug Blocks: 459600    

Description Daniel Riek 2007-12-09 15:36:47 UTC
Full Disk Encryption is a government requirement for 5.2. This bug tracks the
changes required,

Comment 1 Daniel Riek 2007-12-09 16:41:28 UTC
[:Usecase:]

There are two main use-cases we are adressing for 5.2:

* Corporate Laptop
   1. User loses laptop with confidential corporate information.
   2. Data is protected from unauthorized access.
         1. Note: Also the swap space is protected 
   3. User receives new laptop and needs to access backup.
   4. User leaves company and critical corporate information is 
      accessed by the corporate IT department. 

* High Security Laptop
   1. The user is authenticated using a smartcard
   2. The attacker is not able to access the system disks
   3. The swap space is protected 

The Corporate Laptop use case is considered mandatory, the
smartcard-authentication is high priority but not a blocker.

The use cases basically translates to full-disk encryption support. So the
requirements are:
* dm-crypt encryption support in the initrd / boot process (mandatory).
** i18n support is desirable but not required for RHEL5 minor releases.
* hibernate / suspend support for encrypted swap space (mandatory).
* setup at least post-install (anaconda support is considered too intrusive)
(mandatory).
* smartcard authentication support in initrd

One option for the installation would be support in livecd-creator.


Comment 2 Sam Knuth 2008-03-04 21:54:46 UTC
Can you confirm if kickstart support is a requirement? We'd like to see that in
5.3. So far F9 seems to be doing what we want with this exception (option only
exists in GUI)

Comment 3 Tony Fu 2008-10-06 01:46:27 UTC
User krafthef's account has been closed

Comment 4 Taunus 2009-03-05 12:53:00 UTC
Of course it should be possible to set encryption on in kickstart.

What is the current status?

Comment 5 Chris Shoemaker 2009-05-23 02:43:49 UTC
AFAICT, it's not yet possible to set encryption in kickstart/livecd-creator.

Comment 6 Taunus 2010-05-14 10:49:45 UTC
There is kickstart encryption in rhel 6 beta and it seems to be working.

Comment 7 Taunus 2010-12-08 07:10:47 UTC
I would close this one since el6 has this feature.