2 ms·
This doesn't prevent dictionary attacks, since there's no salt involved, AFAIK.
by Ar-Curunir 8y ago
This 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.