Skip to content

fix: recommend configuration profiles instead of policies.json in the app bundle on macOS (2089906) - #394

Merged
bsmth merged 1 commit into
mozilla:mainfrom
spohlMozilla:bug2089906-macOSConfigProfilesDocs
Nov 6, 2026
Merged

bsmth merged 1 commit into
mozilla:mainfrom
spohlMozilla:bug2089906-macOSConfigProfilesDocs

Conversation

@spohlMozilla

Copy link
Copy Markdown
Contributor

Description:

The "Configuring policies" guide no longer tells admins to put policies.json into Firefox.app/Contents/Resources/distribution on macOS. It now explains how to deploy policies with a configuration profile, and how to use /Library/Preferences/org.mozilla.firefox.plist on a Mac without device management.

Motivation:

Adding files to the app bundle breaks its code signature (codesign --verify --deep --strict fails). We'd like installed bundles to stay intact so that the privileged updater can verify them before it updates them.

Related issues and pull requests:

@mkaply, could you review this as well?

@spohlMozilla
spohlMozilla requested a review from bsmth as a code owner November 6, 2026 12:30
@mkaply

mkaply commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

you can also use sudo defaults write. we document that in the policy templates.

https://github.com/mozilla/policy-templates/tree/master/mac

The policies.json route is useful for developers at Mozilla and I direct people to this page so they know how to do it. I'm not sure how best to keep that information.

@spohlMozilla

Copy link
Copy Markdown
Contributor Author

you can also use sudo defaults write. we document that in the policy templates.

https://github.com/mozilla/policy-templates/tree/master/mac

Thank you! Adding now.

The policies.json route is useful for developers at Mozilla and I direct people to this page so they know how to do it. I'm not sure how best to keep that information.

@mkaply Are configuration profiles insufficient for developers at Mozilla? I am concerned that using policies.json is not going to be possible anymore in the not too distant future when macOS starts enforcing valid signatures on .app bundles more generally than right now. If configuration profiles are not sufficient, I'd like to get a bug on file to support this without causing the signatures to break, or having to resign the bundle (which may also no longer work as expected with deep signature verifications). And ultimately, removing support for policies.json in the .app bundle on macOS may be desirable as well to prevent admins from accidentally breaking Firefox, or its updates.

@spohlMozilla
spohlMozilla force-pushed the bug2089906-macOSConfigProfilesDocs branch from d857534 to 008c185 Compare November 6, 2026 12:58
@mkaply

mkaply commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

it's mainly in development situations where they put them in the obj directory (so signing doesn't matter).

@bsmth

bsmth commented Nov 6, 2026

Copy link
Copy Markdown
Collaborator

Looking good, thanks, I just have one comment where we can preserve the JSON method for convenience / testing.

@spohlMozilla
spohlMozilla force-pushed the bug2089906-macOSConfigProfilesDocs branch from 008c185 to 67d5779 Compare November 6, 2026 13:48

@bsmth bsmth left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@bsmth
bsmth merged commit b7b15f9 into mozilla:main Nov 6, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants