From: "msalists@gmx.net" <msalists@gmx.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Asustor NAS and cryptsetup 1.6.1
Date: Mon, 29 Dec 2014 18:32:58 -0800 [thread overview]
Message-ID: <54A20EDA.9030400@gmx.net> (raw)
In-Reply-To: <54A1AB87.1070804@yahoo.com>
On 2014-12-29 11:29, Quentin Lefebvre wrote:
> On 29/12/2014 20:06, msalists@gmx.net wrote :
>> Assuming I did create the container with aes-cbc-essiv:sha256; would
>> cryptsetup automatically figure out the correct parameters when it is
>> subsequently called without those parameters to mount the container?
>> Or do non-default parameters at creation time require the same
>> non-default parameters again for subsequent mounts?
>
> As you may have understood, in plain mode, there is no header, so no
> way for cryptsetup to guess the algorithm used. Thus, if it is a
> non-default one, it must be specified also at mount time.
>
Hm, makes sense. Is there some kind of a config file that I could
specify the parameters in, and that would be read prior to using the
defaults - similar to how some parameters for mount can be specified in
/etc/fstab ?
next prev parent reply other threads:[~2014-12-30 2:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 7:47 [dm-crypt] Asustor NAS and cryptsetup 1.6.1 msalists
2014-12-27 10:11 ` Arno Wagner
2014-12-29 19:06 ` msalists
2014-12-29 19:29 ` Quentin Lefebvre
2014-12-30 2:32 ` msalists [this message]
[not found] ` <20141230100413.GA11208@tansi.org>
2014-12-30 18:18 ` msalists
2014-12-30 19:16 ` Sven Eschenberg
2014-12-31 7:26 ` Arno Wagner
2014-12-30 0:37 ` Claudio Moretti
2014-12-30 1:00 ` msalists
2014-12-30 1:46 ` Arno Wagner
2014-12-30 2:11 ` msalists
-- strict thread matches above, loose matches on Subject: below --
2014-12-27 3:49 msalists
2014-12-27 7:38 ` 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=54A20EDA.9030400@gmx.net \
--to=msalists@gmx.net \
--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.