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.
As far as I understand, the functionality could be done now under iOS with the make-https action as noticed here.
Can we have any comment from the devs about that?
The make-https action is now available for iOS content blockers.
Just above that, it also says:
You can now create macOS-native Safari app extensions to sell and distribute in the App Store. Content Blockers for iOS can be easily ported to macOS. [Emphasis mine.]
I’m contacting you about your HTTPS Everywhere extension. You wrote in
your FAQ : « if you happen to know a way to perform secure request
rewriting in [Safari], feel free to let us know »
Well, there is now a way. In May 2016, Safari Content Blocking API has
been improved to be able to force HTTPS when available. It was then
tested in Safari Developer Preview. Eventually, the feature became
available to everyone in Safari 10 (iOS and macOS).
Have you tried this ? Are you planning on a Safari version of HTTPS
everywhere ?
So it seems the answer is that it seems possible for at least the trivial rulesets. I'd have to investigate if it is possible for more complicated rulesets.
I tried to get a safari extension built with the new content-blocker action, but I have never tried to build a safari extension before and I could not get it to work. :(
I have it working locally. There are some other limitations: 1) New safari extensions need to be packaged with a native app, and I don't have that working yet. 2) This will only work with simple rules. It will not work for rewriting to different hosts, which is pretty common in HTTPS Everywhere. 3) It does nothing for secure cookies. 4) I don't have a developer account so my local extension cannot be distributed. But once I get a download-and-install version working I'll put up a github project for everyone.
I really wish Apple would just implement such functionality themselves if they aren’t willing to open up the API enough. This sort of feature is helpful for literally anyone using Safari, and Apple could easily fork HTTPS Everywhere and do this themselves.
@edlebert@Saklad5 you should probably create 2 issues (one for the redirection rules, one for the secure cookies) at https://bugreport.apple.com to let Apple know of the required functionality. It doesn't mean they will abide by your request, but at least they will know there is a functional need. ;-)
I've been working on an iOS app version of HTTPS everywhere. For doing so I've created this script which processes the rulesets to extract a list of hosts that just require a 'simple' redirect: https://gist.github.com/bouk/bc4b1f406c3d4e83d28ade3f1b18a4e0
Which also supports more than the 50k rule limit, it seems there is no limit on the number in if-domain.
It would be good to hunt down overly complicated rulesets, essentially everything generated by make-trivial-rule is supported while others can't be guaranteed
Reacted by Viktor Szakats, Caio Bianchi and Jesse Squires
@Revod unfortunately, after legal review we found the Apple Developer License Agreement contains provisos that EFF is unable to comply with. This is for reasons similar to what we stated in this 2014 blog post.
We don't want to encourage others to sign the agreement. Third party implementations of HTTPS Everywhere using our rulesets certainly don't run afoul of our licensing of the project, but there's a caveat.
I'm not a lawyer, but my understanding is that Apple enforces restrictions on redistribution via its Licensing Agreement. So posting the project on the Safari store seems to be a violation of the GPL. So it seems that any contributor who had code merged under the GPL could appeal it's listing in the Safari store. This is an unfortunate outcome of being licensed restrictively, and this has been done in the past.
So I'm not a licensing expert, but I think if anyone chose to list HTTPS Everywhere in the Safari store it would be on shaky grounds.
Reacted by Ernesto Graterol, Håvard Pedersen, Brandon Harshe and Jérôme Bertaux
Since the only part of the of the iOS app that would require GPL licensing is the ruleset, which is essentially just a .txt file with a list of hosts, it might be possible to make that file accessible and redistributable from the app, and license the rest of the app under Mozilla Public License. It seems that this would mean that people can redistribute the GPL-licensed part of the app as much as they want. The question is of course whether that's legally sound, or whether having that list of hosts be GPL-licensed means that the whole app needs to be GPL, which we would need legal advice on.
I think I will proceed with that plan, and we'll just see what happens.
Reacted by Ernesto Graterol, Håvard Pedersen, Jeremy Saklad, Brandon Harshe and Alexander
@bouk Something that may be helpful here: the way I understand it, the stipulations of the GPL are such that the restrictiveness only applies to code which is included in the same program. This differs from, say, the AGPL, which extends to network interaction. So here's what may interest you:
We plan on delivering the rulesets out-of-band of the extension itself, making it available on the web (along with a signature), so that the mainline HTTPS Everywhere extension as well as any third-party can download and apply these rules. If an iOS extension were to be developed, it could pull in the rulesets (which have been pre-compiled and provided on a webserver) at runtime, and not run afoul of the GPL.
I have a build up on testflight, please email my at the email on my GitHub profile if you would like to give it a shot.
Reacted by Stephen Edgar, Alexander, Caio Bianchi, Demian, Ernesto Graterol, kalin, Olivier Simard-Casanova, Viktor Szakats, a base, William Budington and 2 more
Reacted by Tereza Tomcova, Viktor Szakats, Stephen Edgar, Daenney, Caio Bianchi, William Budington, Adam, a base, Andrew Sun, Kristian Pennacchia and 6 more
I guess this is ok to close since EFF already said they can't enter a required contract with Apple, and there will be no official version of HTTPS Everywhere for Apple.
Activity
J0WI commentedon Jun 23, 2016
Is this also for iOS Safari?
jellyfishcoder commentedon Jun 23, 2016
@J0WI, not yet, still only content blockers for ios, but it looks like extensions may be a future possibility.
heubergen commentedon Sep 18, 2016
As far as I understand, the functionality could be done now under iOS with the make-https action as noticed here.
Can we have any comment from the devs about that?
dato commentedon Sep 21, 2016
In particular, the above linked What’s New in Safair 10.0 says:
Just above that, it also says:
Thanks in advance for investigating!
Saklad5 commentedon Nov 15, 2016
Could we have an answer as to the feasibility of HTTPS Everywhere using this new API?
Hainish commentedon Nov 24, 2016
Related, this from email to our info@eff.org:
So it seems the answer is that it seems possible for at least the trivial rulesets. I'd have to investigate if it is possible for more complicated rulesets.
Saklad5 commentedon Nov 25, 2016
Even just the trivial rulesets would be better than nothing, right?
CaioBianchi commentedon Dec 23, 2016
Any follow-up on this?
edlebert commentedon Dec 30, 2016
I tried to get a safari extension built with the new content-blocker action, but I have never tried to build a safari extension before and I could not get it to work. :(
javabean commentedon Dec 30, 2016
Should you want to play with a Safari Content Blocker Extension, you may want to start with the simple, no-frill https://github.com/krishkumar/BlockParty
A more advanced one (and probably overkill for research): https://github.com/AdguardTeam/AdguardForiOS
edlebert commentedon Dec 31, 2016
I have it working locally. There are some other limitations: 1) New safari extensions need to be packaged with a native app, and I don't have that working yet. 2) This will only work with simple rules. It will not work for rewriting to different hosts, which is pretty common in HTTPS Everywhere. 3) It does nothing for secure cookies. 4) I don't have a developer account so my local extension cannot be distributed. But once I get a download-and-install version working I'll put up a github project for everyone.
Saklad5 commentedon Dec 31, 2016
Thanks for the attempt, despite the caveats.
I really wish Apple would just implement such functionality themselves if they aren’t willing to open up the API enough. This sort of feature is helpful for literally anyone using Safari, and Apple could easily fork HTTPS Everywhere and do this themselves.
javabean commentedon Jan 1, 2017
@edlebert @Saklad5 you should probably create 2 issues (one for the redirection rules, one for the secure cookies) at https://bugreport.apple.com to let Apple know of the required functionality. It doesn't mean they will abide by your request, but at least they will know there is a functional need. ;-)
CaioBianchi commentedon Jan 11, 2017
Webkit shipped Safari TP21 today: https://webkit.org/blog/7265/release-notes-for-safari-technology-preview-21/
Bugfix (?):
https://trac.webkit.org/changeset/209821
19 remaining items
bouk commentedon Nov 3, 2017
Hi everyone
I've been working on an iOS app version of HTTPS everywhere. For doing so I've created this script which processes the rulesets to extract a list of hosts that just require a 'simple' redirect: https://gist.github.com/bouk/bc4b1f406c3d4e83d28ade3f1b18a4e0
This list can then be inserted into a rule like
[ { "action": { "type": "make-https" }, "trigger": { "url-filter": ".*", "if-domain": [ "*3cdn.net", "*3scale.net", etc. } ]Which also supports more than the 50k rule limit, it seems there is no limit on the number in
if-domain.It would be good to hunt down overly complicated rulesets, essentially everything generated by
make-trivial-ruleis supported while others can't be guaranteedSaklad5 commentedon Nov 3, 2017
@bouk That’s great! Safari’s content blockers are platform-agnostic as I understand it, so that will work on the Mac too!
Revod commentedon Nov 9, 2017
Any news/updates about this?
Hainish commentedon Nov 9, 2017
@Revod unfortunately, after legal review we found the Apple Developer License Agreement contains provisos that EFF is unable to comply with. This is for reasons similar to what we stated in this 2014 blog post.
We don't want to encourage others to sign the agreement. Third party implementations of HTTPS Everywhere using our rulesets certainly don't run afoul of our licensing of the project, but there's a caveat.
I'm not a lawyer, but my understanding is that Apple enforces restrictions on redistribution via its Licensing Agreement. So posting the project on the Safari store seems to be a violation of the GPL. So it seems that any contributor who had code merged under the GPL could appeal it's listing in the Safari store. This is an unfortunate outcome of being licensed restrictively, and this has been done in the past.
So I'm not a licensing expert, but I think if anyone chose to list HTTPS Everywhere in the Safari store it would be on shaky grounds.
bouk commentedon Nov 13, 2017
@Hainish thank you for the reply.
Since the only part of the of the iOS app that would require GPL licensing is the ruleset, which is essentially just a .txt file with a list of hosts, it might be possible to make that file accessible and redistributable from the app, and license the rest of the app under Mozilla Public License. It seems that this would mean that people can redistribute the GPL-licensed part of the app as much as they want. The question is of course whether that's legally sound, or whether having that list of hosts be GPL-licensed means that the whole app needs to be GPL, which we would need legal advice on.
I think I will proceed with that plan, and we'll just see what happens.
Hainish commentedon Nov 16, 2017
@bouk Something that may be helpful here: the way I understand it, the stipulations of the GPL are such that the restrictiveness only applies to code which is included in the same program. This differs from, say, the AGPL, which extends to network interaction. So here's what may interest you:
We plan on delivering the rulesets out-of-band of the extension itself, making it available on the web (along with a signature), so that the mainline HTTPS Everywhere extension as well as any third-party can download and apply these rules. If an iOS extension were to be developed, it could pull in the rulesets (which have been pre-compiled and provided on a webserver) at runtime, and not run afoul of the GPL.
Hainish commentedon Nov 16, 2017
@Chris1000 unfortunately it won't be in the same format as iOS content blockers.
bouk commentedon Nov 21, 2017
I have a working app now, the source code can be found here: https://github.com/bouk/HTTPS4All
This is the tool I use to convert the rules into a hosts list: https://github.com/bouk/https-everywhere-host-list. This is the uploaded to https://hosts.https4all.org/hosts.txt, which the app downloads every time it's opened.
I have a build up on testflight, please email my at the email on my GitHub profile if you would like to give it a shot.
bouk commentedon Jan 7, 2018
Hey everyone, just an update. I’ve released the iOS version, and you can now download it here: https://itunes.apple.com/gb/app/https4all/id1305430042?mt=8
wryanthomas commentedon Jan 29, 2018
Thanks 'bouk'. That's awesome.
Anyone know of (similar) progress on a Safari for Mac extension?
pipboy96 commentedon Mar 26, 2019
bouk commentedon Mar 26, 2019
pipboy96 commentedon Mar 28, 2019
I guess this is ok to close since EFF already said they can't enter a required contract with Apple, and there will be no official version of HTTPS Everywhere for Apple.
fuzzy76 commentedon Sep 3, 2020
How about the new webextension support in Safari 14? Source: https://9to5mac.com/2020/06/24/apple-adds-webp-hdr-support-and-more-to-safari-with-ios-14-and-macos-big-sur/