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 15:37:51 +0100 (CET) Message-ID: <4D8A05BC.8060408@redhat.com> Date: Wed, 23 Mar 2011 15:37: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> In-Reply-To: <20110323151445.733a8058@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 03:14 PM, Rudolf Deilmann wrote: > On Tue, 22 Mar 2011 22:05:06 +0100 > Some features are missing (key size 160 for dmcrypt, and various > losetup-switches (phash,itercountk), but it's unclear, if anyone use > them. ( At least as long as loop-aes is still maintained, it's IHMO > not necessary to support exotic settings ) yes, it is expected. I can implement it if anyone uses it but I doubt it is worth it. This is really not targeted as replacement but compatible mode to open existing devices. BTW key size 160 bits? strange size. for which cipher? Probably kernel cryptoAPI module limitation, there should be no limit in dmcrypt. Milan