From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Pass+keyfile
Date: Mon, 1 Dec 2014 13:49:59 +0100 [thread overview]
Message-ID: <20141201124959.GA29600@tansi.org> (raw)
In-Reply-To: <e6ee118838efadbac63405f95f9b7be4@openmailbox.org>
This construction is redundant and does not provide any
additional security as compared to passphrase alone,
assuming that your passphrase is secure.
If your passphrase is insecure, you should fix that
instead.
Arno
On Mon, Dec 01, 2014 at 03:54:19 CET, 0x14@openmailbox.org wrote:
> Hi there, is this construction secure? Assuming "keyfile" is a file
> and "/dev/device" is a block device, both made with /dev/urandom.
>
> cryptsetup open --hash=sha512 --cipher=aes-xts-plain64 --type=plain
> keyfile keyfile_tmp && cat /dev/mapper/keyfile_tmp | \
> cryptsetup open --hash=sha512 --cipher=aes-xts-plain64 --type=plain
> --key-file=- /dev/device cryptodevice && \
> cryptsetup close keyfile_tmp && mount /dev/mapper/cryptodevice
> /media/cryptodevice
>
> The goal is to use pass+keyfile to decrypt storage. I put it in a
> script and it works as it should at a glance. Are there alternatives
> or improvements? Stupid errors maybe?
>
> Thanks.
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2014-12-01 12:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 2:54 [dm-crypt] Pass+keyfile 0x14
2014-12-01 12:49 ` Arno Wagner [this message]
2014-12-01 13:49 ` Quentin Lefebvre
-- strict thread matches above, loose matches on Subject: below --
2014-12-01 14:54 0x14
2014-12-01 16:39 ` Arno Wagner
2014-12-01 16:49 ` Sven Eschenberg
2014-12-01 17:37 ` 0x14
2014-12-01 22:25 ` Arno Wagner
2014-12-02 0:15 ` 0x14
2014-12-02 1:03 ` Arno Wagner
2014-12-02 2:43 ` 0x14
2014-12-02 3:31 ` Arno Wagner
2014-12-02 3:51 ` 0x14
2014-12-02 19:16 ` 0x14
2014-12-02 21:02 ` Arno Wagner
2014-12-02 22:48 ` 0x14
2014-12-02 23:22 ` Arno Wagner
2014-12-02 23:40 ` 0x14
2014-12-03 16:15 ` Arno Wagner
2014-12-03 16:19 ` Dragan Milivojević
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=20141201124959.GA29600@tansi.org \
--to=arno@wagner.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.