summaryrefslogtreecommitdiff
path: root/debian/patches-applied/045_pam_dispatch_jump_is_ignore
diff options
context:
space:
mode:
authorSteve Langasek <vorlon@debian.org>2019-01-22 15:21:19 -0800
committerSteve Langasek <vorlon@debian.org>2019-01-24 11:54:00 -0800
commit5bbcd8f9bad73877325151b2024c6cdd858174b5 (patch)
tree424e9a64f3aaf5588154b86636cfa5cf6f79edad /debian/patches-applied/045_pam_dispatch_jump_is_ignore
parent5cd7bb4511a7c2b355a615f19a9eca193320aa3e (diff)
Refresh patches
Diffstat (limited to 'debian/patches-applied/045_pam_dispatch_jump_is_ignore')
-rw-r--r--debian/patches-applied/045_pam_dispatch_jump_is_ignore11
1 files changed, 7 insertions, 4 deletions
diff --git a/debian/patches-applied/045_pam_dispatch_jump_is_ignore b/debian/patches-applied/045_pam_dispatch_jump_is_ignore
index 0e3491d3..e19a5456 100644
--- a/debian/patches-applied/045_pam_dispatch_jump_is_ignore
+++ b/debian/patches-applied/045_pam_dispatch_jump_is_ignore
@@ -4,11 +4,11 @@ the chain and PAM_OK (aka required) in the frozen part of the chain.
No one on pam-list was able to explain this behavior, so I changed it
to be consistent.
-Index: pam.debian/libpam/pam_dispatch.c
+Index: pam/libpam/pam_dispatch.c
===================================================================
---- pam.debian.orig/libpam/pam_dispatch.c
-+++ pam.debian/libpam/pam_dispatch.c
-@@ -254,19 +254,7 @@
+--- pam.orig/libpam/pam_dispatch.c
++++ pam/libpam/pam_dispatch.c
+@@ -260,22 +260,7 @@
if ( _PAM_ACTION_IS_JUMP(action) ) {
/* If we are evaluating a cached chain, we treat this
@@ -20,6 +20,9 @@ Index: pam.debian/libpam/pam_dispatch.c
- || (impression == _PAM_POSITIVE
- && status == PAM_SUCCESS) ) {
- if ( retval != PAM_IGNORE || cached_retval == retval ) {
+- if ( impression == _PAM_UNDEF && retval == PAM_SUCCESS ) {
+- h->grantor = 1;
+- }
- impression = _PAM_POSITIVE;
- status = retval;
- }