@pake_preacher : I forgot the details of PAKE and SRP, but in the end the most secure client authentication requires:
1๏ธโฃ Strong, long term, human comprehensible, *serving endpoint* authentication;
*AND*
2๏ธโฃ TLS channel binding (enforcing known endpoints).
(Apart from those, both serving endpoint AND client MUST be trustworthy).
๐จ The -corrupt- CA/B forum breaks 1๏ธโฃ by:
a) Advocating anonymous Domain Validated certificates, which render secure account creation IMPOSSIBLE;
b) Continuously decreasing certificate lifetime.
๐จ Furthermore, "legitimate" MitM's * break 2๏ธโฃ.
* Man in the Middle, like on-device virusscanners and firewalls that "open" TLS tunnels (both requiring installation of a dedicated root certificate) and proxies such as (definitely not limited to) Cloudflare and Fastly.
๐ฑ Passkeys enforce NEITHER 1๏ธโฃ NOR 2๏ธโฃ.
๐ฑ๐ฑ Worse, because passkeys (or FIDO2 hardware keys) can be easily irretrievably "lost", servers typically provide WAY EASIER phishable authentication methods (such as "rescue codes").
@cendyne @soatok @chazh
#AitM #MitM #SecureOnlineAuthIsHARD #SecureAuthentication #OnlineAuthentication #Authentication #Impersonation #ChannelBinding #TLSchannelBinding #UTM #TLS #TLSinterception #TLSscanning #Proxy #Proxies #GoogleIsEvil #CloudflareIsEvil