All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Some questions/clarifications around the LUKS spec
Date: Mon, 14 Mar 2016 20:54:23 +0100	[thread overview]
Message-ID: <56E716EF.2080709@gmail.com> (raw)
In-Reply-To: <56E709E2.4010004@whgl.uni-frankfurt.de>

On 03/14/2016 07:58 PM, Sven Eschenberg wrote:

...
> On a sidenote: When cryptsetup switched it's defaults to aes-xts it 
> stopped being compliant to the (original) LUKS specs. No doubt.
...
> Again cryptsetup gave up on the specs, as there was a severe need for 
> these changes. It really had been wise to ditch the original on disk 
> format at that time and create a new revised (sub)version of the on disk 
> format. It did not happen though and currently the reference 
> implementation is the 'de facto' specification, while the original spec 
> is only the 'de jure' specification. But then again, 'industry' and 
> 'practice' define standards, don't they? *SCNR*

Sorry? Spec is updated, it mentions XTS mode, and disk format remains still the same,
despite I did last update in 2011. (Simply because there was no need to update
it.) I'll mention more in another reply.

Cryptsetup never gave up specs, it is still compatible to the document.

Milan

  reply	other threads:[~2016-03-14 19:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 15:21 [dm-crypt] Some questions/clarifications around the LUKS spec Daniel P. Berrange
2016-03-14 18:58 ` Sven Eschenberg
2016-03-14 19:54   ` Milan Broz [this message]
2016-03-14 21:24     ` Sven Eschenberg
2016-03-14 22:27       ` Milan Broz
2016-03-15 14:21         ` Sven Eschenberg
2016-04-27 12:56         ` [dm-crypt] Cryptesetup and dm-crypt levent demir
2016-04-27 16:35           ` Arno Wagner
2016-03-14 20:31 ` [dm-crypt] Some questions/clarifications around the LUKS spec Milan Broz
2016-03-15 10:23   ` Daniel P. Berrange

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=56E716EF.2080709@gmail.com \
    --to=gmazyland@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 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.