From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane.org>
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 AyHdISg8Gn7g for <dm-crypt@saout.de>;
 Sat,  3 Aug 2013 15:51:23 +0200 (CEST)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sat,  3 Aug 2013 15:51:23 +0200 (CEST)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <glkdd-dm-crypt@m.gmane.org>) id 1V5cEq-0008Bl-Fz
 for dm-crypt@saout.de; Sat, 03 Aug 2013 15:51:20 +0200
Received: from c-98-227-220-190.hsd1.il.comcast.net ([98.227.220.190])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Sat, 03 Aug 2013 15:51:20 +0200
Received: from rnicholsNOSPAM by c-98-227-220-190.hsd1.il.comcast.net with
 local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Sat, 03 Aug 2013 15:51:20 +0200
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
Date: Sat, 03 Aug 2013 08:51:09 -0500
Message-ID: <ktj1s7$5p1$1@ger.gmane.org>
References: <20130802215419.GA30294@tansi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <20130802215419.GA30294@tansi.org>
Subject: Re: [dm-crypt] Cryptsetup FAQ montly pointer 8/13
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 08/02/2013 04:54 PM, Arno Wagner wrote:
> The FAQ can be fount on the Web here:
>    http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions
> and in the sources.
>
> Changes:
> - Added section on swap encryption as item 2.2

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.

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.