Re: Please help test the PAM in experimental

2024-01-20 Thread Svante Signell
Hi,

you don't seem to address:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029097
why?

On Fri, 2024-01-19 at 11:40 -0700, Sam Hartman wrote:
> 
> There are a number of changes, and I'd just like a bit more
> confidence
> that it works as expected before uploading to unstable in about a
> week.
> 
> Changes include:
> 
> * Running pam_umask with usergroups support by default.
> 
> * libpam-modules now depends on libsystemd0 because utmp is not
>   y2038-clean and upstream has decided to depend on elogind for that.
> 
> * New PAM upstream and thus newly rebased patches.
> 
> So, it would be helpful especially if you would install libpam-
> modules
> and libpam0g from experimental.



Re: Please help test the PAM in experimental

2024-01-20 Thread Luca Boccassi
On Fri, 19 Jan 2024 at 18:41, Sam Hartman  wrote:
>
>
> There are a number of changes, and I'd just like a bit more confidence
> that it works as expected before uploading to unstable in about a week.
>
> Changes include:
>
> * Running pam_umask with usergroups support by default.
>
> * libpam-modules now depends on libsystemd0 because utmp is not
>   y2038-clean and upstream has decided to depend on elogind for that.
>
> * New PAM upstream and thus newly rebased patches.
>
> So, it would be helpful especially if you would install libpam-modules
> and libpam0g from experimental.

Thanks for the update, looks good in my testing VM, will check on my
testing desktop later.

I see one warning due to pam_lastlog being deprecated but still in the
default config:

[495799.050948] login[55]: PAM unable to dlopen(pam_lastlog.so):
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No
such file or directory
[495799.051113] login[55]: PAM adding faulty module: pam_lastlog.so

I guess this needs to be filed against the login package, as that's
shipping the rule enabling it?



Please help test the PAM in experimental

2024-01-19 Thread Sam Hartman

There are a number of changes, and I'd just like a bit more confidence
that it works as expected before uploading to unstable in about a week.

Changes include:

* Running pam_umask with usergroups support by default.

* libpam-modules now depends on libsystemd0 because utmp is not
  y2038-clean and upstream has decided to depend on elogind for that.

* New PAM upstream and thus newly rebased patches.

So, it would be helpful especially if you would install libpam-modules
and libpam0g from experimental.


signature.asc
Description: PGP signature