From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nm5-vm9.bullet.mail.ir2.yahoo.com (nm5-vm9.bullet.mail.ir2.yahoo.com [212.82.96.116]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Mon, 29 Dec 2014 20:29:33 +0100 (CET) Message-ID: <54A1AB87.1070804@yahoo.com> Date: Mon, 29 Dec 2014 20:29:11 +0100 From: Quentin Lefebvre MIME-Version: 1.0 References: <549E63FE.8020602@gmx.net> <20141227101133.GA21707@tansi.org> <54A1A63D.5060604@gmx.net> In-Reply-To: <54A1A63D.5060604@gmx.net> 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: "msalists@gmx.net" , dm-crypt@saout.de 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. Best regards, Quentin