Bug 1093058

Summary:	[RFE] System installed on an encrypted LUKS device booting and unlocking itself using TPM module
Product:	Red Hat Enterprise Linux 7	Reporter:	Miguel Perez Colino <miguel>
Component:	cryptsetup	Assignee:	Ondrej Kozina <okozina>
Status:	CLOSED WONTFIX	QA Contact:	Storage QE <storage-qe>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.0	CC:	abokovoy, aghadge, agk, cww, fmartine, guazhang, jbrassow, jfenal, loberman, mbroz, miguel, mthacker, okozina, pdwyer, prajnoha, rhandlin, rsawhill, vcojot, zkabelac
Target Milestone:	pre-dev-freeze	Keywords:	FutureFeature, Triaged
Target Release:	7.6
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-11 21:55:36 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:	1418639, 1475904
Bug Blocks:	1477664

Description Miguel Perez Colino 2014-04-30 13:41:15 UTC

1. Proposed title of this feature request
[RFE] System installed on an encrypted LUKS device booting and unlocking itself using TPM module

3. What is the nature and description of the request?
By security policies workstations are required to have the filesystems encrypted so that information cannot be extracted from them.
Booting requires a passphrase to unlock the LUKS device.
In systems with TPM modules, the unlocking can be automatically done using this capability.


4. Why does the customer need this? (List the business requirements here)
To comply with the enterprise security policies.

5. How would the customer like to achieve this? (List the functional requirements here)
LUKS and GRUB being TPM enabled.

6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Deploy a system on LUKS encrypted device. Enable TPM to unlock LUKS device. Boot from GRUB using TPM LUKS unlocking.

7. Is there already an existing RFE upstream or in Red Hat bugzilla?
No

8. Does the customer have any specific timeline dependencies?
ASAP, next release.

9. Is the sales team involved in this request and do they have any additional input?
No

10. List any affected packages or components.
trousers, tpm-tools, trusted-grub, tpm-luks

11. Would the customer be able to assist in testing this functionality if implemented?
Yes.

Comment 8 Mark Thacker 2016-11-30 21:20:37 UTC

I don't think we will have everything we need to get this done in 7.4. However, the proposed delivery of the Network Bound Disk Encryption technology may very well help with setting up an infrastructure for this.
Then again, NBDE isn't required to solve this problem.

I'm not pm_ack'ing this at this point, though would be prepared to do so if we thought it was in-scope for 7.4.

Comment 9 Russell Doty 2016-12-01 14:33:27 UTC

Is the customer requesting this for TPM 1.2 or TPM 2.0?

Note that TPM 2.0 is much more capable than TPM 1.2 and we are planning to invest any development efforts in TPM 2.0. Having said that, we are aware that most of the TPM installed base is TPM 1.2.

Would a TPM 2.0 only implementation meet the customer requirements?

Comment 10 Mark Thacker 2016-12-02 15:41:27 UTC

I'm willing to argue that a TPM 2.0 deliverable would be fine if there is reasonable expectations that TPM 2.0 will be included in the majority of shipping systems by 2017.

Comment 38 Chris Williams 2020-11-11 21:55:36 UTC

Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed. 

From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."

If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook  

Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product. 

Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.  

[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7