Am Donnerstag, 13. September 2007 schrieb ext Harald Dunkel:
> > > This would allow to run cryptsetup without having to mess
> > > around with dmesg and /proc/partitions to find the next
> > > device name of the encrypted USB stick.
> >
> > Write a udev rule to give it a unique name, like /dev/usb/stick.
>
> AFAICS this would rely too much upon information local to
> each Linux box.
??? If the rule is the same, the created name ist the same.
> The requirement would be to store the symbolic name for the
> encrypted(!) file system on the device itself.
Derive the name from the original device name, i.e.
like /dev/usb/stick -> /dev/mapper/c-stick ("c-" for crypted). If you
follow a consistant scheme, there should be no problem.
> If the name changes with each
> PC the USB stick is plugged into, then there is no real
> advantage over using something like "/dev/sdb3".
See above. Each PC must have the same udev rule. It could also be a more
generic one, like: "Look for a file named "cryptmappings" on the first
(unencrypted) partition and run a script that creates the mappings if the
file exists".
HTH...
Dirk
--
Dirk Heinrichs | Tel: +49 (0)162 234 3408
Configuration Manager | Fax: +49 (0)211 47068 111
Capgemini Deutschland | Mail: dirk.heinrichs@xxxxxxxxxxxxx
Wanheimerstraße 68 | Web: http://www.capgemini.com
D-40468 Düsseldorf | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net
Attachment:
signature.asc
Description: This is a digitally signed message part.
