The root cause of this is likely because there is some legacy system at the bottom of the authentication stack. The password rules give this away -- there is an upper limit on length (50 characters), and you can't use symbols (@, $, etc) or spaces (precluding xkcd-style "correct battery horse staple" memorable passwords). Use a password manager ("storing passwords under symmetric encryption") and don't reuse your password across sites.
As a first approximation, nearly 100% of corporate executives wouldn't see the problem with storing passwords in cleartext. To them, the T-Mobile rep's arguments would seem reasonable:
"I really do not get why this is a problem. You have so many passwords for every app, for every mail-account and so on. We secure all data very carefully, so there is not a thing to fear."
If you ever wonder why more corporations don't get hacked every day, it's probably because the vast majority of software developers are decent, honest human beings who have no desire to inflict large-scale damage.
2 comments
[ 1.9 ms ] story [ 28.2 ms ] threadAs a first approximation, nearly 100% of corporate executives wouldn't see the problem with storing passwords in cleartext. To them, the T-Mobile rep's arguments would seem reasonable:
"I really do not get why this is a problem. You have so many passwords for every app, for every mail-account and so on. We secure all data very carefully, so there is not a thing to fear."
If you ever wonder why more corporations don't get hacked every day, it's probably because the vast majority of software developers are decent, honest human beings who have no desire to inflict large-scale damage.