Red Hat Bugzilla – Bug 89671
Netatalk default pam file does not take authconfig settings
Last modified: 2007-11-30 17:10:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows NT 5.0) Opera
Description of problem:
The default netatalk package installs a file in /etc/pam.d that only works if
you use /etc/passwd and friends and not f.x ldap.
The solution is to change the file to one that uses pam_stack.so
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Install netatalk on a new computer.
Actual Results: people will not be able to log in by using ldap.
Expected Results: I didn't expect pam to be the problem.
This bug has been moved to Fedora Core for investigation against the
shipping 1.6.4 version there.
I just got bit by this one.
It's now 2005 and this bug (posted in *april* of 2003) still exists -- come on
guys, just replace pam.d/netatalk! pam.d/sshd is an excellent template.
Here, look, I'll attach the configuration file to this bug report. Just save it
and rebuild the rpm and we'll all be happy.
Created attachment 109235 [details]
A pam configuration for netatalk that uses system-auth
Sorry for the delay in processing this bug - the previous maintainer
of netatalk has moved on.
PAM configuration files are meant to be configured by the system
administrator to suit local policies.
If your local policy is to allow LDAP or NIS users to use netatalk,
then you have been able to configure netatalk accordingly.
I'm not sure that your modifications to pam.d/netatalk should be
the default for all users . The new authentication policy would
need extensive testing to ensure that no password data can be
I've included it in the next release of netatalk, 2.0.3-2, in
/usr/share/doc/netatalk-2.0.3/config.example/, along with
Even if it were the default in the RPM, it would not replace
/etc/pam.d/netatalk during upgrade because this file is marked
%config(noreplace) in the spec.file, as it is meant to be user
I'm currently testing your pam.d/netatalk file on my netatalk
installation and will make it the default pam.d/netatalk file
in future releases if it causes no problems and if the upstream
maintainers agree to making it the default.