Description of problem: As described in e.g. http://fedoraproject.org/wiki/Security_Guide/9/LUKSDiskEncryption#Step-by-Step_Instructions step 5 or http://www.saout.de/tikiwiki/tiki-index.php?page=EncryptedDeviceUsingLUKS step 1b, a device that is to be encrypted should first be initialised with random data in order to increase security. AFAIK, this is not done in any version of anaconda today.
+1 I guess we'll want an option 'be unsafer and do not fill with random data first' for those users that are impatient and just want the warm fuzzy feeling of having enabled encryption without having the patience for good encryption.
The amount of time it takes to fill a gigabyte of disk space, combined with size of today's drives, prohibits enabling this by default. This isn't even taking into account the relative lack of entropy on a system running only anaconda. It might be useful to add a checkbox (disabled by default) which, if enabled, causes the device to be filled with random data prior to encryption. The question then becomes: do we use /dev/urandom or badblocks?
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.