[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnash-dev] default load policy in gnashrc
From: |
strk |
Subject: |
Re: [Gnash-dev] default load policy in gnashrc |
Date: |
Mon, 20 Nov 2006 15:43:28 +0100 |
On Mon, Nov 20, 2006 at 03:20:36PM +0100, Tomas Groth wrote:
> > So, rationale is:
> > - use 'whitelist' if you want to DENY by default
> > - use 'blacklist' if you want to ACCEPT by default
>
> This seems logical to me, so fine by me :)
>
> I was thinking that maybe we should also support regular expressions (or
> similar) when defining black/whitelist, so that it is easier to block
> communication to standard server name such as
> "violating.your.privacy.[a-z]*.com"...
The manual page talks about "domains" rather then hostnames, meaning
that we should consider the entries as regexp in the form .*.name.
This would make presence of *bo&h* whitelist/blacklist meaningful.
Example:
blacklist spammers.com
whitelist special.spammers.com
Any use of regexp-like strings will require us to implement the concept
of a *best matching* line, so that the 'stricter' mathcing is used.
In the above example, www.special.spammers.com would be allowed, altogut
matching both blacklist and whitelist.
> Maybe an option to forbid connections to adresses not on the main sites should
> be implemented as well.
Could you expand this ?
--strk;
Re: [Gnash-dev] default load policy in gnashrc, Rob Savoye, 2006/11/20
Re: [Gnash-dev] default load policy in gnashrc, strk, 2006/11/20
Re: [Gnash-dev] default load policy in gnashrc, Rob Savoye, 2006/11/20
[Gnash-dev] crossdomain policy (was: default load policy in gnashrc), strk, 2006/11/20