Cryptsetup is started twice on startup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
Bug Description
Binary package hint: cryptsetup
I tried to use cryptsetup in karmic with a encrypted file (via losetup). Cryptsetup supports this kind of configuration, my /etc/crypttab line looks like this:
# <target name> <source device> <key file> <options>
container /home/user/
However, I couldn't decrypt the file on startup. I started debugging this problem and noticed that the startup function "do_start" from /lib/cryptsetup
In my opinion, the upstart script doesnt work properly, it doesnt support the noearly option from crypttab anyway (the old init.d script is running twice, once with a early parameter (INITSTATE=
Changed in cryptsetup (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: regression-release |