From: Milan Broz <gmazyland@gmail.com>
To: "Dragan Milivojević" <d.milivojevic@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Cryptsetup FAQ montly pointer 8/13
Date: Sat, 03 Aug 2013 16:47:12 +0200 [thread overview]
Message-ID: <51FD17F0.5090805@gmail.com> (raw)
In-Reply-To: <CALtW_aiGJQcDKUNh9Na2DsgdHfecFZs1F1g-8JmAv6-9LgO+7w@mail.gmail.com>
On 08/03/2013 04:10 PM, Dragan Milivojević wrote:
>> Another option for reliably identifying the swap partition is to use
>> /dev/disk/by-id/<identifier> to identify the drive by model and serial
>> number. For example, my own swap partition is
>>
>> /dev/disk/by-id/scsi-SATA_ST95005620AS_5YX1NEGE-part5
>>
>> That should be safe unless I re-purpose that drive and forget to update
>> /etc/crypttab.
>
> I would suggest using UUID. It works in all cases (partition, raid,
> lvm member etc).
> My crypttab (encrypted swap/home):
>
> luks-4dc17e23-e895-4e4b-8061-114fb33c310b
> UUID=4dc17e23-e895-4e4b-8061-114fb33c310b none
> luks-46969c48-ab1f-4bd7-bc2a-ae7c1bc86b26
> UUID=46969c48-ab1f-4bd7-bc2a-ae7c1bc86b26 none
>
> This was generated by fedora install.
Sure, this is the best way if you use LUKS and Fedora installer
is using LUKS even for swap.
For plain crypt (or Truecrypt) you have no UUID, so you cannot use it.
(You can use uuid/wwid of underlying device as mentioned above
but this is not be present always.)
Milan
next prev parent reply other threads:[~2013-08-03 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 14:10 [dm-crypt] Cryptsetup FAQ montly pointer 8/13 Dragan Milivojević
2013-08-03 14:47 ` Milan Broz [this message]
2013-08-03 17:57 ` Arno Wagner
2013-08-03 20:47 ` Milan Broz
2013-08-03 21:47 ` Arno Wagner
2013-08-03 22:51 ` Matthias Schniedermeyer
2013-08-03 17:47 ` Arno Wagner
2013-08-03 12:49 ` Alex Elsayed
-- strict thread matches above, loose matches on Subject: below --
2013-08-02 21:54 Arno Wagner
2013-08-03 13:51 ` Robert Nichols
2013-08-03 17:46 ` Arno Wagner
2013-08-04 15:02 ` 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=51FD17F0.5090805@gmail.com \
--to=gmazyland@gmail.com \
--cc=d.milivojevic@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox