But the thing is that you should never have access to the plaintext password and thus you should never be able to receive it in an email. You should store the salted hash of the password instead of the password itself.
But the thing is that you should never have access to the plaintext password and thus you should never be able to receive it in an email. You should store the salted hash of the password instead of the password itself.
8ace40@programming.dev 1 year ago
These kind of forums don’t store the plaintext password, they send an email while in memory, and hash them afterwards. Still bad security, but it’s not storing it in plaintext.
Miaou@jlai.lu 1 year ago
It’s storing it in at least one third party’s database. Indeed, it’s not stored in plain text, it’s doing something much worse
sekhat@lemmy.temporus.me 1 year ago
But you are supposed to change that generated password as soon as you use it to login. Now I have no idea about these forums, but you’d expect the software to enforce that need to change
Miaou@jlai.lu 1 year ago
It’s still stupid because people reuse password. They shouldn’t, but they do. If it’s one time login, make it a token. There’s zero reason to ever email a password, period
jormaig@programming.dev 1 year ago
But your password should never reach the server. It should be hashed already at the client and then salted at the server with a random hash. Then you store the salted hash