Bug 1391836 - provide fedora specific systemd-user PAM file
Summary: provide fedora specific systemd-user PAM file
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-04 08:13 UTC by Yu Watanabe
Modified: 2017-01-12 19:22 UTC (History)
9 users (show)

Fixed In Version: systemd-232-2.fc26
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-12 01:17:42 UTC
Type: Bug


Attachments (Terms of Use)

Description Yu Watanabe 2016-11-04 08:13:30 UTC
Description of problem:

systemd-232 provides the minimal systemd-user PAM configuration, and this does not include pam_limits.so.
Please provide the previous version of systemd-user PAM file.

Version-Release number of selected component (if applicable):

systemd-232-1

Actual results:

systemd-user PAM configuration file does not contain about pam_limits.so

Expected results:

systemd-user PAM includes system-auth PAM file.

Additional info:
https://github.com/systemd/systemd/commit/baed1fedba161d7db89636a417751891831c432a

Comment 1 Jan Pokorný [poki] 2017-01-11 15:25:43 UTC
IIUIC, this is already fixed in rawhide.

Comment 2 Zbigniew Jędrzejewski-Szmek 2017-01-11 17:17:15 UTC
No, it needs reverting of the upstream change. Done now, but I won't rebuild yet, since there are other outstanding issues.

Comment 3 Zbigniew Jędrzejewski-Szmek 2017-01-12 01:17:42 UTC
Pfff, you're right, it was already fixed. I think I must have overridden the file locally by installing directly from sources.

Comment 4 Jan Pokorný [poki] 2017-01-12 19:22:30 UTC
FYI, I was scratching this surface as I was becoming desperate because
systemd user sessions were not working for me in rawhide installation.

Because of very superficial error reporting (cf.
https://github.com/systemd/systemd/issues/5000#issuecomment-271899678)
I first thought that something with PAM (or NSS) is wrong on
my system while in fact it was lethal combination of SELinux
and dontaudit policy rules that made real root cause hard to
discover; see [bug 1401625 comment 9] + [bug 1412165] spin-off.


Note You need to log in before you can comment on or make changes to this bug.