On Fri, Dec 29, 2000 at 09:03:45PM -0500, Benjamin Coates wrote:
> >From Brandon <[EMAIL PROTECTED]>
> >BC:
> >> I just want to mention that I don't think it's realistic to just forbid
> >> client-side code in Freenet; Far too many applications will need it,
> >> especially since the server-side code that makes many web things possible
> >> isn't available on Freenet, and we can't realistically add every
> concievable
> >> feature to the client like we did date-based redirects.
> >
> >Of course. But it's not forbidden. You can just optionally have a warning
> >system turned on.
> >
>
> "Forbid" was a poor choice of word. We need a method of using client-side
> code that does not compromise the anonymity or security of the user.
>
> --
> Benjamin Coates
Is the only possible anonymity threat something that causes the browser to
make a request over a non-freenet protocol like http? I mean, can we say
JavaScript is OK so long as it doesn't trick the browser into making
a non-freenet request?
If so, you can easily protect yourself just by configuring your browser
to use a non-existent proxy for any non-freenet protocol, or use a firewall,
or whatever.. right?
--
// Tavin Cole
_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
