Re: automatic mounting of an encrypted harddrive
On Sun, Nov 08, 2009 at 21:48:05 +0100, Tobias Schula wrote:
> Am Sonntag 08 November 2009 14:34:45 schrieb Florian Kulzer:
> > On Sun, Nov 08, 2009 at 13:01:36 +0100, Tobias Schula wrote:
[...]
> > > Ah, I see, this is the output on my computer:
> > > # /sbin/blkid -p /dev/sdc1
> > > /dev/sdc1: ambivalent result (probably more filesystems on the device)
[...]
> > > After these steps I was able to plug it in and the KDE device notifier
> > > showed me the new drive. But I didn't set it up in Debian but in Kubuntu
> > > if that's important.
> >
> > I cannot find anything wrong with your procedure. I think the fact that
> > you used Kubunutu should not matter.
Denken ist Glückssache...
[...]
> # hd -n 80 /dev/sdc1
> 00000000 4c 55 4b 53 ba be 00 01 61 65 73 00 00 00 00 00 |LUKS....aes.....|
> 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 00000020 00 00 00 00 00 00 00 00 78 74 73 2d 70 6c 61 69 |........xts-plai|
> 00000030 6e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |n...............|
> 00000040 00 00 00 00 00 00 00 00 73 68 61 31 00 00 00 00 |........sha1....|
> 00000050
>
>
> Here's one strange thing: I encrypted USB flash drive following the steps
> above. But this time it works! What's the difference between the two?
[...]
> # hd -n 80 /dev/sdc1
> 00000000 4c 55 4b 53 ba be 00 01 61 65 73 00 00 00 00 00 |LUKS....aes.....|
> 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 00000020 00 00 00 00 00 00 00 00 63 62 63 2d 65 73 73 69 |........cbc-essi|
> 00000030 76 3a 73 68 61 32 35 36 00 00 00 00 00 00 00 00 |v:sha256........|
> 00000040 00 00 00 00 00 00 00 00 73 68 61 31 00 00 00 00 |........sha1....|
> 00000050
>
> It seems that Ubuntu uses xts-plain but Sid cbc-essiv and the SHA-256
> algorithm. But it's strange that both drives are recognised by Kubuntu but
> only the flash drive by Debian.
It looks like blkid has a bug that has been fixed in Ubuntu, see their
changelog of util-linux:
util-linux (2.16-1ubuntu5) karmic; urgency=low
* Always return encrypted block devices as the first detected encryption
system (ie. LUKS, since that's the only one) rather than probing for
additional metadata and returning an ambivalent result. LP: #428435.
-- Scott James Remnant <scott AT ubuntu DOT com> Wed, 21 Oct 2009 14:22:31 +0100
You can file a bug report against Debian's util-linux and ask the
maintainer to take over the Ubuntu fix.
--
Regards, |
Florian |
Reply to: