From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Wed, 23 Mar 2011 17:26:51 +0100 (CET) Message-ID: <4D8A1F48.8020904@redhat.com> Date: Wed, 23 Mar 2011 17:26:48 +0100 From: Milan Broz MIME-Version: 1.0 References: <4D7E53E5.3040007@redhat.com> <20110314221329.19d588ea@gmail.com> <4D87973E.1090300@redhat.com> <20110322194725.3b104ed5@gmail.com> <4D88F404.30607@redhat.com> <20110322214404.2592589a@gmail.com> <4D890F02.6010803@redhat.com> <20110323151445.733a8058@gmail.com> <4D8A05BC.8060408@redhat.com> <20110323170055.189425c8@gmail.com> In-Reply-To: <20110323170055.189425c8@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.3.0-rc1 (test release candidate) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rudolf Deilmann Cc: dm-crypt@saout.de On 03/23/2011 05:00 PM, Rudolf Deilmann wrote: > Am Wed, 23 Mar 2011 15:37:48 +0100 > schrieb Milan Broz : > >> BTW key size 160 bits? strange size. for which cipher? >> Probably kernel cryptoAPI module limitation, there should be no limit >> in dmcrypt. > > it's mentioned for twofish and blowfish in my manpage of losetup > (losetup/loop-aes accepts even other key lengths. I don't know, > if this behaviour is intentend or make sense at all ) ok, just quickly reading twofish cryptoAPI implementation in kernel, it seems to not support 160bit (just 128, 192, 256). so neither cryptsetup nor dmcrypt problem. Milan