Re: [Gnash-dev] default load policy in gnashrc

[strk]

Since nobody answered I decided what to do :)

If a *whitelist* is found in the gnashrc, access
to any host *not* listed therein will be *forbidden*.

If you *do* have both 'whitelist' and 'blacklist', the
blacklist won't be used.

So, rationale is:
        - use 'whitelist' if you want to DENY by default
        - use 'blacklist' if you want to ACCEPT by default

--strk;

On Mon, Nov 13, 2006 at 10:33:38AM +0100, strk wrote:
> I've started using .gnashrc and found a conceptual limit in
> secirity specification.
> 
> We have a whitelist and a blacklist, but the default is always
> to grant access, so what's the point of a whitelist ?
> Should we consider a 'non-existent' whitelist as a default policy
> of *GRANT* and existenc of it as a default policy of *BLOCK* ?
> Or, should we add another variable in 'gnashrc' explicitly setting
> the default policy ?
> 
> --strk; 
> 
>  /"\    ASCII Ribbon Campaign
>  \ /    Respect for low technology.
>   X     Keep e-mail messages readable by any computer system.
>  / \    Keep it ASCII. 
> 
> 
> 
> _______________________________________________
> Gnash-dev mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnash-dev

-- 

 /"\    ASCII Ribbon Campaign
 \ /    Respect for low technology.
  X     Keep e-mail messages readable by any computer system.
 / \    Keep it ASCII.