unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: muradm <mail@muradm.net>
Cc: guix-devel@gnu.org
Subject: Re: Enabling PAM support or not only..
Date: Wed, 24 May 2023 12:01:49 -0400	[thread overview]
Message-ID: <87v8ghhg5u.fsf@gmail.com> (raw)
In-Reply-To: <87r0r78sul.fsf@muradm.net> (muradm's message of "Tue, 23 May 2023 08:24:50 +0300")

Hi Muradm,

muradm <mail@muradm.net> writes:

[...]

> core-updates merging commit 3bacd3c76a added linux-pam to cups
> package. Resulting in https://issues.guix.gnu.org/issue/63198.
> While switching cups-service-type's default package from cups
> to cups-minimal solves authentication issue, it however
> broke ipptool printer finder tool. When PAM support is
> compiled in, it does not work without proper PAM entry.
>
> While workaround could be as simple as:
>
> +(simple-service
> + 'cups-pam-service
> + pam-root-service-type
> + (list (unix-pam-service "cups" #:allow-empty-passwords? #f)))
>
>
> Total solution could be:
> https://issues.guix.gnu.org/issue/63198#4

Now applied, thanks.

>
> swaylock with screen-locker-service-type:
>
> commit 146bae3979 added linux-pam to swaylock package. Resulting
> in https://issues.guix.gnu.org/issue/63357#2.
>
> While workaround could be as simple as:
>
> -(service screen-locker-service-type
> -         (screen-locker-configuration
> -          "swaylock" (file-append swaylock "/bin/swaylock") 
>            #f)))))
> +(simple-service
> + 'cups-pam-service
> + pam-root-service-type
> + (list (unix-pam-service "cups" #:allow-empty-passwords? #f)))
>
> Detailed explanation with total solution is provided in
> https://issues.guix.gnu.org/issue/63652.
>
>
> The following coming afterwards to my mind:
>
> GUIX at first is package manager, so there are a lot of them,
> but of two types:
>   - BOUND - ones referenced from (gnu system) (gnu services)
>   - FREE-STANDING - ones not referenced

I don't know about swaylock, but for CUPS, the change was strictly
required; you can't build the full CUPS without PAM anymore, I think.  I
had tried as a possible solution to the PAM problems.

So the distinction between bound and free-standing in this context is
not very useful (when the changes are forced by upstream rather than
chosen by the contributors).  What would be useful though is increasing
our test coverage to catch these issues.

-- 
Thanks,
Maxim


      reply	other threads:[~2023-05-24 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23  5:24 Enabling PAM support or not only muradm
2023-05-24 16:01 ` Maxim Cournoyer [this message]

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=87v8ghhg5u.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@muradm.net \
    /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).