3 ms·
but two subsequent protocol versions had already shipped That doesn't really address the 'agility didn't help here' point at all. The argument against agility
by pvg 8y ago
but two subsequent protocol versions had already shipped
That doesn't really address the 'agility didn't help here' point at all. The argument against agility as a design approach is straightforward and widely articulated - it's obviously informed by the SSL/TLS experience but doesn't outright depend on it. It's not too difficult to imagine that there could be some sort of coherent counter-argument. If you have one, though, it's impossible to parse it out from this enthusiastic mixture of non-responsive detail and superciliousness.
- tialaramex 8y agoBut it did help there, as I already pointed out and you ignored twice.
- tptacek 8y agoIt did not help here. In fact, it amplified the problem. We knew RC4 to be broken when BEAST was announced. Nevertheless, people enabled it, as a "stopgap", to deal with BEAST. RC4 is arguably less secure than BEAST-affected TLS (BEAST was in practice quite difficult to trigger), and, either way, all those RC4 deployments ended up also needing to be scoured off the Internet!