News for hackers. Stuff that matters.
Re:I made my own WireGuard VPN server by tialaramex on Sunday August 05, 2018 @10:43PM (#17694804)
Sure, lets blame the travel.

You're very kind to Paul Kocher in naming him one of the "best in the world". Maybe he'd just gone to Vegas too when he decided you could get away with abusing RSA decryption to implicitly authenticate the recipient?

In grouping cross protocol attacks like DROWN in as downgrades you undo your own arguement. WireGuard with this unusual definition can become vulnerable to downgrade, bad guys might get your WireGuard v2 private keys by abusing the legacy WireGuard v1 protocol, the deliberate lack of compatibility between the two not withstanding.

Of course the specifics of DROWN can't work against WireGuard, nor against TLS 1.3, but you're insisting this isn't about specifics, it's a general "lesson"

Re:I made my own WireGuard VPN server by tialaramex on Saturday August 11, 2018 @04:02AM (#17738831)
On that last sentence - TLS 1.3 can be vulnerable here under the same circumstances as TLS 1.2, I have no idea what I was thinking here, I was reminded by Appendix E.8 of the RFC this morning so I guess appendices are good for something.
Re:I made my own WireGuard VPN server by tptacek on Sunday August 05, 2018 @11:57PM (#17695016)
I'm pretty comfortable with my assessment of Kocher. It's easy to look up what he's been up to.

Help me understand how exactly someone would get WireGuard's v1 Noise primitives, which bake the v1 construction identifiers and a v1 constant into the derivation of all secrets as the literal first step of the protocol, to generate something that would be comprehensible to a hypothetical v2 of the protocol.

Re:I made my own WireGuard VPN server by tialaramex on Monday August 06, 2018 @03:11AM (#17695687)
My crystal ball is cloudy.

No, no, you're right, back in 1996 the "best in the world" were incompetent buffoons, whereas today we know exactly how to do this right and we definitely haven't overlooked anything /s

Re:I made my own WireGuard VPN server by tptacek on Monday August 06, 2018 @03:36AM (#17695790)
This isn't an answer to the question I asked, it's just huffing.
Re:I made my own WireGuard VPN server by tialaramex on Monday August 06, 2018 @07:18AM (#17696678)
You didn't ask a question. You did ask me to "help you" see into the future and I informed you that my crystal ball is cloudy.
Re:I made my own WireGuard VPN server by tptacek on Monday August 06, 2018 @10:36AM (#17697926)
That's a weird way to say "ok, I was wrong about it being possible to recapitulate DROWN using WireGuard v1 and any hypothetical WireGuard v2".
Re:I made my own WireGuard VPN server by tialaramex on Monday August 06, 2018 @12:11PM (#17698886)
An ability to recognise that "I don't know a successful attack" isn't the same as "it's impossible to attack" is why I don't share your (as yet unjustified) confidence in zero agility. It's a microcosm of this thread.
Re:I made my own WireGuard VPN server by tptacek on Monday August 06, 2018 @01:01PM (#17699419)
I'm sorry, but you're being slippery, and I'm not going to pretend that's a valid argument. It is not my claim that nobody will find vulnerabilities in WireGuard. I hope they do! Generalizing and weaponizing crypto exploits is something I work on professionally and I'm a cheerleader for team breaker.

My claim is that a cross-protocol attack like DROWN will not work on WireGuard, and I explained why.

Rather than acknowledge that explanation, you either (a) rattle off irrelevant details or (b) retreat to abstractions. But there's no abstraction to retreat to. DROWN isn't an unknowable attack. You can just read the paper to see how it works. After you do that, I suggest you read the WireGuard white paper, which is short and straightforward (the cryptographic details make up only about a third of it). You've said several things on this thread that lead me to believe you haven't yet read it, and I think you'll find it enlightening.