From Fedora Project Wiki

< QA‎ | TestCases

(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...)
 
m (internal link cleaning)
 
Line 5: Line 5:
  
 
References:
 
References:
# [https://fedoraproject.org/wiki/Anaconda/Features/EncryptedBlockDevices#Test_Plan Anaconda/Features/EncryptedBlockDevices]
+
# [[Anaconda/Features/EncryptedBlockDevices#Test_Plan|Anaconda/Features/EncryptedBlockDevices]]
# [https://fedoraproject.org/wiki/Releases/FeatureEncryptedFilesystems Releases/FeatureEncryptedFilesystems]
+
# [[Releases/FeatureEncryptedFilesystems|Releases/FeatureEncryptedFilesystems]]
 
== Steps To Reproduce ==
 
== Steps To Reproduce ==
 
* start the installer
 
* start the installer

Latest revision as of 22:08, 17 September 2016

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
  • Create multiple new non-encrypted RAID partitions
  • create one or more non-encrypted filesystems using the RAID partitions
  • continue the installation

Expected Results

in post-install system, verify:

  • install completes successfully
  • RAID partitions are non-eencrypted, and do not have entries in /etc/crypttab
  • none of the filesystems created are encrypted