From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tK8D6rxZUQK4 for ; Tue, 18 Dec 2012 01:36:14 +0100 (CET) Received: from v4.tansi.org (ns.km33513-03.keymachine.de [87.118.94.3]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 18 Dec 2012 01:36:13 +0100 (CET) Received: from gatewagner.dyndns.org (84-74-164-49.dclient.hispeed.ch [84.74.164.49]) by v4.tansi.org (Postfix) with ESMTPA id 3AE2B1404001 for ; Tue, 18 Dec 2012 01:36:13 +0100 (CET) Date: Tue, 18 Dec 2012 01:36:12 +0100 From: Arno Wagner Message-ID: <20121218003612.GA14871@tansi.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dm-crypt] UUID question List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de 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 ) 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