From: Milan Broz <gmazyland@gmail.com>
To: Robert Nichols <rnicholsNOSPAM@comcast.net>, dm-crypt@saout.de
Subject: Re: [dm-crypt] Documentation inconsistency -- On-Disk Format
Date: Fri, 21 Nov 2014 08:32:11 +0100 [thread overview]
Message-ID: <546EEA7B.5010109@gmail.com> (raw)
In-Reply-To: <m4m9bl$fc9$1@ger.gmane.org>
On 11/21/2014 03:51 AM, Robert Nichols wrote:
> I just noticed that in the LUKS On-Disk Format Specification document 1.2.1
> http://wiki.cryptsetup.googlecode.com/git/LUKS-standard/on-disk-format.pdf
> the LUKS key slots are numbered 1-8, whereas all the tools number them 0-7.
It is just for "historic" reasons. I can fix it in documentation but old
documentation is still in place (it is installed e.g. as docs in various distros).
It could make the problem even worse.
(And changing tools means breaking user scripts which is even worse.)
It is not the first standard which uses pseudo-code description while real
implementation differs in details.
> That makes communication difficult.
I do not think so. When dealing with users problem always the tool output
is important. The slot offsets depends on key size so you must have always
proper luksDump output for the device.
Milan
next prev parent reply other threads:[~2014-11-21 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 2:51 [dm-crypt] Documentation inconsistency -- On-Disk Format Robert Nichols
2014-11-21 7:32 ` Milan Broz [this message]
2014-11-21 10:00 ` Arno Wagner
2014-11-21 9:56 ` Arno Wagner
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=546EEA7B.5010109@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=rnicholsNOSPAM@comcast.net \
/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.