3 ms·
This still sounds the same as client side hashing to me. At some point I tried talking to people to make client side hashing an option in <input type=password
by lucb1e 8y ago
This still sounds the same as client side hashing to me.
At some point I tried talking to people to make client side hashing an option in <input type=password hashmethod=X>, but nobody cared more than saying "yeah sounds good" when prompted. If this would have been implemented and would have become mainstream, browsers can warn if a site (suddenly) doesn't use it, much like warning for http (or even pinning a la hsts). So as it is, it indeed cannot be done securely in browsers.
- tptacek 8y agoApart from the fact that I think client-side hashing is silly, I agree with you; we're saying the same thing about the feasibility of PAKEs in browser applications.
- the_clarence 8y agoIt’s not silly if it’s done outside of browsers I’d say. But with browsers it's tricky to implement (and its where it would be useful)
- tptacek 8y agoIt's silly because as soon as you're doing something custom clientside, you might as well just use a PAKE.
- the_clarence 8y agoI don't agree. PAKE is useful to setup a secure channel. But if you already have a secure channel that doesn't need client authentication, and you want to augment it with client authentication, this is easier to implement
- fileworm 8y agoYour proposal is equivalent to sending plaintext passwords, because the client-calculated hash can be used like a password.
- tptacek 8y agoNo, it's not. You can capture the password-equivalent authenticator, but (assuming a strong KDF) not easily reverse it back out to a password that could be used at other sites, which is the only reason anyone cares about hiding passwords from servers in the first place.
- Ar-Curunir 8y agoThis doesn't prevent dictionary attacks, since there's no salt involved, AFAIK.
- lvh 8y agoSince you're not worried anymore about burning the server-side resources, you prevent the dictionary attack in this scenario with a punitively expensive KDF. (Note: I am not saying this is a good idea! It's OPAQUE but worse.)
- lucb1e 8y agoIn the draft spec I wrote it would be salted by default with the origin (proto+domain+port), and could be overridden (in case a site changes domains) by a parameter. That would act as salt for the site, so that you have a unique hash for each site without having to keep (and sync to other browsers and computers) a database of salts.
- the_clarence 8y agoi like your idea a lot
- AlexCoventry 8y agoThe blog post points out that client-side hashing exposes you to ahead-of-time dictionary attacks, because you have to reveal the salt in the initial phase of the challenge.