On 8/13/14 2:59 PM, Benjamin Smedberg wrote: > > On 8/13/2014 3:34 AM, Philipp Kewisch wrote: >> >> Does this also affect binary extensions in any way? I'd imagine that >> globally installed extensions would break signing if placed incorrectly. > > You cannot place anything in the Firefox bundle. Any extensions, binary > or not, would need to be elsewhere. I don't know that we have a > supported global install location on Mac. > > --BDS >
When you say not supported, does this mean you have no motivation or plans to allow extensions formerly dropped in Contents/MacOS/extensions/ to be placed in a different location that doesn't require resigning? I suspect this means enterprise administrators will need to resign if they want to install Firefox on many machines and provide preinstalled extensions? On a related matter, has Stephan's suspicion been confirmed that running the binary manually will not trigger gatekeeper and allow developers to run the app, with all extensions in obj/dist/Nightly.app/Contents/MacOS/extensions/ (where they end up with --enable-extensions) Thanks, Philipp _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
