Package: cryptsetup Version: 20050111-3 Severity: minor Tags: patch Hi,
I added a note that /dev/random can block upon boot. Attached is a patch. Regards, Bastian -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-treasure3 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages cryptsetup depends on: ii dmsetup 2:1.01.00-4 The Linux Kernel Device Mapper use ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libdevmapper1.01 2:1.01.00-4 The Linux Kernel Device Mapper use ii libgcrypt11 1.2.0-11.1 LGPL Crypto library - runtime libr ii libgpg-error0 1.0-1 library for common error values an ii libpopt0 1.7-5 lib for parsing cmdline parameters -- no debconf information
--- /usr/share/doc/cryptsetup/CryptoSwap.HowTo 2005-03-08 17:10:24.000000000 +0100 +++ CryptoSwap.HowTo 2005-04-18 13:47:44.000000000 +0200 @@ -18,7 +18,11 @@ # <target device> <source device> <key file> <options> cswap /dev/hda9 /dev/random swap -Reboot, and that's it! You have a crypted swap device. +Reboot, and that's it! You have a crypted swap device. Note that the +/dev/random device might not generate enough random bytes, so the boot +process can wait indefinitely unless you press some keys on your +keyboard. To be sure that booting is not interrupted, use /dev/urandom +instead as device. Read the crypttab(5) manpage for more information, for example options to use a different encryption algorithm than the default.
