From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/pambase:master commit in: /
Date: Wed, 4 Mar 2020 17:32:19 +0000 (UTC) [thread overview]
Message-ID: <1583343121.7eaf47da1d6cd18a8253c25213c34b16ae08e87f.soap@gentoo> (raw)
commit: 7eaf47da1d6cd18a8253c25213c34b16ae08e87f
Author: David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 4 17:32:01 2020 +0000
Commit: David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Wed Mar 4 17:32:01 2020 +0000
URL: https://gitweb.gentoo.org/proj/pambase.git/commit/?id=7eaf47da
Run pam_env.so after pam_systemd.so for better socket support
* Running pam_systemd.so before setting user environment
variables makes it possible for the user to use variables
such as `XDG_RUNTIME_DIR` in their own definitions.
Bug: https://bugs.gentoo.org/711450
Signed-off-by: David Seifert <soap <AT> gentoo.org>
system-auth.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/system-auth.in b/system-auth.in
index 02d0e50..e65e4c2 100644
--- a/system-auth.in
+++ b/system-auth.in
@@ -34,7 +34,6 @@ password optional pam_permit.so
#if HAVE_PAM_SSH
session optional pam_ssh.so
#endif
-#include "system-session.inc"
#if HAVE_SYSTEMD
-session optional pam_systemd.so
@@ -47,3 +46,4 @@ session optional pam_ssh.so
#if HAVE_LIBCAP
auth optional pam_cap.so
#endif
+#include "system-session.inc"
next reply other threads:[~2020-03-04 17:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 17:32 David Seifert [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-13 21:15 [gentoo-commits] proj/pambase:master commit in: / Mike Gilbert
2025-04-13 21:15 Mike Gilbert
2025-04-13 21:15 Mike Gilbert
2025-04-13 21:15 Mike Gilbert
2025-04-13 21:15 Mike Gilbert
2025-04-13 21:15 Mike Gilbert
2025-02-23 23:46 Sam James
2023-11-13 6:20 Sam James
2021-11-14 11:55 Mikle Kolyada
2020-10-12 15:28 Sam James
2020-08-05 6:13 Sam James
2020-08-05 6:04 Sam James
2020-06-18 10:11 Mikle Kolyada
2020-06-17 18:30 Mikle Kolyada
2020-06-16 16:26 Mikle Kolyada
2020-06-10 11:50 Mikle Kolyada
2020-06-10 11:50 Mikle Kolyada
2020-04-29 21:37 Mikle Kolyada
2019-11-28 18:21 Mikle Kolyada
2019-11-27 9:27 Mikle Kolyada
2019-11-24 14:37 Mikle Kolyada
2019-11-15 18:09 Mikle Kolyada
2019-04-02 13:11 Mikle Kolyada
2015-05-17 5:22 Mike Frysinger
2015-02-15 4:48 Mike Frysinger
2015-02-15 4:48 Mike Frysinger
2015-02-15 4:48 Mike Frysinger
2015-02-15 4:48 Mike Frysinger
2014-03-13 14:40 Samuli Suominen
2014-03-13 14:17 Samuli Suominen
2014-03-13 14:12 Samuli Suominen
2012-04-17 7:10 Paweł Hajdan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1583343121.7eaf47da1d6cd18a8253c25213c34b16ae08e87f.soap@gentoo \
--to=soap@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox