Package: libpam-ldap Version: 184-8.6 Severity: normal Dear Maintainer,
after upgrading from squeeze to wheezy, pam_ldap behaviour changed. in the squeeze setup the pam file for pure-ftpd contained: " auth sufficient pam_ldap.so config=/etc/pam_ldap_pureftpd.conf auth required pam_deny.so account sufficient pam_ldap.so config=/etc/pam_ldap_pureftpd.conf account required pam_deny.so session optional pam_ldap.so config=/etc/pam_ldap_pureftpd.conf " and also a pam_ldap_pureftdp.secret existed after the upgrade to wheezy, a pam_ldap.secret is needed, which i did not have before; hence it is more difficult (how?) to use different ldap servers for different services and it feels consistent with this pam setup error messages: " .. pure-ftpd: pam_ldap: could not open secret file /etc/pam ldap.secret (No such file or directory) Jul 8 14:55:11 pure-ftpd: pam_ldap: ldap_search_s Operations error.. " so a link (pam_ldap.secret) to pam_ldap_pureftpd.secret fixed it, but cf comments supra hth, Wim -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=nl_BE@euro, LC_CTYPE=nl_BE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages libpam-ldap depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38 ii libldap-2.4-2 2.4.31-1+nmu2 ii libpam-runtime 1.1.3-7.1 ii libpam0g 1.1.3-7.1 libpam-ldap recommends no packages. Versions of packages libpam-ldap suggests: ii libnss-ldap 264-2.5 -- debconf information man added * shared/ldapns/base-dn: dc=intranet,dc=somedomain,dc=org * libpam-ldap/dbrootlogin: false * libpam-ldap/override: true * shared/ldapns/ldap-server: ldaps://ad.someworkingldapadserver.org:636 libpam-ldap/pam_password: crypt libpam-ldap/binddn: cn=proxyuser,dc=example,dc=net libpam-ldap/rootbinddn: cn=manager,dc=example,dc=net * shared/ldapns/ldap_version: 3 * libpam-ldap/dblogin: false -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
