Re:Towards HTTPS by Default
by NegativeK on Wednesday August 16, 2023 @04:41PM
(#37153494)
I consider managing a CA at home to be a _much_ bigger security risk than having HTTP traffic on my home LAN.
[ Parent
| on HN ]
Re:Towards HTTPS by Default
by janosdebugs on Wednesday August 16, 2023 @04:52PM
(#37153650)
That may be so, but I from the perspective of a few billion people using Chrome, the percentage of people that need to and should access something on the local network without encryption is probably a few magnitudes smaller than the same audience on Hacker News.
Re:Towards HTTPS by Default
by ownagefool on Wednesday August 16, 2023 @04:50PM
(#37153609)
This doesn't make sense unless you use the CA for something in addition / more critical for HTTP.
Sure, you could leak said CA, but it's only going to leave you in the same position as HTTP.
You can generate CA certs that are only allowed to sign certs for specific domains, but _nothing_ respects that self limitation.
That means that if the CA keys get out, someone could use it to sign their own cert for google.com, [mybank].com, or [mypasswordmanager].com. Every device with my CA cert on it will trust those.
Re:Towards HTTPS by Default
by ownagefool on Thursday August 17, 2023 @08:38AM
(#37160644)
That's a fair point.
Re:Towards HTTPS by Default
by GoblinSlayer on Thursday August 17, 2023 @08:39AM
(#37160653)
Sign a certificate expiring in 2070 and delete the CA key. That's all management you need. And if anyone has access to your disk, it's much easier for them to add you their CA certificate than search for your CA key.