Live data from Hacker News

HTTPS Everywhere will sunset in January 2023

eff.org

11–20 of 148 posts

Re: HTTPS Everywhere will sunset in January 2023

#11
post #5

That was a good extension for a specific time. I stopped using it about 5 years ago when everyone had been pushing HTTPS hard, and Let's Encrypt had become popular. I didn't notice any websites not using HTTPS, so I didn't look back.

http://neverssl.com remains for those badly-setup wifi networks.

Cool, they even generate subdomains dynamically to avoid caching

Re: HTTPS Everywhere will sunset in January 2023

#12

That was a good extension for a specific time. I stopped using it about 5 years ago when everyone had been pushing HTTPS hard, and Let's Encrypt had become popular. I didn't notice any websites not using HTTPS, so I didn't look back.

One website not supporting HTTPS which caught my eye is http://paulgraham.com/

Re: HTTPS Everywhere will sunset in January 2023

#13
post #9

There's a piece of animation software that I use in my game development called Spine, and it's truly fantastic and the developers and staff are great... but the PHPBB forums don't have https enabled. I've brought it up on these same forums[0] but I don't think they get why https is an important thing to turn on, even in 2022. Turning on https mode in my browser brings up, as it should, a large error message saying th…

Not only do the forums have HTTPS disabled, but they expect you to download executables to run on your computer over HTTP. And, the kicker: they already have a legit HTTPS cert for the entire site: visiting on HTTPS redirects you to HTTP _facepalm_.

Never heard of Spine before your comment, but if I found this in the wild I'd assume it was amateur hour and turn back immediately.

Re: HTTPS Everywhere will sunset in January 2023

#14
post #9

There's a piece of animation software that I use in my game development called Spine, and it's truly fantastic and the developers and staff are great... but the PHPBB forums don't have https enabled. I've brought it up on these same forums[0] but I don't think they get why https is an important thing to turn on, even in 2022. Turning on https mode in my browser brings up, as it should, a large error message saying th…

> Turning on https mode in my browser brings up, as it should, a large error message saying that the site is insecure. I can't imagine that's a terribly good first impression, even though, again, Spine is one of the best animation packages out there.

A site being on HTTP isn't necessarily insecure. That warning is inaccurate. It's more about creating censors and gatekeepers in the form of certificate authorities.

(Debian packages are still served over HTTP and are secure with no certificate authority. Try to figure that out!)

Re: HTTPS Everywhere will sunset in January 2023

#15
Interesting. Just a couple hours ago, I was reading their post (2016) on how they were sunsetting their canary watch program, saying that it had achieved the goals they had set out on for it (internally, my knee-jerk reaction was "...what?").

Of course, I'm not as incredulous this time around over HTTPS Everywhere.

https://www.eff.org/deeplinks/2016/05/canary-watch-one-year-...

Re: HTTPS Everywhere will sunset in January 2023

#16
post #9

There's a piece of animation software that I use in my game development called Spine, and it's truly fantastic and the developers and staff are great... but the PHPBB forums don't have https enabled. I've brought it up on these same forums[0] but I don't think they get why https is an important thing to turn on, even in 2022. Turning on https mode in my browser brings up, as it should, a large error message saying th…

> Turning on https mode in my browser brings up, as it should, a large error message saying that the site is insecure. I can't imagine that's a terribly good first impression, even though, again, Spine is one of the best animation packages out there. A site being on HTTP isn't necessarily insecure. That warning is inaccurate. It's more about creating censors and gatekeepers in the form of certificate authorities. (De…

Debian packages are verified via a separate mechanism after download. The only verification method included in your web browser is HTTPS.

Re: HTTPS Everywhere will sunset in January 2023

#17
post #9

There's a piece of animation software that I use in my game development called Spine, and it's truly fantastic and the developers and staff are great... but the PHPBB forums don't have https enabled. I've brought it up on these same forums[0] but I don't think they get why https is an important thing to turn on, even in 2022. Turning on https mode in my browser brings up, as it should, a large error message saying th…

> Turning on https mode in my browser brings up, as it should, a large error message saying that the site is insecure. I can't imagine that's a terribly good first impression, even though, again, Spine is one of the best animation packages out there. A site being on HTTP isn't necessarily insecure. That warning is inaccurate. It's more about creating censors and gatekeepers in the form of certificate authorities. (De…

Debian ships with its own signing keys to authenticate the packages that it downloads. They are acting as their own CA.

This isn't scalable to the web.

Re: HTTPS Everywhere will sunset in January 2023

#18

Earlier quoted context omitted.

> Turning on https mode in my browser brings up, as it should, a large error message saying that the site is insecure. I can't imagine that's a terribly good first impression, even though, again, Spine is one of the best animation packages out there. A site being on HTTP isn't necessarily insecure. That warning is inaccurate. It's more about creating censors and gatekeepers in the form of certificate authorities. (De…

Debian ships with its own signing keys to authenticate the packages that it downloads. They are acting as their own CA. This isn't scalable to the web.

Whether or not it's scalable is orthogonal to the question. A browser would call Debian's repos insecure despite the fact that they are secure by other means.

vv: whether it's authenticated by TLS or PGP is literally isomorphic except one is centralized to CAs and one is decentralized with web of trust. That's the only difference.

Re: HTTPS Everywhere will sunset in January 2023

#19
post #9

There's a piece of animation software that I use in my game development called Spine, and it's truly fantastic and the developers and staff are great... but the PHPBB forums don't have https enabled. I've brought it up on these same forums[0] but I don't think they get why https is an important thing to turn on, even in 2022. Turning on https mode in my browser brings up, as it should, a large error message saying th…

Not only do the forums have HTTPS disabled, but they expect you to download executables to run on your computer over HTTP. And, the kicker: they already have a legit HTTPS cert for the entire site: visiting on HTTPS redirects you to HTTP _facepalm_. Never heard of Spine before your comment, but if I found this in the wild I'd assume it was amateur hour and turn back immediately.

A slight correction here, the download of the exe does take place over https. As does buying the software, and signing up to the forums. But everything else doesn't?

The software itself is some of the smoothest and most stable I've ever used. And when there's an update within the software that, as far as I'm aware, takes place over https too.

But the rest of the site and forums, even when signed in, is http, and I don't really know why.

Re: HTTPS Everywhere will sunset in January 2023

#20

Earlier quoted context omitted.

Debian ships with its own signing keys to authenticate the packages that it downloads. They are acting as their own CA. This isn't scalable to the web.

Whether or not it's scalable is orthogonal to the question. A browser would call Debian's repos insecure despite the fact that they are secure by other means. vv: whether it's authenticated by TLS or PGP is literally isomorphic except one is centralized to CAs and one is decentralized with web of trust. That's the only difference.

Because they are. Your web browser has no way to validate the authenticity of any content served by a Debian mirror. This is very much done that way because anyone can run a Debian mirror (or indeed a mirror for almost any distribution, which all authenticate their packages in a similar manner).

Nothing stops an admin running a repository mirror from choosing to make it serve malicious content, so the downloads need to be authenticated out of band. This is the very definition of insecure.

Post reply on HN