Article delegate-en/4215 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
search
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
[Reference:<_A4214@delegate-en.ML_>]
Newsgroups: mail-lists.delegate-en

[DeleGate-En] Re: ACLs PERMIT/REJECT priority order
18 Nov 2008 02:20:14 GMT feedback@delegate.org (Yutaka Sato)
The DeleGate Project


Hi,

In message <_A4214@delegate-en.ML_> on 11/17/08(22:00:12)
you Dmitry Donskih <ppyhqbdyi-h5qfbmz6rw3r.ml@ml.delegate.org> wrote:
 |Could anyone explain in what order PERMIT REJECT REMITTABLE etc.
 |parameters are processed?
 |Or is there any way to prioritize such parameters
 |(i.e. like MOUNT pri=XX option does)?

There is no priority among them because all of them must be satisfied 
to be permitted.  Any parameter except REJECT must be sutisfied if
specified (explicitly or implicitly).  And if REJECT is given and
matched, the access is forbidden regardless of any other access control
parameters.
You can see it in the implementation of "access.c:PERMITTED_ACCESS()".

Cheers,
Yutaka
--
  9 9   Yutaka Sato <y.sato@delegate.org> http://delegate.org/y.sato/
 ( ~ )  National Institute of Advanced Industrial Science and Technology
_<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller

  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
@_@V