> If the website can pull out your password to show it to you, an attacker can pull out the password to steal it.
As ever, the issue is explaining hashing.
> If the website can pull out your password to show it to you, an attacker can pull out the password to steal it.
As ever, the issue is explaining hashing.
Ordinary people are going to be thinking about a key in a lock. Does the lock on your house store the key inside? Maybe in some kind of information-theoretic sense but in the ordinary meaning of the word, no, it has a representation (that may not even be sufficiently specific to recover your key exactly). And if you lose your key you don't break into the lock to recover it--you call a locksmith to replace the lock, and get new keys.
That right there is an intuitive understanding of both hashing and good security principles that goes surprisingly far.
I don't think people are thinking about keys and locks. Passwords are a thing that existed before computers and that people understand perfectly outside of an IT context. Spies in films use secret phrases to prove they're the contact, kids use passwords to gain access to the clubhouse. But in all these non IT contexts the person checking the authentication knows the shared secret, so it's obvious how they check it.
If my mental model is "I've arranged a secret password with this website that proves I'm really me", then my first question when told the website doesn't know what secret password is "well how does it know that the password is correct?".
The best I've been able to come up with today is a somewhat lengthy metaphone with color mixing.
[Edit] Having said that, I just went and talked to my technical literate non programmer wife and she used the key and door analogy.
"It is possible to store passwords in a way that the website cannot see your password, but can still verify that a password entered by you checks out." (trust us, after all you're trusting that we know what we're talking about by reading this stuff)