From: Nick Battle <nick.battle@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Migrating from loop AES to dm-crypt
Date: Wed, 19 Sep 2012 19:07:47 +0100 [thread overview]
Message-ID: <k3d1fr$61e$1@ger.gmane.org> (raw)
In-Reply-To: <20120918213214.GA14243@tansi.org>
On 18/09/12 22:32, Arno Wagner wrote:
>> I just tried this again and it now works fine. I thought I tried
>> several plain "create" options, but... evidently not!
>
> Data recovery has a tendency to devolve into chaos, if you
> only do it rarely ;-)
LOL, yes! I think I tried the basic "create" options after I'd read a page
somewhere about the full syntax for the cipher and hash arguments, so I was
probably trying all manner of fancy IV schemes and chaining modes. If only I'd
tried the basic stuff!
Anyway, sorted now. I've posted the answer in the other forums where I asked the
same question (LinuxQuestions and the SUSE forums), so hopefully along with your
FAQ update we'll help a few people who have the same problem :)
Thanks again.
--
Cheers,
-nick
prev parent reply other threads:[~2012-09-19 18:05 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
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 [this message]
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='k3d1fr$61e$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).