I'm about to make a change in the way configurable security policies are 
stored, and I wanted to let everyone know. The instructions at 
http://www.mozilla.org/projects/security/components/ConfigPolicy.html 
still apply, except for the following change: When you create one or 
more site-specific policies, you must add one additional line to prefs, 
that looks like this:

user_pref("capability.policy.policynames", "mypolicy");

where "mypolicy" is the name of the policy you created. For example, if 
you want to stop all popup windows from appearing on yahoo.com, you 
might use these prefs:

user_pref("capability.policy.annoyingsites.sites", "http://www.yahoo.com";);
user_pref("capability.policy.annoyingsites.Window.open", "noAccess");

As of tomorrow's build, you will have to add this line as well:

user_pref("capability.policy.policynames", "annoyingsites");

As of tomorrow, site-specific policies *will not work* without adding 
this line. If you have more than one site-specific policy, add their 
names to the "policynames" line; do not add a second "policynames" line. 
For example,

user_pref("capability.policy.policynames", "annoyingsites, spamsites, 
othergroup");

Use commas and/or spaces to separate the names. Also note that the 
default policy is unaffected and doesn't need to be listed on the 
policynames line. If you don't use site-specific policies you can ignore 
this message.

I apologize in advance for the added hassle, but this change makes 
possible a major performance boost. This is bug 119646 if anyone's 
curious. I'm going to update the docs as well.
        -Mitch


Reply via email to