From: Fourhundred Thecat <400thecat@gmx.ch>
To: dm-crypt@saout.de
Subject: [dm-crypt] cryptsetup: luksFormat: requires <device> as arguments
Date: Sat, 25 Jul 2020 15:42:34 +0200 [thread overview]
Message-ID: <a0e97bd3-9a9c-5086-75fd-53c13d067869@gmx.ch> (raw)
Hello,
I am trying to create a new detached luks header, but the command fails:
cryptsetup -v --type luks1 --cipher aes-xts-plain64 --key-size 512
--hash sha512 --use-random luksFormat /dev/null --header LUKS-HEADER
--align-payload=0
WARNING!
========
This will overwrite data on LUKS-HEADER irrevocably.
Are you sure? (Type uppercase yes): YES
Enter passphrase for LUKS-HEADER:
Verify passphrase:
Device /dev/null is not compatible.
Command failed with code -3 (out of memory).
And when I ommit /dev/null, then I get another error:
cryptsetup: luksFormat: requires <device> [<new key file>] as arguments
Why does cryptsetup require a device, when I am formatting the detached
luks header? No device is involved at this point. All I want is to
create header file.
How can I create a header, without specifying the device ?
thanks,
next reply other threads:[~2020-07-25 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 13:42 Fourhundred Thecat [this message]
2020-07-25 15:41 ` [dm-crypt] cryptsetup: luksFormat: requires <device> as arguments Milan Broz
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=a0e97bd3-9a9c-5086-75fd-53c13d067869@gmx.ch \
--to=400thecat@gmx.ch \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).