Anaconda/Features/Encrypted Boot IPA key Management

From FedoraProject

< Anaconda | Features(Difference between revisions)
Jump to: navigation, search
(Current status)
(Owner)
 
(3 intermediate revisions by one user not shown)
Line 6: Line 6:
  
 
== Owner ==
 
== Owner ==
* Name: [Dave Lehman] / [Miloslav Trmač]
+
* Name: [[User:Dlehman|Dave Lehman]] / [[User:Mitr|Miloslav Trmač]]
  
 
== Current status ==
 
== Current status ==
* Completed in F11: 70% - cryptsetup-luks changes are in, <code>volume_key</code> is in rawhide.  Anaconda integration code was prepared, but is not applied yet.
+
* Completed in Fedora 13: 75%
* Last update July 27, 2009
+
* Last update 2010-11-05
  
 
== Detailed Description ==
 
== Detailed Description ==

Latest revision as of 21:43, 5 November 2010

Contents

[edit] Anaconda Encrypted Boot IPA key Management

[edit] Summary

Provide enterprise-class key management support for encrypted devices

[edit] Owner

[edit] Current status

  • Completed in Fedora 13: 75%
  • Last update 2010-11-05

[edit] Detailed Description

Add support for saving encryption keys (to recover access to a volume when the passphrase is forgotten, or when the user leaves a company), and for creating backup passphrases (to be disclosed to the user when the user forgets the passphrase and is on the road). See Key Management for general discussion, Disk encryption key escrow use cases for specifics.

Subtasks:

  • Add two or three small packages (python-volume_key and volume_key-libs, perhaps python-nss) to the installation image
  • Add two kickstart options (#508963) to pykickstart. The options specify an URL for a certificate (to use for encryption, implicitly enables key escrow) and a "create backup passphrase" flag.
  • Add anaconda support: Download the specified certificates, and use the functionality provided by the *volume_key* packages and to store encryption keys or passphrases under $rootPath/root. (#510545)
  • Add system-config-kickstart support for the new kickstart options; needs to integrate with other planned changes to the storage configuration GUI, blocked on those.
  • Add FirstAidKit support for recovering access to encrypted voluems using the stored encryption keys

[edit] Target Audience

Enterprise customers want a means by which they can guarantee access to the data on encrypted block devices in employees' systems. This way they still have a way in if the user changes the device's keys/passphrases.

[edit] Product Variants / High Level Use Cases

Relevant to desktops/laptops particularly, but depending upon implementation may be interesting for other products as well e.g. to support encrypted databases, medical records protection.

[edit] Hardware Architectures

All

[edit] Testing

TBD but should be integrated with anaconda storage testing

[edit] Third-Party Dependencies

Cryptsetup-luks, volume_key, perhaps python-nss, and anaconda interdependencies

[edit] Bugzilla Numbers

  • See Bug 458392 - [RFE] luks: add support for admin keyslot for the prereq from an anaconda POV
Note: The above description does not address the "admin keyslot" requirement. This remains an useful feature, does anybody own it?
  • Bug 488718 - (encrypted_LVM) Support for encrypted LVs in LVM2 & key management (tracker) for a description of work in progress
  • Bug 508960 - tracker for all key escrow work
  • Bug 508963 - Add key escrow options to pykickstart
  • Bug 510545 - (anaconda) RFE: encryption key escrow support
  • Bug 508967 - (system-config-kickstart) RFE: encryption key escrow support