Displaying 3 results from an estimated 3 matches for "damhtdt".
2015 Mar 04
2
LUKS encypted partition using --key-file can only be decrypted with --key-file
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I created a LUKS encrypted partition via a udev-triggered script on
6.6 using --key-file /tmp/foo. This worked fine, and I can decrypt the
LUKS partition via script and manually using --key-file with luksOpen.
The odd problem is that I can't decrypt the partition using the
prompt. If I manually create a file with the passphrase in it
2015 Mar 04
0
LUKS encypted partition using --key-file can only be decrypted with --key-file
...mply
truncated to the correct length (too short is an error). A key read
from the terminal or from stdin is hashed, then truncated or padded
to the proper length.
See "NOTES ON PASSWORD PROCESSING" in the cryptsetup manpage.
Presumably, if you stored the hashed key phrase in the keyfile
(DAMHTDT) it would work from the terminal without "--hash -plain".
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
2015 Sep 14
1
LUKS encypted partition using --key-file can only be decrypted with --key-file
...length (too short is an error). A key read
> from the terminal or from stdin is hashed, then truncated or padded
> to the proper length.
>
> See "NOTES ON PASSWORD PROCESSING" in the cryptsetup manpage.
> Presumably, if you stored the hashed key phrase in the keyfile
> (DAMHTDT) it would work from the terminal without "--hash -plain".
Reviving a very old thread...
I tried this (cryptsetup --hash plain luksOpen /dev/sdb1 sdb1) but it
fails to recognize the passphrase at the command line still. When I
tried to use '--hash plain' on luksFormat, I get:
[r...