Opened 12 years ago

Last modified 11 years ago

#585 closed enhancement (Implemented)

Check what, if any, settings are needed in prefs.js

Reported by: sjmurdoch Owned by:
Priority: High Milestone:
Component: Applications/Torbutton Version: 1.1
Severity: Keywords:
Cc: sjmurdoch Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I added some changes to the Tor Browser Bundle to improve user privacy. These appear to work with Torbutton,
but there could be conflicts I have missed. The changes were made in revision r12889:

http://cvs.seul.org/viewcvs/viewcvs.cgi/torpedo/trunk/build-scripts/config/prefs.js?root=Tor&rev=12889&r1=12840&r2=12889

Do these look OK? It some are useful, but are not already applied by Torbutton, maybe they should be folded in so as to
to be useful to more users. If they are redundant, but don't conflict, is there a problem in leaving them in (belt
and braces)?

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (1)

comment:1 Changed 11 years ago by mikeperry

flyspray2trac: bug closed.
Went through these. The only one of note is network.proxy.failover_timeout, but according to the mozillazine docs, it only applies if the network.proxy.type is 2 (autoconfig). We use 1 (fixed proxy).

I don't think they should conflict if you leave them set in torbrowser, but the unrestricted xpconnect pref could cause breakage somewhere. That pref is completely undocumented.

Note: See TracTickets for help on using tickets.