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 C2F659672 for ; Wed, 12 Aug 2009 00:06:48 +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 u-gppMM2OnAJ for ; Wed, 12 Aug 2009 00:06:43 +0200 (CEST) Received: from mail-ew0-f214.google.com (mail-ew0-f214.google.com [209.85.219.214]) by mail.saout.de (Postfix) with ESMTP for ; Wed, 12 Aug 2009 00:06:43 +0200 (CEST) Received: by ewy10 with SMTP id 10so7319896ewy.13 for ; Tue, 11 Aug 2009 15:06:42 -0700 (PDT) Message-ID: <4A81EB67.30002@gmail.com> Date: Wed, 12 Aug 2009 01:06:31 +0300 From: Moji MIME-Version: 1.0 References: <4A8174D3.7000909@gmx.de> <4A8179D4.40807@gmx.at> <20090811212516.39750@gmx.net> In-Reply-To: <20090811212516.39750@gmx.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] reinstallation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de I do not entirely understand your question, so I apologize if my answer is not what you are looking for. If you repeated those steps then any information on /dev/sda2 will be lost forever. "luksFormat" writes the luks header information, that includes the key that decrypts the rest of the partition(device). If there is an old key it will write over it making any old data on that luks partition effectively unrecoverable. "luksOpen" uses your supplied key to decrypt the device key stored in the header information and then maps it to /dev/mapper/. If I understand your original post, the "/dev/sda2" is currently unencrypted data? If that is the case then you MUST copy that data over to another device while you set up then encrypted partition, then transfer it back, as the steps you listed will erase your old partition. -MJ RaMaier@gmx.de wrote: > Hi Hannes, > in the documents I keep. I found that I had encrypted /dev/sda2. The procedure I recorded was: > umount /dev/sda2 > cryptsetup luksFormat /dev/sda2 > cryptsetup luksOpen /dev/sda2 tresor > mkfs.ext3 /dev/mapper/tresor > mount /dev/mapper/tresor /tresor > > What will happen if I repeat the steps ? > Should I just leave the mkfs.ext3 out ? > Would I be able to access my old data again ? > What does lufsFormat really do ? Format the partition ? > As I staded the data is pretty valuable to me. > > thanks for your help. > Best regards > Rainer > > > -------- Original-Nachricht -------- >> Datum: Tue, 11 Aug 2009 16:01:56 +0200 >> Von: Hannes Erven >> An: Rainer Maier >> CC: dm-crypt@saout.de >> Betreff: Re: [dm-crypt] reinstallation > >> Hi Rainer, >> >> >>> How can I reinstall LUKS on my new Debian (Lenny)? >> I guess the debian (and thus cryptsetup) installations on your old >> machine weren't that up to date, right? >> >> With the new debian lenny, you don't need to install anything: LUKS is >> already included in the default cryptsetup package you should already >> have installed (http://packages.debian.org/lenny/cryptsetup ). >> >>> >From http://code.google.com/p/cryptsetup/: >> "The former version of cryptsetup only had low-level operations for >> dm-crypt ready, and around version cryptsetup-luks 1.0.5 was renamed to >> be the official version of cryptsetup. " >> >> You still might have to change your old scripts, if you have some, to >> just call cryptsetup instead of cryptsetup-luks . >> >> >> HTH, best regards >> >> -hannes >> >> >> >> _______________________________________________ >> dm-crypt mailing list >> dm-crypt@saout.de >> http://www.saout.de/mailman/listinfo/dm-crypt >