From: Nick Battle <nick.battle@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Migrating from loop AES to dm-crypt
Date: Fri, 14 Sep 2012 21:08:50 +0100 [thread overview]
Message-ID: <k302mv$js9$1@ger.gmane.org> (raw)
In-Reply-To: <20120914180032.GA13099@tansi.org>
On 14/09/12 19:00, Arno Wagner wrote:
> I also have no idea what you need, but loop AES has no metadata,
> i.e. the correct options need to be given every time. That
> means your openSUSE 12.1 gave them, either because it was the
> defaults used there, or because they were encoded somewhwere
> (crypttab?)
All I think I have to go on is the openSUSE mount(1) options that worked (-o
loop,phash=sha256,encryption=aes128).
> In the first case an OpenSUSE 12.1 life CD should help.
> In the second case you need to find the parameters, for
> example in a backup of the old system.
I should presumably be able to mount using an old live CD, but if that's using
losetup (albeit via mount), I'm not sure how to find the actual parameters.
> If you get the container mapped with the old openSUSE,
> dmsetup table --target crypt --showkey /dev/mapper/<device>
> should give cipher, mode and offsets.
Will that work even for a "plain" losetup with a cipher. That looks like a
dm-crypt tool?
> If you figure it out, can you tell me which parameters worked
> for cryptsetup, so I can add them in Secrion 7 of the FAQ? Thanks!
Yes, absolutely!
--
Cheers,
-nick
next prev parent reply other threads:[~2012-09-14 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 17:35 [dm-crypt] Migrating from loop AES to dm-crypt Nick Battle
2012-09-14 18:00 ` Arno Wagner
2012-09-14 20:08 ` Nick Battle [this message]
2012-09-15 12:04 ` Matthias Schniedermeyer
2012-09-18 7:16 ` Ludwig Nussel
2012-09-18 7:47 ` Milan Broz
2012-09-18 21:03 ` Nick Battle
2012-09-18 21:32 ` Arno Wagner
2012-09-19 18:07 ` Nick Battle
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='k302mv$js9$1@ger.gmane.org' \
--to=nick.battle@gmail.com \
--cc=dm-crypt@saout.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.