From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] UUID question
Date: Tue, 18 Dec 2012 01:36:12 +0100 [thread overview]
Message-ID: <20121218003612.GA14871@tansi.org> (raw)
In-Reply-To: <CAADET=cgxphPsmRCR3SQTU_cXefhW1Zk86ut_vUpVoKW_3d-bw@mail.gmail.com>
On Mon, Dec 17, 2012 at 04:10:50PM -0800, David Li wrote:
> Hi, I wonder if the dm-crypt partition UUID (shown in blkid -p <dev>) can
> be used to uniquely associate it with the set of keys the partition will
> need. Are there any cases that the UUID would change during the partition's
> lifetime?
The UUID is actually a filesystem attribute, not a partition
attribute. That said, for purpose of an UUID, LUKS is regarded as a
filesystem, which is IMO the correct way to view it, but not a
perfect one. So, yes, the UUID will change if you do a luksFormat
(aptly named if LUKS is regarded as a filesystem), but it will not
change otherwise. As a luksFormat invalidates all keys, that should
do for your purpose.
Arno
--
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
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2012-12-18 0:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 0:10 [dm-crypt] UUID question David Li
2012-12-18 0:36 ` Arno Wagner [this message]
2012-12-18 8:12 ` Marc Ballarin
2012-12-18 8:57 ` Arno Wagner
2012-12-18 16:46 ` David Li
2012-12-19 23:30 ` Sven Eschenberg
2012-12-18 8:21 ` Milan Broz
2012-12-18 8:55 ` Arno Wagner
[not found] <mailman.1.1356001202.8121.dm-crypt@saout.de>
2012-12-20 11:16 ` Yaron Sheffer
2012-12-21 1:24 ` Sven Eschenberg
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=20121218003612.GA14871@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