My organization has an air-gapped development network in which we need to deploy an internally developed extension. We are attempting to do this via GPO with the latest version of Firefox ESR. We have been running into an issue where the extension is not being installed when the browser starts. After reviewing the distribution documentation for Firefox add-ons it appears that we have to submit the extension to be signed by Mozilla, the problem here is that our extension is on the air-gapped network and cannot be moved to an internet connected device per our clients policies.
I had read on this page page that Firefox ESR does allow unsigned extensions if you set `xpinstall.signatures.required` to `false` but that conflicts with the Add-on signing in Firefox support page that states: "Firefox Extended Support Release (ESR): Some versions allowed overrides, but most recent ESR releases also enforce signing."
So we appear to be at an impasse, we cannot have the extension signed and we are required to use the ESR version of Firefox (the Nightly and Developer versions are not allowed.) Is there anyway that we could selfsign the extension? Or bypass the requirement via GPO?
My organization has an air-gapped development network in which we need to deploy an internally developed extension. We are attempting to do this via GPO with the latest version of Firefox ESR. We have been running into an issue where the extension is not being installed when the browser starts. After reviewing the distribution documentation for Firefox add-ons it appears that we have to submit the extension to be signed by Mozilla, the problem here is that our extension is on the air-gapped network and cannot be moved to an internet connected device per our clients policies.
I had read on this [https://extensionworkshop.com/documentation/enterprise/enterprise-distribution/ page] page that Firefox ESR does allow unsigned extensions if you set `xpinstall.signatures.required` to `false` but that conflicts with [[Add-on signing in Firefox|the Add-on signing in Firefox]] support page that states: "Firefox Extended Support Release (ESR): Some versions allowed overrides, but most recent ESR releases also enforce signing."
So we appear to be at an impasse, we cannot have the extension signed and we are required to use the ESR version of Firefox (the Nightly and Developer versions are not allowed.) Is there anyway that we could selfsign the extension? Or bypass the requirement via GPO?
