Re: [TLS] Should TLS 1.3 use an augmented PAKE by default?

[Peter Sylvester <[e-mail]>]

On 03/19/2014 04:43 PM, Andy Lutomirski wrote:
> On Tue, Mar 18, 2014 at 10:54 PM, Ryan Sleevi <[e-mail]> wrote:

>> TLS SRP's lack of use suggests that there is not a high pressure for
>> deployment here.
>>
>> It's probably worth thinking some about why SRP adoption has been so
>> slow (i don't know the global answer here, but i only know a few folks
>> who are using it)
I remember that years ago, when we implemented SRP
with openssl, I was thinking about the doing same in the NSS.
Well, not enough time.

The reason was the possibility to use the database for
url/login/password

- Browsers have the user/password containers tied to some host.

- A browser can add the ciphersuite but no user in the clienthello
   if the host is not known.

- If the host is known the browser can immediately provide the
   identity (which could be encoded as hash(user@host).

- A password could also be encoded as in Steve Bellovins draft.

This leaves us at the same "inconvenience" having a pop up
for the "PIN" outside the html layer but at least one would not
send a password to a badly authenticated site?

Peter