all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Felix Lechner via Guix-patches via <guix-patches@gnu.org>
To: 63383@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#63383] Fwd: PAM may cause issues on system updates
Date: Wed, 28 Jun 2023 11:44:21 -0700	[thread overview]
Message-ID: <CAFHYt56SpBw71_kNVcx-Jrjvn9PES3yn+L6CLt3o-ywcEnVJTw@mail.gmail.com> (raw)
In-Reply-To: <CAFHYt567hXKWgA6hFKF6aFoXtdi2vtwoLYAmaf2jAqD1+OwBcg@mail.gmail.com>

[an earlier version was sent to the wrong bug]

Hi,

There is another bug that was probably a reason why some folks
hesitated to accept this patch:

  https://issues.guix.gnu.org/32182

In that bug, Ludo' proposed to refer from Shepherd services to PAM
services by absolute paths. I believe it is a viable and worthy
solution.

(By contrast, this bug makes PAM services refer to PAM modules by
absolute paths.)

Another solution could be to make all PAM modules and services Guile
scripts. While admittedly a more comprehensive effort, I believe such
an upgrade might be popular in the broader community, which is
generally tired of PAM. The only prerequisite to execute those scripts
would be a working copy of GNU Guile (i.e. no libpam or libc).

Kind regards
Felix




       reply	other threads:[~2023-06-28 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFHYt567hXKWgA6hFKF6aFoXtdi2vtwoLYAmaf2jAqD1+OwBcg@mail.gmail.com>
2023-06-28 18:44 ` Felix Lechner via Guix-patches via [this message]
2023-08-15 20:19   ` bug#63383: [PATCH 0/4] Various PAM improvements Ludovic Courtès
2023-08-16 18:21     ` [bug#63383] " Felix Lechner via Guix-patches via

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

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

  git send-email \
    --in-reply-to=CAFHYt56SpBw71_kNVcx-Jrjvn9PES3yn+L6CLt3o-ywcEnVJTw@mail.gmail.com \
    --to=guix-patches@gnu.org \
    --cc=63383@debbugs.gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.