From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by mail.saout.de (Postfix) with ESMTP id 337089778 for ; Wed, 12 Aug 2009 08:24:56 +0200 (CEST) Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tm4Iv8wNIfNp for ; Wed, 12 Aug 2009 08:24:50 +0200 (CEST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mail.saout.de (Postfix) with SMTP for ; Wed, 12 Aug 2009 08:24:50 +0200 (CEST) Message-ID: <4A825F04.5070109@gmx.de> Date: Wed, 12 Aug 2009 08:19:48 +0200 From: Rainer Maier MIME-Version: 1.0 References: <4A8174D3.7000909@gmx.de> <4A8179D4.40807@gmx.at> <20090811212516.39750@gmx.net> <4A81EB67.30002@gmail.com> <20090811224009.300710@gmx.net> <20090811233447.GC31949@resivo.wgnet.de> In-Reply-To: <20090811233447.GC31949@resivo.wgnet.de> Content-Type: text/plain; charset="iso-8859-15"; format="flowed" Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] reinstallation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Hi Jonas, here is the output: ---------------------------------------------------------------------------= ----------------------------- sv3000:~# dpkg -l cryptsetup Gew=FCnscht=3DUnbekannt/Installieren/R=3DEntfernen/P=3DVollst=E4ndig L=F6sc= hen/Halten | Status=3DNicht/Installiert/Config/U=3DEntpackt/Fehlgeschl. Konfiguration/ Halb installiert/Trigger erWartet/Trigger anh=E4ngig |/ Fehler?=3D(kein)/Halten/R=3DNeuinst notw/X=3Dbeide (Status, Fehler:=20 GROSS=3Dschlecht) ||/ Name Version Beschreibung +++-=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D-=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D-=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D un cryptsetup (keine=20 Beschreibung vorhanden) sv3000:~# --> directly in the kernel. ---------------------------------------------------------------------------= ----------------------------- sv3000:~# cryptsetup --version cryptsetup 1.0.6 ---------------------------------------------------------------------------= ----------------------------- sv3000:~# cryptsetup luksDump /dev/sda2 LUKS header information for /dev/sda2 Version: 1 Cipher name: aes Cipher mode: cbc-essiv:sha256 Hash spec: sha1 Payload offset: 1032 MK bits: 128 MK digest: MK salt: MK iterations: 10 UUID: 6c2a5824-5594-4516-885b-4a82a5be9554 Key Slot 0: DISABLED Key Slot 1: ENABLED Iterations: 115171 Salt: Key material offset: 136 AF stripes: 4000 Key Slot 2: DISABLED Key Slot 3: DISABLED Key Slot 4: DISABLED Key Slot 5: DISABLED Key Slot 6: DISABLED Key Slot 7: DISABLED sv3000:~# ---------------------------------------------------------------------------= ----------------------------- sv3000:~# cat /proc/crypto name : aes driver : aes-i586 module : aes_i586 priority : 200 refcnt : 1 type : cipher blocksize : 16 min keysize : 16 max keysize : 32 name : md5 driver : md5-generic module : kernel priority : 0 refcnt : 1 type : digest blocksize : 64 digestsize : 16 sv3000:~# ---------------------------------------------------------------------------= ----------------------------- sv3000:~# dmsetup targets -su: dmsetup: command not found sv3000:~# I cut the salt and digest. Best regards Rainer Jonas Meurer schrieb: > Hello Rainer, >=20 > On 12/08/2009 RaMaier@gmx.de wrote: >> Here my description what has happened. Hopefully it becomes clearer now. >> =20 >> What I wrote were the initial steps I perforemed when I first set up >> the partition (/dev/sda2). Again I did not repeat them now. >> After my old PC had died I installed the RAID controller in a new PC >> and installed Debian. (/dev/hda) cryptsetup is now already included. >> (Thanks for the hint Arno) >> Since it's a hardware controller the files on the not encrypted >> partition (/dev/sda1) were immediately available. >> Now I am looking for the steps I have to perform to access the data in >> the encrypted partition (/dev/sda2) again, without destroying them. >> >> When I now enter >> cryptsetup luksOpen /dev/sda2 tresor >> I get=20 >> Command failed: No steup backend available >=20 > please give some more information. i.e. paste the output of the > following commands (as root): >=20 > # dpkg -l cryptsetup >=20 > # cryptsetup --version >=20 > # cryptsetup luksDump /dev/sda2 >=20 > # cat /proc/crypto >=20 > none of the commands modifies your partition, they only print > information about versions, partition types, crypto ciphers, kernel > crypto support, etc. >=20 > greetings, > jonas >=20 >=20 > ------------------------------------------------------------------------ >=20 > _______________________________________________ > dm-crypt mailing list > dm-crypt@saout.de > http://www.saout.de/mailman/listinfo/dm-crypt