Description of problem: Added an encrypted tmp partition in /etc/crypttab, e.g.: tmp-crypt /dev/mapper/vg0-lv_tmp /dev/urandom tmp,cuper=aes-cbc-essiv:sha256 which is then mounted in /etc/fstab : /dev/mapper/tmp-crypt /tmp ext2 defaults 1 2 On boot, the tmp-crypt entry in crypttab is skipped on the first pass of rc.sysinit:init_crypto() as it has a random key. However, this means the device doesn't yet exist when entries in fstab are automounted - which fails, and drops to the filesystem recovery prompt. Version-Release number of selected component (if applicable): initscripts-8.45.7-1 How reproducible: Always Steps to Reproduce: 1. Create crypttab for a tmp partition with random key 2. Mount said encrypted partition as tmp in fstab 3. Actual results: Mount of /tmp fails; on boot drops to filesystem recovery prompt Expected results: /tmp mounts Additional info:
%s/cuper/cipher/g
I encountered the exact same problem. The swap option in crypttab seems to work with init_crypto() in rc.sysinit, but the tmp option does not. It looks like neither mke2fs nor mktemp execute successfully in the init_crypto() script, and /dev/mapper/$dst is left unformatted. Boot fails when fstab gets to it.
The same problem as described by the reporter appears also in Fedora 7 with initscripts-8.54.1-1. The crypttab file is processed twice, first without the random data source and then with it. The encrypted tmp is created during the second pass, but the filesystems are already mounted at that stage. I have configured the fstab entry with 0 as the last field, because a freshly created filesystem does not need checking. There is no recovery prompt, the system starts normally. Just the /tmp is not on a separate encrypted partition as it should be, but it is a normal unencrypted subdirectory on the root filesystem.
Exact same issue is still present in Fedora 8 Test 3. When might we expect some attention to this?
Still experiencing this on Fedora 9 with current updates - as described previously the crypttab entry seems to work, but /tmp need to be mounted before the second pass of crypttab in which the encrupted tmp is set up. Randomly encrypted swap in crypttab works fine.
This appears to be related to 250881.
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.
Still present on F11 initscripts-8.95-1.i586 It would indeed seem related to bug #250881 (possibly a dupe) - I'll try the patch there in a minute (once I've found a rescue disk!).
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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
*** This bug has been marked as a duplicate of bug 667282 ***