Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #66090

Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl

Path csiph.com!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder7.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From Luc Maisonobe <luc@spaceroots.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl
Date Wed, 15 Jan 2020 09:40:03 +0100
Message-ID <zoMnw-fl-15@gated-at.bofh.it> (permalink)
References <zoCHv-2Pr-3@gated-at.bofh.it> <zoCHv-2Pr-3@gated-at.bofh.it>
X-Mailbox-Line From debian-bugs-dist-request@lists.debian.org Wed Jan 15 08:30:11 2020
Old-Return-Path <debbugs@buxtehude.debian.org>
X-Spam-Flag NO
X-Spam-Score 0.45
Reply-To Luc Maisonobe <luc@spaceroots.org>, 948921@bugs.debian.org
Resent-To debian-bugs-dist@lists.debian.org
Resent-Cc Debian Kernel Team <debian-kernel@lists.debian.org>
X-Debian-Pr-Message followup 948921
X-Debian-Pr-Package src:linux
X-Debian-Pr-Source linux
X-Spam-Bayes score:0.0000 Tokens: new, 47; hammy, 150; neutral, 64; spammy, 0. spammytokens: hammytokens:0.000-+--H*u:60.0, 0.000-+--H*u:60.9.0, 0.000-+--H*UA:60.9.0, 0.000-+--H*u:x86_64, 0.000-+--5.4.0
Dkim-Signature v=1; a=rsa-sha256; c=simple/simple; d=spaceroots.org; s=mail; t=1579076548; bh=50vS6iYNMZ9seFgoVytlbXuXe13+qFEoZQKogmPTGn0=; h=Subject:References:From:To:Date:In-Reply-To:From; b=FG8aDbrje/H68ZNPpfiygKTEZpnRpCJeV+J+PnlDtDmEAnWgnKaRoE2DmNgZeRy7Z FWsXYdYAi4d3ZUSpgm6BH2+cfL1ZafJeh+643vCP+7tXxjkfwnk7TPBTRpPGK48ACn igyDH3MshMY2JrVbJnqk/KCOdo7H6o12SBIY4g+I=
User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version 1.0
Content-Type text/plain; charset=utf-8
Content-Language fr
Content-Transfer-Encoding 7bit
X-Greylist delayed 339 seconds by postgrey-1.36 at buxtehude; Wed, 15 Jan 2020 08:28:12 UTC
X-Debian-Message from BTS
X-Mailing-List <debian-bugs-dist@lists.debian.org> archive/latest/1579297
List-ID <debian-bugs-dist.lists.debian.org>
List-URL <https://lists.debian.org/debian-bugs-dist/>
Approved robomod@news.nic.it
Lines 49
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Wed, 15 Jan 2020 09:22:05 +0100
X-Original-Message-ID <af5ab640-9800-e5cf-ae0f-fe3069145762@spaceroots.org>
X-Original-References <157903105094.2380.3930152496779778070.reportbug@marislae.si.c-s.fr> <157903105094.2380.3930152496779778070.reportbug@marislae.si.c-s.fr>
Xref csiph.com linux.debian.bugs.dist:991416 linux.debian.kernel:66090

Cross-posted to 2 groups.

Show key headers only | View raw


Here are some additional informations about the problem.

I rechecked it was not a keyboard layout problem by setting up
an additional luks key, a very short one that used only keys that
were at the same position in both qwerty and azerty. It does
not work, so it's definitely not a keyboard problem.

The error I get on boot is as follows:

  Caching passphrase for sdb1_crypt:***********************
  [  15.212421] device-mapper: table: 253:0: crypt: Error allocating
crypto tfm
  device-mapper: reload ioctl on   failed: No such file or directory
  cryptsetup: ERROR: sdb1_crypt: cryptsetup failed, bad password or options?

  Caching passphrase for sdb1_crypt:

I tried to use a key file instead of a key typed by user just
like I did on the other laptop. I do not want to use this method
for  this specific machine for security reasons (it should not be
abel to boot unattended), but tried it temporarily. I regenerated
the initramfs after changing the /etc/crypttab file, but it didn't
work either. When generating initramfs, I got the following warning,
so it may explain why it didn't work.

  cryptsetup: WARNING: Skipping root target sdb1_crypt: uses a key file

In this case (booting with a key file), the error was different:

  Volume group "vg-ssd" not found
  Cannot process volume group vg-ssd
  Volume group "vg-hdd" not found
  Cannot process volume group vg-hdd
  Volume group "vg-hdd" not found
  Cannot process volume group vg-hdd
  Volume group "vg-hdd" not found
  ...
  Cannot process volume group vg-hdd
  Volume group "vg-hdd" not found
  Cannot process volume group vg-hdd
  mdadm: error opening /dev/md?*: No such file or directory
  Cannot process volume group vg-hdd
  Volume group "vg-hdd" not found

then the boot process drops to initramfs shell. Exploring the filesystem
at this stage, I didn't find the key file.

best regards,
Luc

Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0)  with decrypt_keyctl Luc Maisonobe <luc@apache.org> - 2020-01-14 23:20 +0100
  Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl Luc Maisonobe <luc@spaceroots.org> - 2020-01-15 09:40 +0100
    Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl Salvatore Bonaccorso <carnil@debian.org> - 2020-01-15 21:30 +0100
      Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition  does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl luc <luc@spaceroots.org> - 2020-01-16 09:30 +0100

csiph-web