-
I'm raising the priority on this a little, because for us, the new version of pam_access completely breaks our authorization setup.
2009-11-06 18:28:19 UTC in Pluggable Auth Modules
-
Background:
Our netgroups look like:
login_samplehost.example.com (-, apollock, )
Our access.conf looks like:
+:root:ALL
+:@login_samplehost.example.com:ALL
-:ALL:ALL
To be clear, we have per-host netgroups.
As of the change made in
http://pam.cvs.sourceforge.net/viewvc/pam/Linux-PAM/modules/pam_access/pam_access.c?view=diff&pathrev=Linux-PAM-1_0_90&r1=1.29&r2=1.30...
2009-11-04 21:24:25 UTC in Pluggable Auth Modules
-
Hi,
I was just trying out Barada, and it doesn't appear to do any logging on success or failure. This would be useful.
regards
Andrew.
2009-01-14 03:21:41 UTC in Barada
-
Hi,
I just tried out Barada, and while it works for authentication, the application requesting the authentication complains:
PAM unable to resolve symbol: pam_sm_setcred
From my brief research on this error, it appears that PAM modules should define this function even if they do not set credentials.
regards
Andrew.
2009-01-14 03:20:57 UTC in Barada
-
According to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508148, simpleproxy performs poorly when nss_mdns is in use (because of a call to gethostbyaddr()), which is now the default in at least Debian. The attached patch fixes this by changing the call to getnameinfo()
2008-12-09 07:18:34 UTC in simpleproxy
