Open Bug 1047740 Opened 10 years ago Updated 2 years ago

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

Categories

(Core :: Preferences: Backend, defect)

Product:
Core
Component:
Preferences: Backend
Platform:
x86
macOS
Type:
defect

Tracking

()

People

(Reporter: spohl, Unassigned)

References

Details

This is very similar to bug 1047738, with the difference that we used to allow for partner builds that added 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 add prefs.
Blocks: 1047742
Flags: needinfo?(mconnor)
Component: Application Update → Preferences: Backend
Product: Toolkit → Core
Summary: Find new way to allow for partner builds that add prefs on OSX, due to v2 signing requirements → Find new way to allow for administratively configured builds to add prefs on OSX, due to v2 signing requirements
Summary: Find new way to allow for administratively configured builds to add prefs on OSX, due to v2 signing requirements → Find new way to allow for administratively configured installs to add prefs on OSX, due to v2 signing requirements
No longer blocks: 1047584
Group: mozilla-employee-confidential
What do you mean by administratively configured installs versus distribution? Are you referring to AutoConfig (the primary way administrators configure Firefox)?
Robert, could you clarify?
Flags: needinfo?(robert.strong.bugs)
This bug is for adding prefs to an install in general. Bug 1047742 is for using a config file and could be renamed if you like. Note that since these bugs were filed we believe we have found a way to handle this.
Flags: needinfo?(robert.strong.bugs)
Flags: needinfo?(mconnor)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.