From Fedora Project Wiki

< QA‎ | TestCases

Revision as of 13:19, 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)

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

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 rescue mode functionality should continue to work as expected, and not create situations where the encryption leads to undesired errors; in particular, a user should be able to successfully enter rescue mode for a system that has its root fs on an encrypted block device.

References:

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

Steps To Reproduce

Set up the system that uses one or more of each kind of encryption:

  • encrypted block devices
  • encrypted filesystems

Then start the installer and test:

  • Boot anaconda
  • Proceed to the partitioning dialog
  • Each of the encrypted block devices are correctly identified by anaconda, and require passphrase to access
  • Each of the encrypted file systems are correctly identified by anaconda, and require passphrase to access

Expected Results

  • Verify each of the encrypted block devices are correctly identified by anaconda, and require passphrase to access
  • Verify each of the encrypted file systems are correctly identified by anaconda, and require passphrase to access