summaryrefslogtreecommitdiff
path: root/debian/patches-applied
diff options
context:
space:
mode:
authorSam Hartman <hartmans@debian.org>2021-07-09 10:50:09 -0600
committerSteve Langasek <steve.langasek@canonical.com>2021-09-15 17:52:39 -0700
commit01dd10ca3efd89193c3f0429064b54bc09501eec (patch)
tree815675c1d564deb2e4a9b073dcd075e966106f0f /debian/patches-applied
parent04d20bb46f932e9963676d5bc4aff5be052435f3 (diff)
Revert "Prefer _PAM_ISA to DEFAULT_MODULE_PATH"
It turns out Debian uses DEFAULT_MODULE_PATH and _PAM_ISA in the opposite meaning of upstream. DEFAULT_MODULE_PATH is based on libdir, which is the multiarch path, while _PAM_ISA is /lib/security. So my patch had the opposite effect as intended.
Diffstat (limited to 'debian/patches-applied')
-rw-r--r--debian/patches-applied/lib_security_multiarch_compat8
1 files changed, 4 insertions, 4 deletions
diff --git a/debian/patches-applied/lib_security_multiarch_compat b/debian/patches-applied/lib_security_multiarch_compat
index 2ac671a4..e386ff39 100644
--- a/debian/patches-applied/lib_security_multiarch_compat
+++ b/debian/patches-applied/lib_security_multiarch_compat
@@ -24,16 +24,16 @@ Index: pam-1.4.0/libpam/pam_handlers.c
+ mod->dl_handle = _pam_dlopen(mod_path);
+ } else {
+ char *mod_full_path = NULL;
-+ if (asprintf(&mod_full_path, "%s/%s",
-+ _PAM_ISA, mod_path) >= 0) {
++ if (asprintf(&mod_full_path, "%s%s",
++ DEFAULT_MODULE_PATH, mod_path) >= 0) {
+ mod->dl_handle = _pam_dlopen(mod_full_path);
+ _pam_drop(mod_full_path);
+ } else {
+ pam_syslog(pamh, LOG_CRIT, "cannot malloc full mod path");
+ }
+ if (!mod->dl_handle) {
-+ if (asprintf(&mod_full_path, "%s%s",
-+ DEFAULT_MODULE_PATH, mod_path) >= 0) {
++ if (asprintf(&mod_full_path, "%s/%s",
++ _PAM_ISA, mod_path) >= 0) {
+ mod->dl_handle = _pam_dlopen(mod_full_path);
+ _pam_drop(mod_full_path);
+ } else {