2 ms·
The problem is that the broken protocol is frequently not removed. It is shoved to the end of the list, where it remains available, but that's "good enough" bec
by tedunangst 2y ago
The problem is that the broken protocol is frequently not removed. It is shoved to the end of the list, where it remains available, but that's "good enough" because surely it won't actually get used.
- kibwen 2y agoSure, but the same concern exists even for applications that have inflexible protocols. You either have someone willing and able to say that enough is enough and break backwards compatibility, or you don't.
- tedunangst 2y agoWell, I think one of the problems with ssl3 is nobody really knew who was using it on purpose, and even the people using it didn't know. With something like WireGuard 2, you will presumably figure out pretty quickly which endpoints can't communicate if they're still on wg1. At least that's something.