4 ms·
How do you do this without leaking your code to mozilla?
by funklebunkle 8y ago
How do you do this without leaking your code to mozilla?
- Vinnl 8y agoI don't think you can have Mozilla sign it without letting them see the code.
- idle_zealot 8y agoOut of curiosity, under what circumstances would you consider distributing an extension bundle to be leaking its code? Unless I'm misunderstanding, isn't this the same file you'll be distributing to your users? At first bluff it seems similar to worrying about leaking your website's frontend (I've got news for you...).
- tomp 8y agoIt could be a private extension developed by a company internally, and only distributed to internal users.
- earenndil 8y agoIf it's for an entire company, then it's easy enough to compile your own copy of firefox that accepts extensions signed with the company signature rather than mozilla.
- funklebunkle 8y agoIt's really not. Small businesses exist.
- earenndil 8y agoIf you have the resources to develop an internal company addon, you have the resources to build a firefox that accepts a different signature.
- jamietanna 8y agoRespectfully disagree - having to rebuild each time patches come out, on multiple OSes and versions, which have a patch to allow unsigned extensions is a massively more time expensive than developing a browser extension, and requires extra knowledge on the behalf of the persons responsible
- Vinnl 8y agoLuckily it's not necessary: you can still enable a flag in ESR releases that allow installation of unsigned add-ons, so that solves it for company-internal tools.
- uremog 8y agooff-topic: the phrase is, "at first blush"
- MisterAV 8y agoAren't extension written in Javascript? Then the source is always visible to users.
- derimagia 8y agoThey are referring to an internal company tool
- ghostly_s 8y ago"Leaking your code to mozilla"? What do you think they are going to do with it?