[dm-crypt] inconsistent behavior btw a binary and library call when closing truecrypt volume made up of multiple algorithms

.. ink .. mhogomchungu at gmail.com
Mon Feb 18 05:58:09 CET 2013


test:

1. create a truecrypt volume using multiple algorithms,i went with
AES-twofist-serpent
2. open the volume using cryptsetup with "cryptsetup tcryptOpen ttt ttt"
3. ls -l /dev/mapper/ will give:

crw------- 1 root root 10, 236 Feb 17 22:37 /dev/mapper/control
lrwxrwxrwx 1 root root       7 Feb 17 23:45 /dev/mapper/ttt -> ../dm-2
lrwxrwxrwx 1 root root       7 Feb 17 23:45 /dev/mapper/ttt_1 -> ../dm-1
lrwxrwxrwx 1 root root       7 Feb 17 23:45 /dev/mapper/ttt_2 -> ../dm-0

It looks like 3 mapper will be created,each per algorithm.

closing the mapper with " cryptsetup tcryptClose ttt" will remove all three
mappers expected.

closing the mapper through the library "crypt_deactivate( NULL,"ttt" )"
will not remove all 3,just the "ttt" one.With the library call, all 3 seem
to require to be removed individually.

Is this behavior of the library expected?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.saout.de/pipermail/dm-crypt/attachments/20130217/70e55882/attachment.html>


More information about the dm-crypt mailing list