[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 16:06:14 +0100 |
On Mon, Nov 20, 2006 at 03:55:06PM +0100, Tomas Groth wrote:
> > > Maybe an option to forbid connections to adresses not on the main sites
> > should
> > > be implemented as well.
> >
> > Could you expand this ?
> >
>
> The idea of this is based on normal web-ads, which uses cookies to identify
> you. This can in many cases be blocked by disabeling cookies from "foreign"
> sites. Example: You're browsing www.site1.com, which contains an ads which is
> fetched from www.web-ads.com/ad1.html, and that code tries to make a cookie on
> your pc, but because it's not on www.site1.com, it can be blocked. I think
> this
> is a option in some browsers, but i'm not sure if this is actually needed in
> gnash...
The same effect could be obtained by filling the 'whitelist' on
the fly with a single host: the one from which the toplevel movie
is loaded.
This reminds me of a current problem in gnash... We feed the
standalon player with the movie from stdin, so whitelist/blacklist
has NO effect on top-level movie. I didn't verify this but I suppose
no load of toplevel movie will currently be blocked. Should test
this and add support for this (using the url passed with -u might
be a quick hack).
--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