[hylafax-users] PAM (new Hylafax server change?) and other login changes....

[Karl Denninger <karl@xxxxxxxxxxxxx>]

Hi folks;

I've got a  "live one."

Updated to the most recent HylaFax release and suddenly all my client 
logins broke.

Looking through the logs it appears that HylaFax is now hitting the PAM 
service whenever it doesn't find a match in the hosts.hfaxd
table.  But - the documentation says nothing about this, and it isn't 
matching the "wild card" user records that used to work (e.g. 
"user@^.*::some-password")  Also, the old wild-card stemming for IP 
addresses (e.g. "192.168.") doesn't work any longer either!

So - what needs to be in the /etc/pam.d directory?  I'm cool with it 
using the Unix password file but I can't find the magic incantation and 
its not referenced in the current documentation.

--
Karl Denninger (karl@xxxxxxxxxxxxx)
http://www.denninger.net




%SPAMBLOCK-SYS: Matched [@hylafax.org], message ok


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*