From FedoraProject

< QA‎ | TestCases

Revision as of 13:18, 11 August 2008 by Mganisin (talk | contribs) (New page: == Description == Support the use of encrypted filesystems for anything other than /boot using cryptsetup and LUKS. This includes install time creation/configuration, as well as integrated...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Description

Support the use of encrypted filesystems for anything other than /boot using cryptsetup and LUKS. This includes install time creation/configuration, as well as integrated support in mkinitrd and initscripts (others?). Currently we are only pursuing support for encrypted devices using cryptsetup/LUKS.

When using encrypted file systems/block devices, the functionality should continue to work as expected, and not create situations where the encryption leads to undesired errors.

References:

  1. Anaconda/Features/EncryptedBlockDevices
  2. Releases/FeatureEncryptedFilesystems

Steps To Reproduce

  • start the installer
  • enter the disk druid paritioning screen
  • select an existing RAID device member partition (such as sda1), OR

create a new RAID device member partition

  • select the "encrypt" checkbox for the partition
  • enter a passphrase for the partition
  • continue the installation

Expected Results

in post-install system, verify:

  • a passphrase for each encrypted RAID device member partition is required to access it
  • an entry for the partition exists in /etc/crypttab