2 ms·
Besides issues like requiring javascript or something, its usually not a useful step. The hash of the password can be stolen just as easily as the password its
by jayd16 10y ago
Besides issues like requiring javascript or something, its usually not a useful step. The hash of the password can be stolen just as easily as the password itself. You've just made a new password.
If you salt the password with the url, all you've done is made a unique password per website which is what you were supposed to be doing anyway.
- dsp1234 10y agoThe point was for the browser to warn the end user about password re-use. The browser doesn't need javascript to see the contents of a password field, or to show an indicator in the browser's chrome. It's the browser. If you salt the password with the url, all you've done is made a unique password per website which is what you were supposed to be doing anyway. Note that browsers can already store password lists (ex: Chrome settings, search manage passwords). There would just be an extra step to compare those passwords together.