From: Christoph Anton Mitterer <calestyo@scientia.net>
To: dm-crypt@saout.de
Subject: [dm-crypt] Re: Reading the passphrase from a key-file
Date: Fri, 14 May 2021 16:12:27 +0200 [thread overview]
Message-ID: <ed25163751e0601433d07437397fe57cee90f19f.camel@scientia.net> (raw)
In-Reply-To: <286a7fed-2e24-b622-d9fd-ed3445a547be@gmail.com>
On Fri, 2021-05-14 at 15:41 +0200, Milan Broz wrote:
> But if the input is a binary file, it will stop on the first EOL
> (then you must use --keyfile-size).
> Please read "NOTES ON PASSPHRASE PROCESSING FOR LUKS" in the man
> page.
The manpage might be a bit ambiguous there, it says:
>From key file: The complete keyfile is read up to the compiled-in
>maximum size. Newline characters do not terminate the input.
What exactly is a key file here?
I assume "luksFormat <device> [<key file>]" definitely counts to it.
Thus everyone who created his volumes like this, should be on the safe
side (an quickly notice in any other operations, if he doesn't use the
full key), right?
Same, when "--key-file=someActualFile luksFormat <device>" is used, I
guess.
But what about when --key-file=- is used?
That's kind of a mix between "key file" and stdin, the later which is
documented to end et EOL.
I strongly hope in that case it also read the *full* stdin?
Cheers,
Chris.
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
next prev parent reply other threads:[~2021-05-14 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 11:51 [dm-crypt] Reading the passphrase from a key-file Volker Dormeyer
2021-05-14 13:41 ` [dm-crypt] " Milan Broz
2021-05-14 13:53 ` Arno Wagner
2021-05-14 14:12 ` Christoph Anton Mitterer [this message]
2021-05-14 15:22 ` Clemens Fruhwirth
2021-05-14 15:50 ` Milan Broz
2021-05-14 18:10 ` Clemens Fruhwirth
2021-05-14 20:43 ` Milan Broz
2021-05-15 7:08 ` Clemens Fruhwirth
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=ed25163751e0601433d07437397fe57cee90f19f.camel@scientia.net \
--to=calestyo@scientia.net \
--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;
as well as URLs for NNTP newsgroup(s).