News for hackers. Stuff that matters.
Re:I made my own WireGuard VPN server by tialaramex on Sunday August 05, 2018 @09:56PM (#17694659)
The confusion seems to lie with you here if it's with anyone. The stop gap RC4 preference is explicitly enabled by handshaking.

Beyond that though you seem to have your history out of order, BEAST is a TLS 1.0 attack, but TLS 1.2 was finished years before BEAST was published.

It's not a case of a protocol version "had to be burned to fix the problem" but two subsequent protocol versions had already shipped years ago which fixed the underlying cause and, as is the reality for which you seem so ill-prepared, scarcely anybody had upgraded.

All these years later financial services companies are getting waivers from PCI saying their cheap third rate POS terminal "has a mitigating control" and so it's fine that they still do TLS 1.0. So that's nice. Nice for them I mean. Hey, if you're "lucky" one day they'll be relying on a ten year out-of-date WireGuard, as enthusiastically endorsed by Thomas Ptacek. And every time you're asked about it you can spit feathers. How dare they. Like I said, if you're lucky.

As messy and uphill as it has been, the journey from SSLv2 to TLS 1.3 was only possible with the handshake.

Re:I made my own WireGuard VPN server by pvg on Monday August 06, 2018 @04:10AM (#17695901)
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.

Re:I made my own WireGuard VPN server by tialaramex on Monday August 06, 2018 @07:53AM (#17696850)
But it did help there, as I already pointed out and you ignored twice.
Re:I made my own WireGuard VPN server by tptacek on Monday August 06, 2018 @10:35AM (#17697907)
It 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!
Re:I made my own WireGuard VPN server by tptacek on Sunday August 05, 2018 @11:51PM (#17694995)
Thai Duong did BEAST during the brief window he worked with me at Matasano, so I'm pretty sure I have the chronology right.