Re:Extensions in Firefox 59
by xg15 on Saturday January 27, 2018 @03:56PM
(#16248047)
Thank you very much for the contribution. The decentralized web projects sound really exciting and it's awesome to see support from Mozilla.
However, I find the concept of the scheme whitelist pretty strange in context of WebExtensions.
Of course it makes sense that http:, https:, data:, blob:, etc should be off-limits for extensions. But on the other hand, I'd think that the primary use-case of registering protocol handlers in extensions is to handle existing links - something that the ext+/web+ rule seems to be particularly designed to disallow.
Apparently, the actual handler whitelist for WebExtensions can be found at [1]. It looks pretty... arbitrary?
For example, it's amazing to see that magnet: irc:, ssh: and gopher: are on there, but then why not ftp:, ws: or even steam:? There could be some useful extensions intercepting those as well.
Likewise, while the inclusion of scuttlebutt, ipfs etc is very good news, what makes them eligible now that didn't make them earlier?
Generally, I'd like to know by what process is that whitelist managed and what are the criteria to get on there.
(I understand it's derived from the official HTML5 whitelist [2]. To be honest, that one looks even more arbitrary - but of course has different security considerations, as it defines an API for the open web. The two lists also seem to have some differences, as e.g. gopher: isn't on the HTML5 whitelist while openpgp4fpr: is not on the extensions list.)
However, I find the concept of the scheme whitelist pretty strange in context of WebExtensions.
Of course it makes sense that http:, https:, data:, blob:, etc should be off-limits for extensions. But on the other hand, I'd think that the primary use-case of registering protocol handlers in extensions is to handle existing links - something that the ext+/web+ rule seems to be particularly designed to disallow.
Apparently, the actual handler whitelist for WebExtensions can be found at [1]. It looks pretty... arbitrary?
For example, it's amazing to see that magnet: irc:, ssh: and gopher: are on there, but then why not ftp:, ws: or even steam:? There could be some useful extensions intercepting those as well.
Likewise, while the inclusion of scuttlebutt, ipfs etc is very good news, what makes them eligible now that didn't make them earlier?
Generally, I'd like to know by what process is that whitelist managed and what are the criteria to get on there.
(I understand it's derived from the official HTML5 whitelist [2]. To be honest, that one looks even more arbitrary - but of course has different security considerations, as it defines an API for the open web. The two lists also seem to have some differences, as e.g. gopher: isn't on the HTML5 whitelist while openpgp4fpr: is not on the extensions list.)
[1] https://developer.mozilla.org/en-US/Add-ons/WebExtensions/ma...
[2] https://html.spec.whatwg.org/multipage/system-state.html#cus...