dm-crypt.saout.de archive mirror
 help / color / mirror / Atom feed
From: Nick Battle <nick.battle@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] Migrating from loop AES to dm-crypt
Date: Fri, 14 Sep 2012 18:35:19 +0100	[thread overview]
Message-ID: <k2vpn4$96e$1@ger.gmane.org> (raw)

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

             reply	other threads:[~2012-09-14 17:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 17:35 Nick Battle [this message]
2012-09-14 18:00 ` [dm-crypt] Migrating from loop AES to dm-crypt Arno Wagner
2012-09-14 20:08   ` Nick Battle
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='k2vpn4$96e$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).