Re:Chrome 68 will mark all HTTP sites as “not secure”
by dcow on Friday February 09, 2018 @07:58AM
(#16339834)
Pre-shared keys are only good for bootstrapping a stronger trust relationship. You could use TLS-SRP to exchange identities and then mutually authenticate each other for the general case. X509 is not the problem. Centrally manager trust hierarchies are.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by collinmanderson on Friday February 09, 2018 @08:10AM
(#16339891)
I’d rather see an ssh-style ask once and then trust forever after that.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by kernelPan1c on Friday February 09, 2018 @03:53PM
(#16343734)
Isn't this just key pinning? I'd like to see a P2P system. This way governments can't force CA's to allow MITM.
In simple terms it allows you to setup a TLS session by both sides proving they know the secret password, without either side exposing it, thus MITM is unable to capture it, it is an alternative to the cert model that works very well for network local devices.
But of course Chrome and firefox both have zero interest in supporting this use case despite TLS-SRP kicking around for ages now, they'd much rather have you connect to your own devices via a mediated cloud gateway server, for your own safety of course.