unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 54770-done@debbugs.gnu.org
Subject: bug#54770: Non-root LUKS devices unusable after Shepherd upgrade
Date: Fri, 08 Apr 2022 18:18:07 +0200	[thread overview]
Message-ID: <87zgkvblc0.fsf@gnu.org> (raw)
In-Reply-To: <87r168etvd.fsf@inria.fr> ("Ludovic Courtès"'s message of "Thu, 07 Apr 2022 18:33:10 +0200")

Ludovic Courtès <ludo@gnu.org> skribis:

> Following the Shepherd upgrade in commit
> 400c9ed3d779308e56038305d40cd93acb496180, attempts to open non-root LUKS
> devices from a Shepherd service fail with this cryptsetup message:
>
>   Nothing to read on input.
>
> This is because standard input is now /dev/null so it cannot read the
> passphrase.

Fixed with these commits:

  f239b9d788 tests: Add "encrypted-home-os" installation test.
  dcb0e54a4f file-systems: Invoke fsck tools with 'system*/tty'.
  931f13840b mapped-devices: Ensure 'cryptsetup open' gets a tty.

Ludo’.




  parent reply	other threads:[~2022-04-08 16:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 16:33 bug#54770: Non-root LUKS devices unusable after Shepherd upgrade Ludovic Courtès
2022-04-08  9:32 ` Ludovic Courtès
2022-04-08 13:34   ` Ludovic Courtès
2022-04-08 16:18 ` Ludovic Courtès [this message]
2022-04-09 14:51 ` Christoph Weiss
2022-04-11 12:39   ` Ludovic Courtès
2022-04-11 17:07 ` bug#54770: (no subject) Christoph Weiss
2022-04-12  8:41   ` bug#54770: Non-root LUKS devices unusable after Shepherd upgrade Ludovic Courtès
2022-04-12 17:00     ` Christoph Weiss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgkvblc0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=54770-done@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).