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.)
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.)