From: Grzegorz Szymaszek <gszymaszek@short.pl>
To: Martin Olsson <martinolsson311@yahoo.com>
Cc: Arno Wagner <arno@wagner.name>, cryptsetup@lists.linux.dev
Subject: Re: Password hash as LUKS key
Date: Wed, 15 Mar 2023 17:24:31 +0100 [thread overview]
Message-ID: <ZBHxP1L7FMpfW600@nx64de-df6d00> (raw)
In-Reply-To: <885982240.717525.1678893078734@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
Hi,
On Wed, Mar 15, 2023 at 03:11:18PM +0000, Martin Olsson wrote:
> printf "%s\n%s\n%s\n" "12345" "$y$j9T$35ITJ7yCc3kFUsasf3QDa/$n.HqacKYHPIEE6VxIHhT2vW8.7vfh.fn008SQS5ETb9"| sudo /sbin/cryptsetup luksAddKey /dev/sda3
1. The format string contains three %s conversion specifications, but
you provide printf with only two operands. Please try something like
the following in your shell:
printf '1. %s 2. %s 3. %s\n' FIRST SECOND
This is probably not an issue since IIRC luksAddKey only asks for
the new passphrase once, so it should ignore the next empty line.
2. In double quotes, a dollar denotes a variable name. For example, in
"$y$j9T", the shell replaces $y and $j9T with the values of the
respective variables. Since they are probably not defined, they are
replaced with empty strings instead. I think the actual password you
set with the above command is
"5ITJ7yCc3kFUsasf3QDa/.HqacKYHPIEE6VxIHhT2vW8.7vfh.fn008SQS5ETb9".
Good luck!
--
Grzegorz Szymaszek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-15 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1738775229.2387123.1678372528163.ref@mail.yahoo.com>
2023-03-09 14:35 ` Password hash as LUKS key Martin Olsson
2023-03-10 1:19 ` Arno Wagner
2023-03-15 15:11 ` Martin Olsson
2023-03-15 16:24 ` Grzegorz Szymaszek [this message]
2023-03-15 20:35 ` Michael Kjörling
2023-03-20 17:06 ` Martin Olsson
2023-03-20 18:53 ` Arno Wagner
2023-03-20 20:38 ` Michael Kjörling
2023-03-21 17:52 ` 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=ZBHxP1L7FMpfW600@nx64de-df6d00 \
--to=gszymaszek@short.pl \
--cc=arno@wagner.name \
--cc=cryptsetup@lists.linux.dev \
--cc=martinolsson311@yahoo.com \
/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