The big assumption here is that SSL/TLS is used solely in browsers. That is not how it is being used in Thread, for example, and indeed in other similar technologies. In Thread, it is used for local device authentication and authorisation. These use cases clearly benefit from a PAKE, i.e. getting deriving a shared cryptographic from a weaker shared password.
Robert On 15 February 2016 at 22:32, Tony Arcieri <basc...@gmail.com> wrote: > On Mon, Feb 15, 2016 at 11:54 AM, Watson Ladd <watsonbl...@gmail.com> > wrote: > >> PAKE in SSL has always been a solution in search of a problem. >> > Browsers do not have UI elements compatible with PAKE (unless someone > cares to bring up the basic auth dialog, in which case I'd simply suggest > please don't) > > Brian Warner's "Magic Wormhole" use case seems like something of a killer > app for PAKE, but that's clearly a non-SSL context. > > PAKE in SSL seems to be in need of new browser standards which are > probably unlikely to happen. I think "passwordless" standards like FIDO > UAF/U2F which offer a better user experience are far more likely to see > browser support. > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > >
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
