From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane.org>
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 CZgyyGAtVtBB for <dm-crypt@saout.de>;
 Fri, 14 Sep 2012 22:06:11 +0200 (CEST)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Fri, 14 Sep 2012 22:06:11 +0200 (CEST)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <glkdd-dm-crypt@m.gmane.org>) id 1TCc9U-0005z2-Kd
 for dm-crypt@saout.de; Fri, 14 Sep 2012 22:06:12 +0200
Received: from cpc1-rdng16-0-0-cust630.15-3.cable.virginmedia.com
 ([86.9.210.119]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Fri, 14 Sep 2012 22:06:12 +0200
Received: from nick.battle by
 cpc1-rdng16-0-0-cust630.15-3.cable.virginmedia.com with local (Gmexim 0.1
 (Debian)) id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Fri, 14 Sep 2012 22:06:12 +0200
From: Nick Battle <nick.battle@gmail.com>
Date: Fri, 14 Sep 2012 21:08:50 +0100
Message-ID: <k302mv$js9$1@ger.gmane.org>
References: <k2vpn4$96e$1@ger.gmane.org> <20120914180032.GA13099@tansi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
In-Reply-To: <20120914180032.GA13099@tansi.org>
Subject: Re: [dm-crypt] Migrating from loop AES to dm-crypt
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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