[wpkg-users] Firefox Proxy - unlocked

[Justin Brinegar]

lockPref and defaultPref are the way to go.  Example of in-production usage:

lockPref("signon.rememberSignons", false);
// prevent passwords from being saved

defaultPref("browser.cache.disk.capacity", 1024);
// 1mb of disk space for cache
defaultPref("browser.cache.disk.enable", true);
// enable the above
defaultPref("browser.cache.memory.capacity", -1);
// dynamic setting based on ram in machine
defaultPref("browser.cache.memory.enable", true);
// enable the above

Do note that there are *some* preferences that simply will not lock, and 
there are some that will not default.  Specifically, I encountered 
issues with defaulting the homepage in Firefox 3.5.  In Thunderbird (and 
to a lesser extent in Firefox), there are groups of settings that must 
all be locked before settings will actually lock.  This led to a 
non-intuitive approach for locking SMTP settings, among other 
interesting things.  My point: you may have to lock/default more 
settings than you would initially think.

I've locked down my deployment of Thunderbird and Firefox using locked 
and default preferences.  You can do some pretty cool things with it in 
Thunderbird, especially if your organization uses a single-sign on 
technology and has an LDAP server.

Justin

Tomasz Chmielewski wrote:
> On 02.03.2010 12:56, Christian Becker wrote:
>> Hi,
>>
>> I want to set the Proxy of Firefox. So I used the tutorial at wpkg.org
>> <http://wpkg.org>. Works fine, but these are only "locked" settings.
>> Is there a way to set Proxy - but unlocked - so that every user could
>> change it individually?
> 
> I think instead of "lockPref" you would have to use just "pref".
> 
> But you may want to experiment a bit yourself.
> 

-- 
Justin Brinegar
.. brinegar at physics.unc.edu
.. (919) 962 - 6494
.. Assistant Windows Administrator
.. Physics & Astronomy Networking Infrastructure and Computing
.. University of North Carolina at Chapel Hill