You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Try implementing HTTPS Everywhere using WebExtensions #2640
We have a long lead time before XPCOM is deprecated, and there are some big issues to solve, like how to make SSL Observatory work in such a world (probably we need Mozilla to implement some extra APIs).
We should try implementing HTTPS Everywhere using the new API, to see if it is possible. Probably starting from the Chromium code rather than the existing Firefox code makes the most sense.
I was wondering whether SSL Observatory is coming to Chrome or disappearing from Firefox too at #1681 (comment) and I was linked here after asking at OFTC and this issue answers my question.
We have a long lead time before XPCOM is deprecated, and there are some big issues to solve, like how to make SSL Observatory work in such a world (probably we need Mozilla to implement some extra APIs).
So I took a cursory look here, and it'll be surprisingly easy to adapt the Chrome code to support the new WebExtensions model, and move to one unified extension codebase.
@semenko Can you explain why in detail that we won't be able to have the SSL Observatory? I saw and read the links, but I don't understand what you're referring to.
No APIs exist, that I'm aware of, that allow for access to TLS data in Chrome (or in the WebExtension model in Firefox).
The Chrome dev team also announced that they won't be adding any new APIs to support accessing TLS info. (You can probably find a bug somewhere at https://crbug.com)
@semenko Well, that sucks. I wonder what purpose they have of not allowing TLS? Wouldn't it just make it more secure? Chrome isn't exactly the most secure or private browser, so you would think they would want to improve it when they can...
I'm closing this for now, we can reopen a separate issue for building the SSL Observatory into the WebExtensions codebase if the APIs become available at some point.
Activity
Mikaela commentedon Sep 12, 2015
I was wondering whether SSL Observatory is coming to Chrome or disappearing from Firefox too at #1681 (comment) and I was linked here after asking at OFTC and this issue answers my question.
Would Proposal: native.js to “embrace & extend” the WebExtensions API help if Mozilla implements it?
semenko commentedon Jan 22, 2016
So I took a cursory look here, and it'll be surprisingly easy to adapt the Chrome code to support the new WebExtensions model, and move to one unified extension codebase.
There's great documentation here: https://developer.mozilla.org/en-US/Add-ons/WebExtensions
And some issues to look at here: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Chrome_incompatibilities
As of now, it looks like:
DerekTurtleRoe commentedon Feb 21, 2016
@semenko Can you explain why in detail that we won't be able to have the SSL Observatory? I saw and read the links, but I don't understand what you're referring to.
semenko commentedon Feb 21, 2016
No APIs exist, that I'm aware of, that allow for access to TLS data in Chrome (or in the WebExtension model in Firefox).
The Chrome dev team also announced that they won't be adding any new APIs to support accessing TLS info. (You can probably find a bug somewhere at https://crbug.com)
DerekTurtleRoe commentedon Feb 21, 2016
@semenko Well, that sucks. I wonder what purpose they have of not allowing TLS? Wouldn't it just make it more secure? Chrome isn't exactly the most secure or private browser, so you would think they would want to improve it when they can...
Hainish commentedon Oct 11, 2016
I'm closing this for now, we can reopen a separate issue for building the SSL Observatory into the WebExtensions codebase if the APIs become available at some point.
Hainish commentedon Oct 11, 2016
Thanks for all your work on this @semenko !