[Date Prev][Date Next]
(ITS#3683) peername fails in 2.2.23-3
Full_Name: Anton Sluijtman
OS: Linux timewind 2.6.7 #2 Fri Jul 16 16:22:14 CEST 2004 i686 GNU/Linux
Submission from: (NULL) (188.8.131.52)
in version: 2.1.30-3
a configuration, like the following
access to attr=uid
by peername="137.56.*.*" * read
by * none
however in version: 2.2.23-3
This configuration does not grant access to the 137.56.*.* range anymore
by peername=*.*.*.* * read
does not even grant read access
by * read
does grant access
Leaving out the peername constraint and specifying: by * read
seems the be the only alternative, but this is as you understand
a major drawback.
Did I miss something in the documention? If so please tell me.
I would very much like continue to use the peername feature!