Re:<input type="password" maxlength="20"> prevents me from l...
by walrus01 on Friday October 02, 2026 @07:50PM
(#49940012)
I mean literally like if the person's password was "potato##!" the customer service person would read back "potato##!". They weren't reading the encrypted contents of a pw field.
[ Parent
| on HN ]
Re:<input type="password" maxlength="20"> prevents me from l...
by UqWBcuFx6NV4r on Friday October 02, 2026 @07:58PM
(#49940064)
That doesn’t mean that it is stored as plain text. It just means that it isn’t hashed.
I agree that it any system that allows this IS almost certainly just storing as plain text, and that it’s bad regardless.
Re:<input type="password" maxlength="20"> prevents me from l...
by unsnap_biceps on Friday October 02, 2026 @07:59PM
(#49940071)
their point is it could have been stored encrypted and then decrypted for the customer service person to read back to you. Access to plain text != storing it as plain text.
Re:<input type="password" maxlength="20"> prevents me from l...
by Atheros on Saturday October 03, 2026 @03:00AM
(#49941980)
The only way three people can keep a secret is if two of them are dead.
If the data can be read by so many people in the company that even the customer service people have access, it's functionally not encrypted.
Re:<input type="password" maxlength="20"> prevents me from l...
by unsnap_biceps on Saturday October 03, 2026 @10:56AM
(#49944858)
I don't disagree with you, however the original claim of
> provably storing peoples' online banking logins in plaintext in some ancient mainframe database system
Is not about functional encryption but storing directly as plain text.