From: Yves-Alexis Perez <corsac@debian.org>
To: Arno Wagner <arno@wagner.name>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Verify LUKS password
Date: Tue, 29 Nov 2011 18:40:18 +0100 [thread overview]
Message-ID: <1322588418.1932.12.camel@scapa> (raw)
In-Reply-To: <20111129173124.GA20264@tansi.org>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
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 #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-29 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 15:22 [dm-crypt] Verify LUKS password Marcos Barbosa
2011-11-29 17:31 ` Arno Wagner
2011-11-29 17:40 ` Yves-Alexis Perez [this message]
2011-11-29 18:17 ` Arno Wagner
2011-11-29 18:33 ` Marcos Barbosa
2011-11-29 17:42 ` Marcos Barbosa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1322588418.1932.12.camel@scapa \
--to=corsac@debian.org \
--cc=arno@wagner.name \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox