Jesse Houwing <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> Don Dwiggins wrote:
>
....
> > I just saw the Configurable Security Policies page, and it looks like a
> > promising tool. I'll definitely use the "disable popup" setting. However,
> > I'd also like to disable other things. I've read a bit about JS being used
> > to "spy" on browser users, and that's an obvious hole (or set of holes) to
> > close.
> >
> > What I'd like to achieve, if possible, is a sort of "80% solution" -- not
> > necessarily bulletproofing the browser, but at least giving me a comfortable
> > enough feeling to leave JS enabled.
....
> Look at:
>
> http://www.mozilla.org/projects/security/components/configPolicy.html
Yes, that's the article I referenced in my first message. My question is,
other than disabling popups (which the article shows how to do), what would
be a good set of restrictions to put on what downloaded JS can do?
--
Don Dwiggins Solvitur ambulando
[EMAIL PROTECTED]
