2 ms·
How does this work when a user is visiting https://bank.example https://bank.example for the first time? Are we supposed to let granny eat the risk of a MITM wh
by gruez 2y ago
How does this work when a user is visiting https://bank.example https://bank.example for the first time? Are we supposed to let granny eat the risk of a MITM when she gets a new device? Furthermore, how is such a system supposed to work in private browsing? You either have to introduce a fingerprinting vector (by which certificates are remembered/trusted), or expose users to MITM risk every time.
- zmmmmm 2y agoI'm not proposing this for everything and high security public facing contexts can definitely do the maintenance to manage frequent certificate rotation. I just don't want my garage door integration with my car to stop working because its certificate broke. I'd argue these privately deployed single use dedicated certificates are actually better off self-signed and issued on a TOFU basis than using public key infrastructure. It's how bluetooth and many other things work, so why on earth are browsers so bent against it.