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 eaORCvpq7Z2C for <dm-crypt@saout.de>;
 Fri, 14 Sep 2012 19:35:07 +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 19:35:06 +0200 (CEST)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <glkdd-dm-crypt@m.gmane.org>) id 1TCZnE-000215-70
 for dm-crypt@saout.de; Fri, 14 Sep 2012 19:35:04 +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 19:35:04 +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 19:35:04 +0200
From: Nick Battle <nick.battle@gmail.com>
Date: Fri, 14 Sep 2012 18:35:19 +0100
Message-ID: <k2vpn4$96e$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [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

I've just upgraded from openSUSE 12.1 to 12.2. I find that the latest version of
mount and losetup do not have the file encryption options they used to, since
everyone should have migrated to dm-crypt. The trouble is, I now have some
encrypted backup volumes that I cannot read!

I used to mount the archives with:

	mount ... -o loop,phash=sha256,encryption=aes128

It looks like I should be using the loopaesOpen option to cryptsetup to mount
these now, but I cannot find a combination of options that works. I'm trying the
following:

cryptsetup loopaesOpen <device> <name> --key-file pp --key-size 128 --hash
sha256 -c aes-cbc-plain

Where the file pp has my passphrase (without a newline) - that I used to enter
at the prompt mount gave when using the "-o loop". This successfully sets up the
mapper, but the result is not recognizable as a filesystem (I think it's ext2).
So I assume the crypto and/or passphrase hash isn't quite right.

I'm afraid the archives are so old that I don't know which options I used to
originally create them, though I almost certainly chose "defaults".

Can anyone help?

-- 
Cheers,
-nick