unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 52533@debbugs.gnu.org
Subject: bug#52533: [PATCH] bug#52533: guix deploy breaks SSH access with a PAM error
Date: Thu, 16 Dec 2021 00:27:50 -0500	[thread overview]
Message-ID: <878rwl86g9.fsf@gmail.com> (raw)
In-Reply-To: <87czlx88ez.fsf@gmail.com> (Maxim Cournoyer's message of "Wed, 15 Dec 2021 23:45:24 -0500")

Hello,

I've found a workaround: disabling PAM for the remote machine
ssh-daemon.  This is not done as part of 'guix deploy', so needs to be
fiddled with manually; I did it this way:

1. take note of the command line and sshd_config file:

--8<---------------cut here---------------start------------->8---
ps -eFww | grep sshd
--8<---------------cut here---------------end--------------->8---

2. Copy the sshd_config file from /gnu/store to somewhere writable and
edit it so tha UsePAM is "no" instead of "yes".

3. Stop the Shepherd service with 'sudo herd stop ssh-daemon'

4. Start the ssh daemon manually (with sudo) by using the command found
in 1. but with the edited config from 2.

Then you should be able to 'guix deploy' successfully.

Reading 'man sshd_config', it says the default for UsePAM is no.
Considering this, and the issue it caused reported here, perhaps we
should disable it by default in Guix?

What do others think?

Thank you,

Maxim




  reply	other threads:[~2021-12-16  5:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16  4:45 bug#52533: guix deploy breaks SSH access with a PAM error Maxim Cournoyer
2021-12-16  5:27 ` Maxim Cournoyer [this message]
2021-12-16 15:02 ` Ludovic Courtès
2022-01-13 12:31   ` Mathieu Othacehe
2022-01-13 12:38     ` Mathieu Othacehe
2022-01-13 15:04     ` Ludovic Courtès
2022-01-13 16:45       ` Maxim Cournoyer
2022-01-17 13:25         ` Ludovic Courtès
2022-01-17 15:19           ` Maxim Cournoyer
2022-01-17 16:13             ` Ludovic Courtès
2022-01-18  4:33               ` Maxim Cournoyer
2022-01-18 11:27                 ` Ludovic Courtès

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=878rwl86g9.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=52533@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).