GNOME's Epiphany 3.23.3 Web Browser Disables HTTPS Everywhere By Default

[phoronix]

Phoronix: GNOME's Epiphany 3.23.3 Web Browser Disables HTTPS Everywhere By Default

Epiphany 3.23.3 was tagged on Monday as the newest development release of this web-browser update being aligned for GNOME 3.24...

http://www.phoronix.com/scan.php?page=news_item&px=GNOME-Epiphany-3.23.3

[uid313]

The good thing about Epiphany is that it supports Wayland, something that Chromium and Firefox does not yet do.

Does it have support for adding extensions?
Does it have developer tools?

[geearf]

it supports Wayland, something that Chromium does not yet do.

hmmmmmm:

https://www.phoronix.com/scan.php?page=news_item&px=Google-Chrome-50

[FireBurn]

That title is a bit misleading, make it sound like HTTPS has been disabled everywhere in the browser

[Palu Macil]

FireBurn True, but it's the actual name of the technology, so there might not be a better wording.

[Palu Macil]

geearf In that thread, people mentioned that despite Chrome support for Wayland, a Mutter issue prevents it from running under anything but XWayland, so if that hasn't been fixed, there is still effectively not great support.

[Las_]

Palu Macil The proper solution would be to not capitalise every word, and only capitalise names. So: GNOME's Epiphany 3.23.3 web browser disables HTTPS Everywhere by default.

[marciosr]

Palu Macil The proper solution would be to not capitalise every word, and only capitalise names. So: GNOME's Epiphany 3.23.3 web browser disables HTTPS Everywhere by default.

Or, better in my opinion: GNOME's Epiphany 3.23.3 web browser disables "HTTPS Everywhere" by default.

[s_j_newbury]

geearf In that thread, people mentioned that despite Chrome support for Wayland, a Mutter issue prevents it from running under anything but XWayland, so if that hasn't been fixed, there is still effectively not great support.

That's not the real issue. Chromium/Ozone/Wayland is an embedded browser, not a desktop product. It has no DE integration at all, no-gtk2/3 UX like the normal Chrome/Chromium browser. Of course it would be great if somebody could build a full desktop browser with it. The core Google/Chrome devs don't seem to be too interested in supporting the Wayland Linux Desktop, they won't even support VAAPI on the X11 Linux Desktop even though it shares virtually all its code with ChromeOS, so I guess we shouldn't be surprised. Windows, ChromeOS, and Android are the main targets they care about.

[droidhacker]

This "https everywhere" thing is cute, but CAN NOT actually work.
The first big problem, is that the CONTENT of a site doesn't necessarily match between their HTTP and HTTPS.
And this one problem is a deal breaker.
Until the site has actually matched up the content, its a non-starter. And once they HAVE, "https everywhere" really becomes redundant, since the server will (or at least should) set a permanent redirect.

Frankly, though, I find the "force all the internet to https" to be a massive and redundant overhead. Crypto really should be restricted to things that are security sensitive. Not static public content.