News for hackers. Stuff that matters.
Re:Chrome will mark all HTTP sites as ‘not secure’ starting ... by Klathmon on Wednesday July 11, 2018 @03:15PM (#17509511)
doesn't that just push the "authority" to DNS. You still need someone to vouch that you are who you say you are.
Re:Chrome will mark all HTTP sites as ‘not secure’ starting ... by lphnull on Wednesday July 11, 2018 @03:45PM (#17509747)
I'd prefer a wild-west type of world where certs are decentralized and "blind trust" towards big authorities becomes optional and still there as a reinforcement, but not necessary and definitely not required to communicate securely.

I mean- if there are adversaries out there trying to hack our communications- then we need to let these adversaries try so that we can engage them head on so that their methods become published, public, and thoroughly analyzed by the people in charge of strengthening our protocols.

This approach would be like fracturing the bone to make it stronger- we allow nation state hack us in order to figure out ways to stop and prevent such hacks using open and transparent software alone. Trusting any group of people anywhere "just because they're trust worthy" feels like a variable defining <the contents of its data> as equal to <the contents of its data>. It just doesn't make sense for a variable to trust itself "just because" because then I wonder if something fishy is going on under the hood.

Re:Chrome will mark all HTTP sites as ‘not secure’ starting ... by foepys on Wednesday July 11, 2018 @03:50PM (#17509791)
That's exactly what you don't want if you can't trust your ISP.
Re:Chrome will mark all HTTP sites as ‘not secure’ starting ... by yjftsjthsd-h on Wednesday July 11, 2018 @04:03PM (#17509880)
Well, yeah. You need to trust someone. And if you aren't willing to centralize, then you're left with key signing parties.
Re:Chrome will mark all HTTP sites as ‘not secure’ starting ... by vbezhenar on Wednesday July 11, 2018 @05:11PM (#17510318)
DNS is a natural source for trust. We need secure DNS for a sane internet anyway. DNS has hierarchical structure which naturally maps to certificate hierarchy.
Re:Chrome will mark all HTTP sites as ‘not secure’ starting ... by AFNobody on Wednesday July 11, 2018 @05:25PM (#17510413)
If a hostile controls a DNS server, you are hosed anyway.
Re:Chrome will mark all HTTP sites as ‘not secure’ starting ... by AgentME on Wednesday July 11, 2018 @07:17PM (#17510993)
If the sites you care about are using HSTS (and they're in the HSTS preload list, or you've visited them before from this device), then the worst the attacker can do is deny you from accessing them.
Re:Chrome will mark all HTTP sites as ‘not secure’ starting ... by AFNobody on Thursday July 12, 2018 @09:32PM (#17519917)
HSTS depends on DNS and NTP.