All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup from aes-cbc to aes-xts
Date: Fri, 30 Oct 2015 00:32:43 +0100	[thread overview]
Message-ID: <20151029233243.GA17172@tansi.org> (raw)
In-Reply-To: <56329DAA.7020403@fosiao.com>

You do not need to format the disk, you just need to luksFormat
the LUKS container (i.e. full disk, partition or loop-file). 
Your LUKS container here is /dev/sda1 and you are 
luks(re)Formatting it with the lines you give.

Regards,
Arno

On Thu, Oct 29, 2015 at 23:28:58 CET, xxiao8 wrote:
> I had a one liner change in my cryptsetup script (see below), as
> long as the key-file is the same, I can keep using the content on
> the hard-drive, which is a surprise to me. Doesn't
> switch-to-aes-xts-plain64 mandate a reformat of the hard drive? am I
> missing something?
> 
> 
> Changing from
> cryptsetup -v -c "aes-cbc-essiv:sha256" --key-size 256 --key-file
> /etc/keys/sda1.key luksFormat --use-random /dev/sda1
> 
> to
> cryptsetup -v -c "aes-xts-plain64" --hash sha256 --key-size 512
> --key-file /etc/keys/sda1.key luksFormat --use-random /dev/sda1
> 
> Thanks for your help,
> 
> xxiao
> 
> _______________________________________________
> 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
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  reply	other threads:[~2015-10-29 23:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 22:28 [dm-crypt] cryptsetup from aes-cbc to aes-xts xxiao8
2015-10-29 23:32 ` Arno Wagner [this message]
2015-10-30 21:31 ` Michael Kjörling

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=20151029233243.GA17172@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.