From: RaMaier@gmx.de
To: Moji <lordmoji@gmail.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] reinstallation
Date: Wed, 12 Aug 2009 00:40:09 +0200 [thread overview]
Message-ID: <20090811224009.300710@gmx.net> (raw)
In-Reply-To: <4A81EB67.30002@gmail.com>
Sorry for the unclear statements.
Here are the answers:
I did not repeat the steps.
/dev/sda2 holds the encrypted data.
Here my description what has happened. Hopefully it becomes clearer now.
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
Command failed: No steup backend available
Best regards
Rainer
-------- Original-Nachricht --------
> Datum: Wed, 12 Aug 2009 01:06:31 +0300
> Von: Moji <lordmoji@gmail.com>
> An: dm-crypt@saout.de
> Betreff: Re: [dm-crypt] reinstallation
> 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 <h.e@gmx.at>
> >> An: Rainer Maier <RaMaier@gmx.de>
> >> 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
> >
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
next prev parent reply other threads:[~2009-08-11 22:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 13:40 [dm-crypt] reinstallation Rainer Maier
2009-08-11 14:01 ` Hannes Erven
2009-08-11 21:25 ` RaMaier
2009-08-11 22:06 ` Moji
2009-08-11 22:40 ` RaMaier [this message]
2009-08-11 23:34 ` Jonas Meurer
2009-08-11 23:36 ` Jonas Meurer
2009-08-12 6:19 ` Rainer Maier
2009-08-12 9:39 ` Jonas Meurer
[not found] ` <20090811214229.GA4796@tansi.org>
2009-08-11 22:25 ` RaMaier
[not found] ` <200908111839.19827.samm@sammaloney.com>
2009-08-11 22:54 ` RaMaier
2009-08-11 23:01 ` Sam
2009-08-12 6:09 ` Rainer Maier
2009-08-12 6:51 ` Milan Broz
2009-08-12 12:25 ` Rainer Maier
-- strict thread matches above, loose matches on Subject: below --
2009-08-11 22:40 Sam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090811224009.300710@gmx.net \
--to=ramaier@gmx.de \
--cc=dm-crypt@saout.de \
--cc=lordmoji@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox