I’ve always been of the impression that storing passwords in a database as plain text is (as someone else here put it) a Very Bad Thing™.
Historically, most of our server-side coding needs have been contracted out to a group of programmers. They store passwords in MySQL databases in plain text.
As the resident code monkey (incidentally, the first server-side-savvy monkey to work here, so I’m inheriting the earth, so to speak) I have this pit of the stomach feeling that it’s my bum that will be on the line when this plain text nonsense is exploited.
I tried to explain to my boss how very very bad plain text passwords are, but it dawned on me: I don’t think I’ve ever really know why they’re so bad. Is there more to it than handing your hackers a list of passwords on a silver platter? That sounds bad enough for me, but in la-la land, where our websites are “secure” and impervious to any hacker, this argument doesn’t seem to cut it. How can I convince (or scare) my boss into demanding hashing on his treasured websites?
Related: Encrypting/Hashing plain
text passwords in
database
In the military it’s called “Defense in Depth”. The theory is that you harden every layer you can rather than hardening just one layer and hoping it’s enough.
I’ve heard databases like yours called “hard on the outside, soft and chewy on the inside”. There are a million ways a dedicated hacker can get access to your database. Social engineering, a disgruntled employee, an ex-employee who decides to see if his login still works, or that backdoor he wrote is still there, one missed OS patch… the list goes on.
If a bad actor gets access through any of these methods, instead of just getting the data, he gets access to every username/password combination of every user of your system, and as someone pointed out, people often use the same combo for every website. So your hacker goes out and owns hundreds of people’s Paypal, email, and bank accounts.
Have I painted a gruesome enough picture yet?