Package: libapache2-mod-auth-pam Followup-For: Bug #412981 I hit the same problem upon upgrading from sarge to etch. Probably I will not be the last one, too, that will have to consult the BTS.
Regarding question 2: It is caused by the fact that the default for the directive AuthBasicProvider is "file". If no file is found (because it is not configured) and therefore the user can not be authenticated by it, the option AuthBasicAuthoritative means that "non-authoritative" authentication methods like pam can be used. Maybe this is meant as a warning, indicating that pam is not the most secure method. Cheers, Johannes -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-xen-amd64 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libapache2-mod-auth-pam depends on: ii apache2.2-common 2.2.3-3.3 Next generation, scalable, extenda ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libpam0g 0.79-4 Pluggable Authentication Modules l libapache2-mod-auth-pam recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
