Debian Bug report logs - #641662
cryptsetup: assumes root is crypt

version graph

Package: cryptsetup; Maintainer for cryptsetup is Debian Cryptsetup Team <pkg-cryptsetup-devel@lists.alioth.debian.org>; Source for cryptsetup is src:cryptsetup.

Reported by: Matt Taggart <taggart@debian.org>

Date: Thu, 15 Sep 2011 00:27:05 UTC

Severity: minor

Merged with 671056

Found in versions cryptsetup/2:1.1.3-4squeeze2, cryptsetup/2:1.4.1-3

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Cryptsetup Team <pkg-cryptsetup-devel@lists.alioth.debian.org>:
Bug#641662; Package cryptsetup. (Thu, 15 Sep 2011 00:27:08 GMT) Full text and rfc822 format available.

Acknowledgement sent to Matt Taggart <taggart@debian.org>:
New Bug report received and forwarded. Copy sent to Debian Cryptsetup Team <pkg-cryptsetup-devel@lists.alioth.debian.org>. (Thu, 15 Sep 2011 00:27:08 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Matt Taggart <taggart@debian.org>
To: submit@bugs.debian.org
Subject: cryptsetup: assumes root is crypt
Date: Wed, 14 Sep 2011 17:25:57 -0700
Package: cryptsetup
Version: 2:1.1.3-4squeeze2

I have several machines which I have upgraded from lenny to squeeze where I 
am seeing the following warnings

  cryptsetup: WARNING: failed to detect canonical device of /dev/md0
  cryptsetup: WARNING: could not determine root device from /etc/fstab

I am using cryptsetup on these machines, but the root is NOT using 
cryptsetup. Here are my fstab and crypttab

fstab:
/dev/md0        /               ext3    defaults,errors=remount-ro 0       1
/dev/mapper/swap1    none    swap    sw    0    0
/dev/mapper/swap2    none    swap    sw    0    0

crypttab:
swap1 /dev/cciss/c0d0p2 /dev/urandom cipher=serpent-xts-plain,size=256,swap
swap2 /dev/cciss/c0d1p2 /dev/urandom cipher=serpent-xts-plain,size=256,swap

It looks like the canonical_device function assumes that a device is using 
cryptsetup and tries a few ways to figure out the actual device and if it 
can't it gives up and gives these errors.

Maybe instead it could detect if a device is just a normal non-crypt disk 
and then not print anything? Or if you are worried about warning in cases 
of misconfiguration, you could print something like

  cryptsetup: WARNING: /dev/md0 does not appear to be a crypt device, 
skipping

Thanks,

-- 
Matt Taggart
taggart@debian.org






Severity set to 'minor' from 'normal' Request was from Jonas Meurer <jonas@freesources.org> to control@bugs.debian.org. (Thu, 01 Nov 2012 13:51:10 GMT) Full text and rfc822 format available.

Marked as found in versions cryptsetup/2:1.4.1-3. Request was from Jonas Meurer <jonas@freesources.org> to control@bugs.debian.org. (Thu, 01 Nov 2012 13:51:11 GMT) Full text and rfc822 format available.

Merged 641662 671056 Request was from Jonas Meurer <jonas@freesources.org> to control@bugs.debian.org. (Thu, 01 Nov 2012 13:51:11 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Fri Apr 25 08:54:25 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.