summaryrefslogtreecommitdiff
path: root/debian/patches-applied/045_pam_dispatch_jump_is_ignore
diff options
context:
space:
mode:
authorSteve Langasek <vorlon@debian.org>2014-01-14 09:30:06 +0000
committerSteve Langasek <vorlon@debian.org>2019-01-08 22:11:52 -0800
commit76063db40810118bf431971dade8871633d06864 (patch)
treebf04fce4c2288ebf24e3465697b25b40a267172e /debian/patches-applied/045_pam_dispatch_jump_is_ignore
parente4b6c30426509601fddd1611f7db99b076626c17 (diff)
Another round of patch refreshing
Diffstat (limited to 'debian/patches-applied/045_pam_dispatch_jump_is_ignore')
-rw-r--r--debian/patches-applied/045_pam_dispatch_jump_is_ignore14
1 files changed, 7 insertions, 7 deletions
diff --git a/debian/patches-applied/045_pam_dispatch_jump_is_ignore b/debian/patches-applied/045_pam_dispatch_jump_is_ignore
index 672ab44d..0e3491d3 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.deb/libpam/pam_dispatch.c
+Index: pam.debian/libpam/pam_dispatch.c
===================================================================
---- pam.deb.orig/libpam/pam_dispatch.c
-+++ pam.deb/libpam/pam_dispatch.c
-@@ -251,19 +251,7 @@
+--- pam.debian.orig/libpam/pam_dispatch.c
++++ pam.debian/libpam/pam_dispatch.c
+@@ -254,19 +254,7 @@
if ( _PAM_ACTION_IS_JUMP(action) ) {
/* If we are evaluating a cached chain, we treat this
@@ -19,10 +19,10 @@ Index: pam.deb/libpam/pam_dispatch.c
- if (impression == _PAM_UNDEF
- || (impression == _PAM_POSITIVE
- && status == PAM_SUCCESS) ) {
-- if ( retval != PAM_IGNORE || cached_retval == retval ) {
+- if ( retval != PAM_IGNORE || cached_retval == retval ) {
- impression = _PAM_POSITIVE;
-- status = retval;
-- }
+- status = retval;
+- }
- }
- }
+ module as ignored as well as executing the jump. */