On Mon, 21 Mar 2011 19:21:50 +0100 Milan Broz <mbroz@xxxxxxxxxx> wrote: > I added offset support, seems loopAES always uses offset==skip > (IOW initial vector is always related to absolute sector size on the > device). No, loopAES supports both options. It depends on user input: -- -o offset The data start is moved offset bytes into the specified file or device. Normally offset is included in IV (initialization vector) computations. If offset is prefixed with @ character, then offset is not included in IV computations. @ prefix functionality may not be supported on some older kernels and/or loop drivers. -- Both options seems to be supported by dmcrypt/dmsetup. In the first case IV offset is always identic to the sector offset, in the second case IV offset is always zero. (IV offset: 6th value at dmsetup table, sector offset: 8th value. I hope, I haven't muddle something ) > I do not plan to add sizelimit option, this can just cause confusion. > > (In fact you can do that using cryptsetup resize command afterwards > or by limiting underlying device. If it is problem, please show me > real example where it is needed.) Sounds reasonable. It's main usage seems to be recovery if your partition table is damaged or similar exceptional things happend. _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
