GNU bug report logs - #63357
[PATCH] gnu: swaylock: Add linux-pam to inputs

Previous Next

Full log

Message #16 received at 63357-done <at> debbugs.gnu.org (full text, mbox):

From: "Benjamin" <benjamin <at> uvy.fr>
To: "Andrew Tropin" <andrew <at> trop.in>, Ludovic Courtès
 <ludo <at> gnu.org>
Cc: 63357-done <at> debbugs.gnu.org, muradm <mail <at> muradm.net>
Subject: Re: bug#63357: [PATCH] gnu: swaylock: Add linux-pam to inputs
Date: Mon, 22 May 2023 17:53:32 +0200

Hello,

> One of our colleagues mentioned that it's a breaking change and swaylock
> with pam backend will complain if suid is set, so the old setups with
> (screen-locker-service swaylock) will break after this commit.
>
> Do we want to document how to configure pam for swaylock in manual and
> add a news entry for this change?

First of all sorry for the breaking change.

I am pretty new to guix and did not know about screen-locker-service.
How I managed to make this to work is by setting a custom pam system
service :

(define-public swaylock-pam-service-type
  (service-type (name 'swaylock)
                (extensions (list (service-extension pam-root-service-type
                                                     (const (list (pam-service
                                                                   (name "swaylock")
                                                                   (auth (list
                                                                          (pam-entry
                                                                           (control "include")
                                                                           (module "greetd"))))))))))
                (description "Swaylock pam configuration")
                (default-value '())))

I do not know the policy in case of breaking changes, but if it is
easier we can roll back this change maybe ?

Best

Benjamin

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.