Comment 14 for bug 430496
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote Re: cryptsetup: blocks | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Damn, the cryptsetup kludged worked for me in the setup I created.
I guess we need to figure it out properly; I would appreciate help from people who actually know and use this stuff.
Basically how it *should* work is that there should be a udev rule or upstart job (maybe the latter since it has to block for input) that detects an encrypted block device, asks for the passphrase, and then creates the unencrypted block device.
(udev will then see the unencrypted device, and mountall will be able to mount it)