How do we now access Components.classes in mozilla.cfg. i need it to add x509 cert to db
we are currently using this pattern in mozilla.cfg to add our cert to the db
var Cc = Components.classes; var Ci = Components.interfaces; var certdb = Cc[\"@mozilla.org/security/x509certdb;1\"].getService(Ci.nsIX509CertDB); cert1 = "the cert hash"; certdb.addCertFromBase64(cert1, \"C,C,C\", \"\");
with quantum this fails with "Components is not defined"
how do we do this moving forward? thanks
Ọ̀nà àbáyọ tí a yàn
What Firefox version is this about?
Is that a release version or a Firefox 60.2.x ESR version?
With the ESR version this should still work, but a Firefox 62 release executes the autoconfig.cfg file in a sandbox.
You can add this line to the autoconfig.js file to disable the sandbox in Firefox 62.
- pref("general.config.sandbox_enabled", false);
All Replies (3)
Ọ̀nà àbáyọ Tí a Yàn
What Firefox version is this about?
Is that a release version or a Firefox 60.2.x ESR version?
With the ESR version this should still work, but a Firefox 62 release executes the autoconfig.cfg file in a sandbox.
You can add this line to the autoconfig.js file to disable the sandbox in Firefox 62.
- pref("general.config.sandbox_enabled", false);
62.0.3
only change was to create autoconfig.js file and add sandbox_enabled line. thanks!
however, this function is imperative to our enterprise and we will need this in the future.
I do not know how long there will be support of this pref in Firefox release, so you may have to switch to Firefox ESR.
- Bug 1479857 - Add a preference (default off) for autoconfig sanboxing for first release
- after a couple of Releases nothing major has happened, we can remove the pref.
- If something goes wrong, it won't require a dot release to flip the pref to disable the sandboxing.
(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html)