3 ms·
> raised enormously This article explains that (a) they chose to mimic an existing well used technology, the TLS handshake, in order to reduce opportunities fo
by tialaramex 4y ago
> raised enormously
This article explains that (a) they chose to mimic an existing well used technology, the TLS handshake, in order to reduce opportunities for surprises and (b) they have performed mathematical verification, something which wasn't practical a decade ago but is today
> I like the idea of OPAQUE password exchange, but I'd much rather see a move towards FIDO2/WebAuthn instead of going for another round of passwords.
You absolutely should use WebAuthn, this work doesn't deprecate WebAuthn, but not doing it wouldn't have magically resulted in lots of web sites getting WebAuthn. WebAuthn is intended to authenticate humans, but OPAQUE-EA not so much.
> Furthermore, with QUIC becoming the next HTTP standard because Google asked nicely, I don't see the point of adding to TLS 1.3 when the crypto scheme seems to be moving towards another protocol anyway.
The "crypto scheme" in QUIC is TLS 1.3. Not "It's a lot like TLS 1.3" or "They copy pasted some of TLS 1.3" it's just TLS 1.3. Features, including Exported Authenticators, from TLS 1.3 work just fine in QUIC because QUIC's encryption is TLS 1.3.
Given your reference to Google "asking nicely" I'm going to guess that you didn't really pay much attention and have concluded that QUIC (the IETF's encrypted transport protocol) is just Google's 10 year old QUIC protocol (today often referred to as gQUIC) plus a bunch of bureaucracy. That's not so, the fact QUIC is built on TLS 1.3 while gQUIC used Google's custom "QUIC Crypto" is just one example of the differences.
- withinboredom 4y ago> they have performed mathematical verification Verification is only as good as the model used to verify it. The implementation may (probably, actually,) still have at least one bug that negates everything.