Page 1 of 1

New built in HTTPS Enforcment vs HTTPSEverywhere

Posted: Thu Dec 18, 2014 3:04 pm
by MajinXES
Hello!

While studying the release notes of V. 2.6.9.8 of NoScript I noticed an awesome and new little feature that came with it. Namely the "Built-in HTTPS enforcement list, seeded with www.youtube.com.

Since I'm also using the HTTPSEverywhere-Addon for Firefox (https://www.eff.org/https-everywhere) I wondered if this "new" feature makes HTTPSEverywhere obsolete and if i can deinstall the AddOn? I mean, why using two AddOns for the same purpose and let them slow down my computer (FF).

I really hope you can help me with this simple and maybe noobish question.

Thanks in advance! :)

MajinXES

Re: New built in HTTPS Enforcment vs HTTPSEverywhere

Posted: Thu Dec 18, 2014 8:29 pm
by Giorgio Maone
No, the built-in list is meant to fix incompatibility problems, rather than providing best-effort encryption on most popular websites, which is HTTPSEverywhere's mission.
Simply, I don't have the manpower to perform the necessary editorial work to maintain a general list.

Re: New built in HTTPS Enforcment vs HTTPSEverywhere

Posted: Thu Dec 18, 2014 9:38 pm
by MajinXES
No worries Giorgio!
It was my bad misunderstanding the release notes and not your's not having the manpower to maintain a general list. You do enough keeping NS uptodate. :)

Thanks for your fast and helpful reply btw. I just stay with HTTPSEverywhere and NoScript then ^^
:)

MajinXES

Re: New built in HTTPS Enforcment vs HTTPSEverywhere

Posted: Fri Dec 19, 2014 12:25 am
by Thrawn
Also, HTTPS Everywhere stores its rules as an SQLite database, which is a format NoScript doesn't use anywhere else, so it would be non-trivial (though theoretically possible) for NoScript to make use of the HTTPS Everywhere ruleset.

Re: New built in HTTPS Enforcment vs HTTPSEverywhere

Posted: Fri Dec 26, 2014 10:08 pm
by dhouwn
HTTPS Everywhere also allows for much more advanced rules, like redirection to a different subdomain.