This has been argued over before. I don't think it should, the reason being that it's not 100% effective, and it will lull people into a false sense of security. Sure it blocks that <img> tag, but I'll bet you if I spent a half hour I could figure out something that would slip past the filter. A while ago it was as simple as a meta tag refresh, but I think that one got fixed ;')
The only thing that could be 100% effective would be to set your browser to use a real proxy for all protocols which would perform http->freenet relaying like fproxy but would block any outgoing non-freenet traffic. After I finish some of the stuff I'm working on, if no one else steps up, I will write one of these, maybe as a service to be run with the node, maybe external.. dunno. Anyway, with FCP in the node now we're in a good position to create this beast. On Mon, Apr 02, 2001 at 11:18:05PM +1200, David McNab wrote: > Oops! > So it does! > Hmmm, I wonder if this should be set on by default in the Windows installer. > > > >>>>> "DM" == David McNab <david at rebirthing.co.nz> writes: > > > > DM> Unless fproxy is reworked to handle this, the only defence I > > DM> can think of is to set one's firewall temporarily to block the > > DM> browser's access to external servers while surfing Freenet. > > Ahem. > > Set: > > services.fproxy.doFiltering=yes > > And the filtering goes on. > > > > ~Mr. Bad -- # tavin cole # if code is law, then Freenet is a crowded theater _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
