Chat App fined for storing passwords in plaintext

https://www.theregister.co.uk/2018/11/23/knuddels_fined_for_plain_text_passwords/
This is amazing, companies are finally getting fined for doing ridiculously stupid things 🙂
Yes, however that's Germany. Falls under EU's home turf. It's easier for EU to fine directly.

It's stupid - making passwords plaintext. What do they have in mind...? Getting easily hacked? It's not hacking if passwords are plaintext... no...? *snorts out laughing*
plain text?! LOL!!! I thought we were in 2018. I don't even do that - I have a password manager for that.
 
Why do companies/websites keep doing this? Does it really take that much more coding to store the passwords encrypted?
 
Why do companies/websites keep doing this? Does it really take that much more coding to store the passwords encrypted?
In short: They don't care.

A company cares about releasing new features and spicing things up so that they can beat their competitors. The last thing they think of is security. And well. We'll never get hacked, right? Why would any criminals go out of their way to target us? Every site / software has this mindset to some extent, including FP, XenForo, etc.

It's actually not particularly surprising. Companies tend to care more about security after they're compromised. But, also the less experienced a programmer is, the more they'll be all about the features and less about security. And well, programmers who know nothing are cheap and plentiful, right?

This is how you get the plaintext, etc.

It's basically what people call "acceptable risk". But in all honesty, I think the chances of you getting targeted sooner or later is probably 10 to 20%. Higher, if you have more than ten users.
In other words, you will almost certainly have someone coming after you, but people think of internet security as well locks, locks work right? Even though they can be picked easily.

The reason that locks are effective is largely because you don't have criminals from all over the world bearing down on you. It's mostly a deterrent. Like the nuclear weapons we all love stockpiling, but we generally know we will never use.

There is no such a thing as a deterrent on the internet. People do things anonymously all the time, there is no risk of being caught "picking a lock" or any other order of embarrassment.
The solution to the problem is probably regulation, but you should never trust the government to do anything vaguely helpful, they will make problems twenty times worse.

P.S. Many attacks, particularly things like SQL Injections or even commonly used software, can be easily automated. I am constantly being bombarded by such attacks, for software I don't even use 24/7 with practically no traffic.

If someone finds a zero day vulnerability, they will quickly weaponise it before the vendor can patch it and before the updates have enough time to flow out (even if a security issue is fixed, admins have to apply the patch).

And if not for the fact that over half the internet runs PHP and all manner of insecure garbage, I might even be a little smug about PHP being an insecure mess (which it is). This is just the tip of the iceberg.

This industry really needs to clean up this mess before the government comes in and regulates the hell out of everyone. Maybe, developers need a hippocratic oath. Like. "I will not write something insecure or which otherwise contributes to these social ills."

When you write insecure code, you don't just let yourself down, but you let the company down, you let your family down and ultimately, you let society down as now it has been hampered because of your ignorance.
 
Last edited:
This business is in the EU and knowing EU and Germany, it isn't suprising to see this happen. But you would at least expect the programmers to store the data in a database or use something like MySQL for the job.

The programmers in that company really need training.
 
This business is in the EU and knowing EU and Germany, it isn't suprising to see this happen. But you would at least expect the programmers to store the data in a database or use something like MySQL for the job.

The programmers in that company really need training.
Uh, what? It said they stored passwords in plaintext, it never said anything about them not using a database, unless you have some source we don't? It's been about twenty years since people built sites without using a database, that would be extremely unlikely.

With passwords, practically no one stores them in plaintext, unless they have no clue what they're doing. Normally, you'd run it through a hashing algorithm, a pre-made mathematical algorithm which is extremely difficult to reverse which spits out something like: $2a$10$ZJoLyvPiZCbKFFP0Cc5lc.Q0H6Bnbbnz90WDR/orRaBLesWgjLbkS

And then, when someone goes to login, you'd hash that password, and then, you'd compare the two hashes. There is no plaintext comparison and not even the server knows what the password is, so if you get compromised, then it's less painful,. If a site ever emails back your password, then you immediately know they're storing it in plaintext.

And beware of those rapidly evolving Nvidia cards, they can chew through weaker hash algorithms like that used in MyBB really easily (md5).

Only bcrypt, Argon 2, etc. are suitable hash algorithms in the modern day.
Even sha1 is on the way out, Google found collisions in it before, if I recall.

P.S. That hash is for test123, you're not going to be getting into any accounts with that, even if you can crack it.
 
Last edited:
Back
Top Bottom