[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
A question of preferences
- To: or-talk@xxxxxxxxxxxxx
- Subject: A question of preferences
- From: Arrakis <arrakistor@xxxxxxxxx>
- Date: Thu, 15 Nov 2007 11:44:35 -0600
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Thu, 15 Nov 2007 12:46:59 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=0ooRhDcWXARsIhDfKWN74/IZOe8dRyfcPL9xNxrX/mk=; b=lk8FPZRtfkG8wl5Sb79XiQcmdToGnPLvHcGUL76zVYFLHnUZGvzNBZGXecCk0fA5Yxgu+Q1unEV+glgdy3sanNCFrgRoQHWROJeSTsRfqpiEPaczyXP4utoKM8w8YaPMA/+9wD97XEid9BDThzkwLFlmpFUpOcL1FZrJ0DfYSVQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=s778Ou+D7XFYNeVSDsdImFarCFRUMmQbX4RDR2XOFbKcEqp8utqMOzty/xW3UhV9HI031aooq9FnMogjaYbZj4XPMa5yqYt1naZjoT800jGzX1veC3WMczY7pa2ZRtOf8OWYVvt8X0zwB3+/Q4C/JFjUordaj5ftKrxS2GryAcQ=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Thunderbird 188.8.131.52 (Windows/20071031)
I'm writing the preferences for the xB Browser, and I've been thinking
about the problem of users who are smart enough to be dangerous to
themselves. I'm talking about those that jump into the proxy settings
and think they are speeding things up by changing to a direct connection
Well, yeah, they're speeding up alright, but at the cost of breaking
So it occurs to me I can keep those settings from being persistent
(nothing can stop someone who is determined to wreck their privacy). I
can do this by employing the user.js, which over-rides whatever the
users sets in their prefs.js files.
Therefore, I am thinking about what settings should be hard-coded on
The goal was "The purpose of user.js is to hardcode browser settings to
keep users from compromising their network anonymity beyond preferences."
That means for Tor/SSH usage, the browser needs to block plugins.
That means for VPN usage, the browser doesn't need to block plugins.
So now we're talking about two different user.js files entirely.
OK fine. But we get to a new point where we have to decide what things
should and shouldn't be blocked from being persistent from one session
to the next.
Of the following, beyond proxy settings, I'm thinking we should keep
network.dns.disableIPv6 = true ; ipv6 addresses fail through tor.
network.proxy.socks_remote_dns = true
network.proxy.failover_timeout = 0 ;always retry the proxy, never revert.
layout.css.report_errors = false ;get rid of java console errors
There are other privacy related settings such as DOM and session info
that are a grey area, but I am thinking those don't meet the above goal,
and thus should be left as preferences for the user.
Comments and suggestions welcome,