> 1. call "blkid" and check the file system on the device,if its present andAnd i would crash & burn right here. Not all encryption is LUKS!
> its not "crypto_LUKS",then its a device with a normal file system,just
> mount it normally.
I use loopAES v3 encryption (a.k.a. lmk3).
i prefer PLAIN type of cryptsetup.The basic idea still stands,encrypted volumes will cause blkid to return either "crypto_LUKS" or nothing.This is the easiest way to identify an encrypted volume.
any particular reason why you prefer loopAES over plain type of cryptsetup?
There are zero identifiable features in a file or block-device that is
loopAES (any version) encrypted. Just like plain encryption. And if i
understood it correctly, this is also true for e.g. a Truecrypt
container.
yap,truecrypt works the same way.
And my personal model has also a splash of special-sauce. My "whole
disc" encryption is from sector 8 until the end of device. So i can put
a dummy-MBR on each HDD in which i can stamp the name. This name in turn
is used in a udev-rule to create a symlink that identifies the connected
HDD. And last but not least, there is the matching autofs configuration,
so i can just cd /misc/<name> after connecting the corresponding HDD.
why dont you use udev links created in "/dev/disk/by-id/" to access your HDD? it seem like
you are doing something udev is already doing and wasting a bit of space in the process.
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
