Re: [PATCH v2 3/7] gnu: Allow OS configurations to add PAM session modules

[宋文武 <iyzsong@gmail.com>]

2015-08-26 15:21 GMT+08:00 Andy Wingo <wingo@igalia.com>:
> On Tue 25 Aug 2015 23:39, ludo@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo <wingo@igalia.com> skribis:
>>
>>> On Tue 25 Aug 2015 16:55, ludo@gnu.org (Ludovic Courtès) writes:
>>>
>>>>   (operating-system
>>>>     ;; ...
>>>>     (pam-services (map (lambda (service)
>>>>                          (pam-service
>>>>                            (inherit service)
>>>>                            (session (cons ...))))
>>>>                        (base-pam-services))))
>>>>
>>> How would that work for other services like slim, mingetty, etc?
>>
>> Oh, it wouldn’t.
>>
>> Just to help me understand, could you explain the typical use case you
>> have in mind?
>
> Sure.  So right now on a Guix system you have /etc/pam.d, and it
> contains configurations for all services that interact with PAM.
> Notably there is "login", for console login, but also slim and lsh.
> Elogind wants to know about all user sessions so it should add a
> "session required /path/to/pam_elogind.so" line to all files in
> /etc/pam.d.  This causes login and logout to signal elogind.
>
> That's how I ended up adding #:additional-session-modules to all the
> other services: mingetty, slim, lsh.
>
> I don't know what the right design is.  I think ideally anything that
> would log in would include some central file rather than having to
> repeat the rules everywhere.
Yes, we can ues 'include' in pam config, this is how the ArchLinux do it:
  https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/pambase
  https://projects.archlinux.org/svntogit/packages.git/tree/trunk/slim.pam?h=packages/slim