From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Steudten Subject: Cryptoloop 2.4.x and 2.6.1 Date: Wed, 14 Jan 2004 16:58:18 +0100 Sender: linux-admin-owner@vger.kernel.org Message-ID: <4005671A.7080909@steudten.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-admin@vger.kernel.org Hi Seems strange. I use the crypto-loop-devices with cipher serpent for a few years. With kernel 2.4.21 i use the patch patch-int-2.4.21.0 or patch-int-2.4.19 and mount --version 2.11u with patches. Everything works fine. My /etc/fstab is: /dev/md9 /crypto ext3 defaults,rw,nodev,noauto,loop,encryption=serpent,offset=1024,errors=remount-ro if i call "mount /crypto" mount ask me for the keysize for the serpent cipher: Available keysizes (bits): 128 192 256 Keysize: 192 And then ask for the password. With the until-linux resp. mount 2.12, no question for the keysize and with same password, the mount fails. I need to test with 2.6.1, if the API from util-linux has changed amd maybe works with 2.6.1.. -- Tom LINUX user since kernel 0.99.x 1994. RPM Alpha packages at http://alpha.steudten.com/packages Want to know what S.u.S.E 1995 cdrom-set contains?