From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane.org>
Received: from lo.gmane.org (lo.gmane.org [80.91.229.12])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Wed, 23 Mar 2011 17:01:11 +0100 (CET)
Received: from list by lo.gmane.org with local (Exim 4.69)
 (envelope-from <glkdd-dm-crypt@m.gmane.org>) id 1Q2QUf-0007Z9-Bn
 for dm-crypt@saout.de; Wed, 23 Mar 2011 17:01:09 +0100
Received: from p5799c668.dip.t-dialin.net ([87.153.198.104])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Wed, 23 Mar 2011 17:01:09 +0100
Received: from rudolf.deilmann by p5799c668.dip.t-dialin.net with local
 (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Wed, 23 Mar 2011 17:01:09 +0100
From: Rudolf Deilmann <rudolf.deilmann@gmail.com>
Date: Wed, 23 Mar 2011 17:00:55 +0100
Message-ID: <20110323170055.189425c8@gmail.com>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] [ANNOUNCE]
	cryptsetup	1.3.0-rc1	(test	release	candidate)
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

Am Wed, 23 Mar 2011 15:37:48 +0100
schrieb Milan Broz <mbroz@redhat.com>:

> 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 )

http://loop-aes.sourceforge.net/ciphers.README mentions twofish160 only.
According to this document, it's necessary for compatibility with suse
8.1 encryption ( together with other unusal and insecure settings).