[dm-crypt] blkid and aes-cbc-plain/aes-cbc-essiv:sha256

.. ink .. mhogomchungu at gmail.com
Mon Mar 12 22:30:02 CET 2012

when a plain volume is created with "aes-cbc-plain" and opened with
"aes-cbc-essiv:sha256", the blkid program correctly reads the file system
of the volume but mount command fails to mount it. Is this behavior
expected behavior?

I am the developer of zulucrypt, the frontend to cryptsetup and i support
both by first trying to open the volume with "aes-cbc-essiv:sha256" and
then with "aes-cbc-plain" if the former fail.This allows the tool to
seamlessly open "old" plain  volumes in legacy mode

The above works but the mount system call adds ugly looking logs to
/var/syslog when it fails to mount the volume the first time around i am
trying to see if i can get around this.

It would have been great if blkid  would fail to read the file system to
tell me the plain volume is opened in wrong mode but it reads it correctly
leaving it up to mount command to notice the wrong mode and then fail to
mount and add the ugly looking log entry.

can i use any cryptsetup API to distinguish volumes created with those two
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.saout.de/pipermail/dm-crypt/attachments/20120312/f1288f59/attachment.html>

More information about the dm-crypt mailing list