[pkg-cryptsetup-devel] Bug#576186: Bug#576186: cryptsetup: Setting up crypto device on Startup takes too long w/ ext3
Jonas Meurer
jonas at freesources.org
Sun Jul 18 20:51:07 UTC 2010
On 08/07/2010 Jonas Meurer wrote:
> > Last line before prompting for passphrase is like:
> > cryptsetup -c -aes-... --key-file=- create cryptofs /dev/sda3
> > After waiting 50 secs, first line is:
> > '[' -z /lib/cryptsetup/checks/vol_id ']'
>
> this verifies, that the delay is caused by cryptsetup binary, not by
> anything else from the initscript. you could check the unlocking
> by booting into single user runlevel (init=1), and manually invoking
>
> # cryptsetup -c aes-cbc-essiv:sha256 create cryptofs /dev/sda3
>
> simply let the unlocking process fail three times (wrong passphrase),
> and the boot process will stop at runlevel 1 with an emergency shell.
> there you can test the manual unlocking of encrypted device.
>
> if this works, and the delay is reproducible at the emergency shell,
> please also provide output of 'cryptsetup --debug -c aes-... create ...'
any news?
greetings,
jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20100718/2792ddb5/attachment.pgp>
More information about the pkg-cryptsetup-devel
mailing list