From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Non-standard cipher mode
Date: Wed, 18 Dec 2013 17:13:28 +0100 [thread overview]
Message-ID: <20131218161328.GA12245@tansi.org> (raw)
In-Reply-To: <20131218114539.GA4763@r00t3d.com>
DO NOT EDIT THE HEADER. This will make your LUKS container
inaccessible until you reverse the changes. What you now
have is an aes-xts-plain64:sha512 container. You do not have
ESSIV anywhere in there, XTS is an alternative to CBC-ESSIV.
That said, if you want aother cipher or mode, easiest way is
to re-create the container. A bit harder and risky without
backup is to use Milan's reencryption tool.
Arno
On Wed, Dec 18, 2013 at 12:45:39 CET, FLD wrote:
> I accidentally created a luks container using option --cipher
> aes-xts-plain64:sha512. Everything seems to be working correctly and
> luksDump shows: "Cipher mode: xts-plain64:sha512". I wonder if I
> should hexedit the header manually and replace the ":sha512" part with
> nulls since the proper format would be just "xts-plain64" since the
> cipher does not need a hash for the ESSIV?
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
next prev parent reply other threads:[~2013-12-18 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 11:45 [dm-crypt] Non-standard cipher mode FLD
2013-12-18 16:13 ` Arno Wagner [this message]
2013-12-18 17:15 ` Milan Broz
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=20131218161328.GA12245@tansi.org \
--to=arno@wagner.name \
--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