summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSteve Langasek <vorlon@debian.org>2009-08-18 17:58:51 -0700
committerSteve Langasek <vorlon@debian.org>2019-01-08 19:42:00 -0800
commitcfee2ebe3192b620fa0b42edea334ccf1eb3aca8 (patch)
tree220c828c7b23657858a6208e5eb89a77db393989
parent6ecbab3d81d4f21cde42605dce7c3a44dbdcb70b (diff)
drop references to pam_stack, which is long dead
-rw-r--r--debian/local/Debian-PAM-MiniPolicy10
1 files changed, 0 insertions, 10 deletions
diff --git a/debian/local/Debian-PAM-MiniPolicy b/debian/local/Debian-PAM-MiniPolicy
index 84b020ca..91722fb9 100644
--- a/debian/local/Debian-PAM-MiniPolicy
+++ b/debian/local/Debian-PAM-MiniPolicy
@@ -73,16 +73,6 @@ to reference the basename (eg. "pam_unix.so"). This will ensure that the
program continues to work even if the module location changes, since
libpam itself will resolve the location.
-You should not use the pam_stack module in the pam config file.
-It's not currently in Debian so it won't work. While I cannot stop
-someone from packaging pam_stack for Debian, I will try to convince
-them that it is not the direction we want. Pam_stack (among other
-faults) uses different pam handles for each step in the process--the
-handle used for session management is not the same as the handle used
-for authentication. This breaks several modules. We have an alternate
-solution for shared PAM configuration across modules, in the form of
-the @include directive.
-
Currently libpam-modules is in the base setup, so its dependency is not
needed (since the library depends on the correct version). However, if any