Comment on Larion Studios forum stores your passwords in unhashed plaintext.
hex@programming.dev 1 year agoYeah if they send the password in an email in plain text that’s not storing it. You can send the email before you store the password while it’s still in memory and then hash it and store it.
Cabrio@lemmy.world 1 year ago
Still bad practice and a security vulnerability at best. Email isn’t E2E encrypted.
beefcat@lemmy.world 1 year ago
there is no possible way to handle sensitive data without storing it in memory at some point
it’s where you do all the salting, hashing, and encrypting
JackbyDev@programming.dev 1 year ago
Understatement of the year right here. Everyone in this thread is more interested in dunking on OP for the few wrong statements they make rather than focusing on the fact that a service is emailing their users their password (not an autogenerated “first time” one) in plaintext in an email.
RonSijm@programming.dev 1 year ago
Since we’re nitpicking here - technically you can. They could run hashing client side first, and instead of sending the password in plain-text, you’d send a hashed version
beefcat@lemmy.world 1 year ago
but then you expose your salt to the public
ilinamorato@lemmy.world 1 year ago
This opens up the possibility of replay attacks in the case of data breaches, though, and those are much more common than http mitm attacks (made even less likely with the proliferation of https).
I’m not entirely sure whether hashing twice (local and server) is wise, having not thought through that entire threat vector. Generally I try to offload auth as much as I can to some sort of oauth provider, and hopefully they’ll all switch over to webauthn soon anyway.
oneiros@lemmy.blahaj.zone 1 year ago
Given what I know about how computers accept user input, I am fascinated to hear what the alternative is.
Cabrio@lemmy.world 1 year ago
You have the text input feed directly into the encryption layer without an intermediary variable.
frezik@midwest.social 1 year ago
Are you suggesting to do all this on the frontend before it goes to the backend?