From: "chiasa.men" <chiasa.men@web.de>
To: dm-crypt@saout.de
Subject: [dm-crypt] unlock via password and device
Date: Tue, 10 Nov 2020 10:04:02 +0100 [thread overview]
Message-ID: <10785019.O7vmMJN3CY@march> (raw)
For the purpose of full disc encryption the tutorials usually suggest to
decrypt luks via usbkey.
The keyscript then often waits the key to appear for several seconds, after
that they fall back to the password prompt.
If the key appears after the waiting time it is ignored.
Is there a way to "step back" after the password prompt appeared?
The current workaround is another process that loops for the key in the
background, decrypts the disk and kills "askpass" several times (resulting in
"wrong password" in the main process)
What would be a clean way to implement the wanted behavior?
As I understood, the keyscript has to print the key to stdout.
I would expect the following keyscript construct to work as well:
---
while luksNotOpened
if [ -e key ]
dd if=key
sleep 1
done &
askpass
---
The background process should still print to stdout and I guess askpass would
do the same when enter is pressed?
However that does not work
next reply other threads:[~2020-11-10 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 9:04 chiasa.men [this message]
2020-11-10 17:34 ` [dm-crypt] unlock via password and device Arno Wagner
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=10785019.O7vmMJN3CY@march \
--to=chiasa.men@web.de \
--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