From: Martin Olsson <martinolsson311@yahoo.com>
To: Arno Wagner <arno@wagner.name>
Cc: "cryptsetup@lists.linux.dev" <cryptsetup@lists.linux.dev>
Subject: Re: Password hash as LUKS key
Date: Wed, 15 Mar 2023 15:11:18 +0000 (UTC) [thread overview]
Message-ID: <885982240.717525.1678893078734@mail.yahoo.com> (raw)
In-Reply-To: <20230310011952.GA1141@tansi.org>
On Fri 10, Mar 10, 2023 at 02:19:54 CET, Arno Wagner <arno@wagner.name> wrote:
>You probably have an issue with line endings. In priciple,
>this works and is supported, but interactive, pipe and
>read-from-file are all a bit different.
I see maybe it's something wrong with the way I'm going about this. The following
are the commands I'm running:
mkpasswd (asks me to enter a password, I enter test)
Password:
$y$j9T$35ITJ7yCc3kFUsasf3QDa/$n.HqacKYHPIEE6VxIHhT2vW8.7vfh.fn008SQS5ETb9
printf "%s\n%s\n%s\n" "12345" "$y$j9T$35ITJ7yCc3kFUsasf3QDa/$n.HqacKYHPIEE6VxIHhT2vW8.7vfh.fn008SQS5ETb9"| sudo /sbin/cryptsetup luksAddKey /dev/sda3
(12345 is an existing key, and the password hash is test)
printf "test" | sudo cryptsetup luksOpen --test-passphrase /dev/sda3 && echo "There is a key available with this passphrase."
No key available with this passphrase.
(this shows that test doesn't work to unlock the encrypted partition)
>The man-page has more info on this. Best try it out with a
>really simple password like "test".
Could you point me to what section I should look at? The man page does mention hash
options but they relate to the encryption of the partition rather than the password I input
to cryptsetup.
BR,
Martin
next prev parent reply other threads:[~2023-03-15 15:12 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 [this message]
2023-03-15 16:24 ` Grzegorz Szymaszek
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=885982240.717525.1678893078734@mail.yahoo.com \
--to=martinolsson311@yahoo.com \
--cc=arno@wagner.name \
--cc=cryptsetup@lists.linux.dev \
/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).