News for hackers. Stuff that matters.
Re:Reverse Engineering My Coway Air Purifier to Ditch the Cloud by teaearlgraycold on Friday November 13, 2026 @03:04PM (#50488915)
People don’t understand things and act shocked when they learn apt and Steam packages are downloaded over HTTP. You only need encryption for private information. CA public keys are not that. But you do need verifiable signatures.
Re:Reverse Engineering My Coway Air Purifier to Ditch the Cloud by sippingabonedry on Friday November 13, 2026 @03:08PM (#50488957)
I partly blame Google and Mozilla for the HTTP hysteria.

You publicly demonize something long enough and otherwise intelligent people start believing HTTPS is an invisibility cloak or the Good Housekeeping seal of approval for the web.

Re:Reverse Engineering My Coway Air Purifier to Ditch the Cloud by notaproton on Friday November 13, 2026 @03:30PM (#50489208)
It kind of makes sense opsec wise when you are on a network with adversaries though.

1) Others knowing knowing exactly which package you are downloading could give them a very clear way to fingerprint and target services you are running

2) HTTPS could allow you to potentially reduce your risk surface in a case where there is a bug in Steam's signature checker itself and someone sends a crafted payload instead of game files. Server validation would have prevented that. This has actually happened with apt before: CVE-2019-3462.

Odds are small, but I believe in DiD. I could imagine an attacker with nothing better to do could get up to this on say, a Uni's network.

And before you come at me with I should be using a VPN to protect against these scenarios, I do that already. This is about HTTPS being a sane default when possible.

Re:Reverse Engineering My Coway Air Purifier to Ditch the Cloud by sippingabonedry on Friday November 13, 2026 @03:41PM (#50489347)
> fingerprint and target services

Or they could connect to the service.

> Server validation would have prevented that

No it wouldn't have. HTTPS does not ensure a server's contents are trustworthy.

> And before you come at me with I should be using a VPN to protect against these scenarios, I do that already

So you protect yourself from unlikely, irrelevant threats by... deliberately paying strangers to MiTM your traffic?

Re:Reverse Engineering My Coway Air Purifier to Ditch the Cloud by teaearlgraycold on Friday November 13, 2026 @03:51PM (#50489466)
But we're talking about an air filter, not a production server.
Re:Reverse Engineering My Coway Air Purifier to Ditch the Cloud by notaproton on Friday November 13, 2026 @03:58PM (#50489559)
I'm all for Air Filters using HTTP!

The default for package upgrades on PCs should be (and is on Ubnutu and Fedora) HTTPS as it reduces risk with minimal performance impact for most of the people.

Re:Reverse Engineering My Coway Air Purifier to Ditch the Cloud by cyphar on Saturday November 14, 2026 @01:49AM (#50494666)
While that is true in principle, there are loads of examples of update protocols where staunchly using HTTP led to security issues. Since you mentioned APT, CVE-2026-109518 was discovered recently but similarly bad issues were discovered a decade ago with CVE-2014-6273 and CVE-2016-1252 (which caused a lot of people to switch to apt-transport-https). There are probably even more -- being able to modify HTTP response headers being parsed by a privileged process is a much more powerful tool than you might expect.

When building update systems, while you shouldn't root your trust in PKI you should still use HTTPS to make attacks harder because even if your updates are signed there is still a lot of parsing going on before you get to the update payload. (Even better, you should use TUF to avoid reinventing insecure designs.)