From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Tue, 30 Dec 2014 03:32:59 +0100 (CET) Received: from [192.168.99.197] ([70.187.182.227]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LzskF-1XjlWb3hkx-014xVh for ; Tue, 30 Dec 2014 03:32:59 +0100 Message-ID: <54A20EDA.9030400@gmx.net> Date: Mon, 29 Dec 2014 18:32:58 -0800 From: "msalists@gmx.net" MIME-Version: 1.0 References: <549E63FE.8020602@gmx.net> <20141227101133.GA21707@tansi.org> <54A1A63D.5060604@gmx.net> <54A1AB87.1070804@yahoo.com> In-Reply-To: <54A1AB87.1070804@yahoo.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Asustor NAS and cryptsetup 1.6.1 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de 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 ?