Attachment 144367 Details for Bug 220769 – patch for crypttab man page (in /usr/share/man/man5/crypttab.5.gz)

[patch] patch for crypttab man page (in /usr/share/man/man5/crypttab.5.gz)

crypttab.5.patch (text/plain), 3.36 KB, created by Mike Breen on 2006-12-26 12:02:55 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Mike Breen

Created: 2006-12-26 12:02:55 UTC

Size: 3.36 KB

patch

obsolete

>--- crypttab.5	2006/12/23 14:07:28	1.1
>+++ crypttab.5	2006/12/23 17:19:01
>@@ -16,14 +16,15 @@
> .\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
> .\"
> .\" Author: Miloslav Trmac <mitr@redhat.com>
>-.TH crypttab 5 "Jul 2006"
>+.\" Minor updates: Michael Breen
>+.TH crypttab 5 "Dec 2006"
> 
> .SH NAME
> /etc/crypttab - encrypted block device table
> 
> .SH DESCRIPTION
> The
>-.B /etc/crypptab
>+.B /etc/crypttab
> file describes encrypted block devices that are set up during system boot.
> 
> Empty lines and lines starting with the
>@@ -59,7 +60,8 @@
> to generate a truly random encryption key.
> 
> The fourth field, if present, is a comma-delimited list of options.
>-The following options are recognized:
>+There are no options for LUKS encrypted partitions.
>+For non-LUKs partitions the following options are recognized:
> .TP
> \fBcipher=\fIcipher\fR
> Specifies the cipher to use; see
>@@ -87,20 +89,34 @@
> 
> .TP
> \fBswap\fR
>-The encrypted block device will be used as a swap partition,
>-and will be formatted as a swap partition
>-after setting up the encrypted block device.
>-The underlying block device
>-will be formatted again as an unencrypted swap partition
>-after destroying the encrypted block device.
>-(This allows sharing a single swap partition between operating
>-system installations,
>-with some of them encrypting the swap partitions and some of them not.)
>-
>-\fIWARNING\fR: Using the
>-.B swap
>-option will destroy the contents of the named partition during every boot, so
>-make sure the underlying block device is specified correctly.
>+The encrypted block device will be used as a swap partition.
>+For this to work,
>+.BR mkswap (8)
>+must first be run on the underlying unencrypted device:
>+on each boot, if the unencrypted device does not look like
>+swap then it will not be used for encrypted swap either;
>+this is to reduce the danger of accidentally destroying data
>+on the wrong partition (for example, if
>+.B /etc/crypttab
>+is not updated after a change to the partition table).
>+If the underlying device is recognised as swap at boot-up then
>+the encrypted device will be created and formatted as swap.
>+When the encrypted device is destroyed at system shutdown
>+the underlying unencrypted device will again be formatted as
>+swap.
>+(This also means the same device will be available as unencrypted
>+swap for any other operating system booted on the same machine.)
>+
>+\fINOTE\fR: If the system does not shut down cleanly then
>+the swap device may not be recognised as such at boot-up.
>+In this case, it will be necessary to run
>+.B mkswap
>+on the underlying block device again and then either reboot
>+or manually run
>+.BR cryptsetup (8)
>+(and
>+.BR swapon (8)
>+to enable swapping).
> 
> .TP
> \fBtmp\fR
>@@ -108,16 +124,19 @@
> it will be formatted using
> .B mke2fs
> and its root directory will be set to mode 01777.
>-The warning about the
>-.B swap
>-option applies here as well.
> 
>-.PP
>-No options can be specified for LUKS encrypted partitions.
>+\fIWARNING\fR: Using the
>+.B tmp
>+option will destroy the contents of the named partition during every boot, so
>+make sure the underlying block device is specified correctly.
>+Also make sure to update 
>+.B /etc/crypttab
>+before rebooting if the underlying device number ever changes
>+(as a result of editing the partition table).
> 
> .SH COMPATIBILITY
> The
>-.B /etc/crypptab
>+.B /etc/crypttab
> file format is based on the Debian cryptsetup package,
> and is intended to be compatible.
>

Actions: View | Diff

Attachments on bug 220769: 144367