On mar., 2011-11-29 at 18:31 +0100, Arno Wagner wrote: > If you actually want to remove the LUKS mapping (i.e. "close" the > LUKS container) when the screen safer engages and remap the LUKS > container when the screensaver is unlocked, then this is complicated. > It mau also not be what you want, given that unmapping the LUKS > container with open files is eiter not possible or can result in > arbitrary data corruption (I have not tried it). So you would > need to do something like this on screenlocker-engage: > > 1. Determine all open files in the LUKS container > 2. Terminate all applications that have these files open > 3. Unmount the LUKS container and verify it did unmount. > If unmount fails, go to 1. (An application could have opened > a file in between...) Maybe you can also do a ro remount first. > 4. Unmap the LUKS container. > > Now, this would need to be somehow script-driven from the > screensaver. Whether automated application clsoe is a good idea > depends very much on the situation and is generally _not_ a good > idea. > What about luksSuspend operation? Regards, -- Yves-Alexis
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
