1047742 - Find new way to allow for administratively configured installs to lock prefs on OSX, due to v2 signing requirements

Status: RESOLVED WONTFIX

(Core :: Preferences: Backend, defect)

Description

[Stephen A Pohl [:spohl]]

This is very similar to bug 1047738, with the difference that we used to allow for partner builds that locked prefs. Our current way of doing this is no longer going to work due to the v2 signing requirements, since we can no longer modify any files inside the top-level .app bundle after it was signed. We will need to find a new solution if we want to support these kinds of partner builds that lock prefs.

Comment 1

[Robert Strong (they/them - no direct email)]

Should either be core -> preferences or firefox -> preferences

Comment 2

[Mike Kaply [:mkaply]]

Can you give an example of a partner that locks prefs?

Comment 3

[Robert Strong (they/them - no direct email)]

This is for administratively configured installs. Stephen confused administratively configured vs. partner builds so I fixed the summary.

Comment 4

[Robert Strong (they/them - no direct email)]

As it stands the administrator can accomplish this by running the app and then modifying the bundle. We can decide if we want to do anything else later and if so in a new bug.

Comment 5

[Mike Kaply [:mkaply]]

The code to look for the autoconfig file was not changed for Mac, so AutoConfig is broken on Firefox 34.

http://hg.mozilla.org/mozilla-central/filelog/18188c19a3c3/extensions/pref/autoconfig/src/nsReadConfig.cpp

http://mxr.mozilla.org/mozilla-central/source/extensions/pref/autoconfig/src/nsReadConfig.cpp#242

Comment 6

[Robert Strong (they/them - no direct email)]

This bug was for finding a new way to accomplish locking prefs which isn't needed and what you have found is a different bug so please file a new bug for the issue you have found.