4 ms·
If that's your threat model, the cited add-on is MIT licensed so you can generate an id of your own <https://github.com/kintesh/containerise/blob/3.9.0/src/mani
by mdaniel 2y ago
If that's your threat model, the cited add-on is MIT licensed so you can generate an id of your own <https://github.com/kintesh/containerise/blob/3.9.0/src/manifest.json#L30 https://github.com/kintesh/containerise/blob/3.9.0/src/manif...> and publish it for yourself, thus controlling its update and ownership lineage
I agree it would be better if one could just install the .xpi from a server you trust but Mozilla hates its users so here we are
- amelius 2y agoI think add-ons are an added complexity that needlessly increases the attack surface. I'd rather not use them, just like some people don't like to use Javascript. I have a bunch of bookmarklets that do everything I want. Something as essential as managing containers should imho be fixed at the browser level, not by an add-on. I don't like it when essential security features are bolted on top of software as an afterthought.
- d3Xt3r 2y agoDo you have a git repo or something for the bookmarklets you use? I haven't used a single bookmarklet in like a decade so I'm curious what you still use them for.
- amelius 2y agoI use them to automate some stuff on niche websites I use, for pure convenience. I don't have them in a git repo, they all live in my bookmarks bar. Note: it's quite easy to create them using chatgpt, nowadays (of course you have to check them before using).