On 06/20/2013 12:03 PM, Jan Janssen wrote: > Hi, > > I just stumbled upon truecrypt support in cryptsetup. It sounds nice, > but there is one big issue that prevents it from being useful in > situations where the truecrypt partition is encrypted using system mode > and other partitions on the drive are mounted/in use (such as dual boot > on a single drive system). > > There is this small limitation that you have to specify the > whole device for opening tcrypt system devices. And the fact that > tcryptOpen refuses to open if that device is mapped/mounted already > prevents me from using cryptsetup altogether for my truecrypt partition. > > It would be nice if this could be fixed/worked around with. Hi, well, you are probably the first real user I know about who tried system encryption truecrypt mapping :) So it is quite possible there are some problems. Please can you describe exactly you configuration (I think I understand the problem but exact description could be better.) Why is main device used? Mapped/mounted other partition or something else? Should be easy to fix I think (we have already --shared option for plain mode). (If you are able to map it with normal truecrypt in Linux, output of lsblk with encryption mapping active should be enough for me.) Thanks, Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
