Public bug reported:
Binary package hint: cryptsetup
crypttab entries are not processed at start up.
There are both upstart and SysV init.d entries from the cryptsetup package at
/etc/init/cryptdisks-enable.conf
/etc/init/cryptdisks-udev.conf
/etc/init.d/cryptdisks
/etc/init.d/cryptdisks-early
/etc/init.d/cryptdisks-enable
/etc/init.d/cryptdisks-udev
Here is an example of a crypttab entry which worked in Karmic but does
not in Lucid.
SwapSpace /dev/disk/by-id/usb-YourUSBMassStorageHere-0:0-part1
/dev/urandom swap,cipher=anubis,size=320,hash=sha384
running
cryptdisks_start SwapSpace
In this case correctly creates the device.
The mass storage is available by USB. As far as I know, there could be
timing problems in it's availability or the constructing of entries
under /dev/disk/by-id.
ProblemType: Bug
Architecture: i386
Date: Mon Feb 15 22:09:16 2010
DistroRelease: Ubuntu 10.04
Package: cryptsetup 2:1.1.0~rc2-1ubuntu11
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SourcePackage: cryptsetup
Uname: Linux 2.6.32-13-generic i686
crypttab:
This information should not be put in automatically, I think.
** Affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 lucid
--
crypttab entries not processed automatically at startup despite upstart files
https://bugs.launchpad.net/bugs/522341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
