Actually, I was wrong. Further testing shows that pam_access simply does
not work as advertised. Those Windows groups with spaces can't be used.
A similar configuration on CentOS does work.
Same with pam_listfile, which works on CentOS, doesn't on Debian. I'm
unsure where the problem is, Samb
Le 08/12/2010 06:25 PM, Camaleón a écrit :
Better "RTCM" → Read The *Correct* Manual
Well, «Correct» is a stretch.
I just found out that you need to put *exactly* this as a pam_access
parameter:
listsep = ,
If you don't put the spaces (as in the manual's example), then the
content of acce
On Thu, 12 Aug 2010 16:00:38 +0200, Laurent Blume wrote:
> Le 08/12/2010 01:09 PM, Camaleón a écrit :
>> Mmm, couldn't be that here apply the same restrictions as for
>> usernames?
>
> Aha, I didn't know that it was so restrictive. But actually, I'm lucky,
> I had read access.conf(5), but overloo
Le 08/12/2010 01:09 PM, Camaleón a écrit :
Mmm, couldn't be that here apply the same restrictions as for usernames?
Aha, I didn't know that it was so restrictive.
But actually, I'm lucky, I had read access.conf(5), but overlooked this
in pam_access(8), which specifically covers my case:
lis
On Thu, 12 Aug 2010 10:20:50 +0200, Laurent Blume wrote:
> I'm trying to restrict access in /etc/security/access.conf based on
> group names which have spaces in them (Windows domains groups, in the
> form DOMAIN+group of users). It already works for groups without a
> space.
>
> I tried escaping
Hello all,
I'm trying to restrict access in /etc/security/access.conf based on
group names which have spaces in them (Windows domains groups, in the
form DOMAIN+group of users). It already works for groups without a space.
I tried escaping with \ or quoting, but it didn't seem to work. Any id
6 matches
Mail list logo
