From: Quentin Lefebvre <qlefebvre_pro@yahoo.com>
To: dm-crypt@saout.de
Cc: 0x14@openmailbox.org
Subject: Re: [dm-crypt] Pass+keyfile
Date: Mon, 01 Dec 2014 14:49:54 +0100 [thread overview]
Message-ID: <547C7202.7040806@yahoo.com> (raw)
In-Reply-To: <20141201124959.GA29600@tansi.org>
Hi,
I guess his point was to build something like a strong authentication with:
(1) something that I *own* (a key, maybe on a USB key),
(2) something that I *know* (a passphrase).
This doesn't look too bad to me.
But maybe it's worth remembering hash algorithms are ignored with key
files in plain mode, so that the --hash=sha512 is not effective and
actually equivalent to --hash=plain in this case.
Best regards,
Quentin
Le 01/12/2014 13:49, Arno Wagner a écrit :
>
> 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.
next prev parent reply other threads:[~2014-12-01 13:49 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
2014-12-01 13:49 ` Quentin Lefebvre [this message]
-- 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=547C7202.7040806@yahoo.com \
--to=qlefebvre_pro@yahoo.com \
--cc=0x14@openmailbox.org \
--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