From: "Ludovic Courtès" <ludo@gnu.org>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: 63383-done@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#63383: [PATCH 0/4] Various PAM improvements
Date: Tue, 15 Aug 2023 22:19:34 +0200 [thread overview]
Message-ID: <87cyzo83e1.fsf_-_@gnu.org> (raw)
In-Reply-To: <CAFHYt56SpBw71_kNVcx-Jrjvn9PES3yn+L6CLt3o-ywcEnVJTw@mail.gmail.com> (Felix Lechner's message of "Wed, 28 Jun 2023 11:44:21 -0700")
Hi,
Sorry for the long delay!
Felix Lechner <felix.lechner@lease-up.com> skribis:
> 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.)
Right. For this reason, I’m dropping the patch that adds more absolute
file names for all modules shipped with ‘linux-pam’ but keeping the rest.
> 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).
Hmm are you suggesting a PAM rewrite in Guile?
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-08-15 20:20 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 ` [bug#63383] Fwd: PAM may cause issues on system updates Felix Lechner via Guix-patches via
2023-08-15 20:19 ` Ludovic Courtès [this message]
2023-08-16 18:21 ` [bug#63383] [PATCH 0/4] Various PAM improvements 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=87cyzo83e1.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=63383-done@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
--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.