Your message dated Mon, 14 Nov 2005 15:32:05 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#310295: fixed in cryptsetup 20050111-4
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 22 May 2005 22:04:19 +0000
>From [EMAIL PROTECTED] Sun May 22 15:04:18 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mx01.qsc.de [213.148.129.14] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DZyYU-00083u-00; Sun, 22 May 2005 15:04:18 -0700
Received: from port-212-202-192-37.dynamic.qsc.de ([212.202.192.37] 
helo=treasure.calvinsplayground.de)
        by mx01.qsc.de with smtp (Exim 3.35 #1)
        id 1DZyXz-00068X-00
        for [EMAIL PROTECTED]; Mon, 23 May 2005 00:03:47 +0200
Received: (qmail 18778 invoked by uid 1000); 22 May 2005 22:04:43 -0000
Message-ID: <[EMAIL PROTECTED]>
Content-Type: multipart/mixed; boundary="===============0316847565=="
MIME-Version: 1.0
From: Bastian Kleineidam <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: cryptsetup: add note about blocking /dev/random in swap howto
X-Mailer: reportbug 3.12
Date: Mon, 23 May 2005 00:04:43 +0200
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

This is a multi-part MIME message sent by reportbug.

--===============0316847565==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0316847565==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="crypt_swap_random.diff"

--- /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.

--===============0316847565==--

---------------------------------------
Received: (at 310295-close) by bugs.debian.org; 14 Nov 2005 23:42:46 +0000
>From [EMAIL PROTECTED] Mon Nov 14 15:42:46 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
        id 1Ebnnx-0002fE-48; Mon, 14 Nov 2005 15:32:05 -0800
From: Jonas Meurer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#310295: fixed in cryptsetup 20050111-4
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 14 Nov 2005 15:32:05 -0800
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 7

Source: cryptsetup
Source-Version: 20050111-4

We believe that the bug you reported is fixed in the latest version of
cryptsetup, which is due to be installed in the Debian FTP archive:

cryptsetup_20050111-4.diff.gz
  to pool/main/c/cryptsetup/cryptsetup_20050111-4.diff.gz
cryptsetup_20050111-4.dsc
  to pool/main/c/cryptsetup/cryptsetup_20050111-4.dsc
cryptsetup_20050111-4_i386.deb
  to pool/main/c/cryptsetup/cryptsetup_20050111-4_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Meurer <[EMAIL PROTECTED]> (supplier of updated cryptsetup package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 14 Nov 2005 23:24:43 +0100
Source: cryptsetup
Binary: cryptsetup
Architecture: source i386
Version: 20050111-4
Distribution: unstable
Urgency: low
Maintainer: Debian Cryptsetup Team <[EMAIL PROTECTED]>
Changed-By: Jonas Meurer <[EMAIL PROTECTED]>
Description: 
 cryptsetup - configures encrypted block devices
Closes: 298944 303484 306021 310295 330370 334485 334490 335359 335604
Changes: 
 cryptsetup (20050111-4) unstable; urgency=low
 .
   * Change Maintainer field to the Debian Cryptsetup Team, add wesley and
     myself to Uploaders
   * Bump standards-version to 3.6.2.1, no changes needed
   * Document that -d option disables hashing (closes: #335604, #298944)
     Thanks to Bastian Kleineidam <[EMAIL PROTECTED]> for the patch
   * Document -r and --readonly options in the manpage (closes: #306021)
   * Split documentation of --help and --usage in manpage
   * Remove /etc/keys and /etc/crypttab on purge (closes: #330370)
   * Update README.html (closes: #334485)
   * Document how to prevent a watermark attack weakness in CryptoRoot.HowTo
     (closes: #334490)
   * Document shortness of /dev/random in CryptoSwap.HowTo (closes: #310295)
   * Fix the first line of usbcrypto.initrd, fixes half of #324353
   * Set permissions for /tmp in cryptdisks script (closes: #303484)
     Thanks to Stefan Reuter <[EMAIL PROTECTED]> for the patch
   * Added LSB initscript headers to cryptdisks script (closes: #335359)
   * renamed cryptsetup.{preinst,postinst,postrm} to preinst, postinst and
     postrm
   * Fix use of update-rc.d in postinst, cryptdisks should be stopped at
     runlevel 0 and 6, and be started at runlevel S. Instead it has been
     started in all tree runlevels up to now.
Files: 
 a39fe7c2609060864ea40b70d624b461 838 admin optional cryptsetup_20050111-4.dsc
 b2f2b2cd6646936297328db2f8ccd255 23269 admin optional 
cryptsetup_20050111-4.diff.gz
 ade422c32985301050f5cfece49ee791 196972 admin optional 
cryptsetup_20050111-4_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDeRn4d6lUs+JfIQIRAnHXAJ9XcytK7UrbwYDTU+us6DSATjY6wgCcCtI2
cf7gO0lzbtKMfAXekmUeWAo=
=FcJr
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to