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: "Ludovic Courtès" <ludo@gnu.org>
Cc: 63383-done@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#63383] [PATCH 0/4] Various PAM improvements
Date: Wed, 16 Aug 2023 11:21:52 -0700	[thread overview]
Message-ID: <CAFHYt55cjoEfaoQCcyoxd+GzmQQWA0Fno4mv3+A9Dmjgc2qNLw@mail.gmail.com> (raw)
In-Reply-To: <87cyzo83e1.fsf_-_@gnu.org>

Hi Ludo'

On Tue, Aug 15, 2023 at 1:19 PM Ludovic Courtès <ludo@gnu.org> wrote:
>
> I’m dropping the patch that adds more absolute
> file names for all modules shipped with ‘linux-pam’ but keeping the rest.

Thanks for doing that. It was the right thing to do.

> Hmm are you suggesting a PAM rewrite in Guile?

Thanks for asking! I rewrote PAM in Guile some time ago [1] but it
still uses a shared library to start Guile via the good old "tortoise"
interface. [2] Upon reflection, I am not sure it would shelter us from
all potential compatibility issues on upgrades, including upgrades of
Guile.

Perhaps it would be best for Guix to adopt a fully script-driven
approach similar to OpenBSD. [3] Maxim may have alluded to it in a
correspondence on this topic elsewhere.

Kind regards
Felix

[1] https://codeberg.org/lechner/guile-pam
[2] https://www.gnu.org/software/guile/docs/guile-tut/tutorial.html#Tortoise
[3] https://blog.lambda.cx/posts/how-bsd-authentication-works/




  reply	other threads:[~2023-08-16 18:23 UTC|newest]

Thread overview: 4+ 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   ` bug#63383: [PATCH 0/4] Various PAM improvements Ludovic Courtès
2023-08-16 18:21     ` Felix Lechner via Guix-patches via [this message]
2023-05-09  0:56 [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=CAFHYt55cjoEfaoQCcyoxd+GzmQQWA0Fno4mv3+A9Dmjgc2qNLw@mail.gmail.com \
    --to=guix-patches@gnu.org \
    --cc=63383-done@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.