Live data from Hacker News

TMobile confirms they store passwords in plaintext, don't see why it's a problem

twitter.com

31–40 of 45 posts

Re: TMobile confirms they store passwords in plaintext, don't see why it's a problem

#31
post #18

Whats stopping someone from creating a list of what strings trslate to each hash

https://en.wikipedia.org/wiki/Salt_(cryptography)

https://github.com/crypto101/book/blob/master/Crypto101.org#...

While that was true before GPUs

>To a modern attack, salts quite simply don’t help.

Everybody should really move to key derivation functions (ideally scrypt)

Re: TMobile confirms they store passwords in plaintext, don't see why it's a problem

#32
post #5

Here comes the damage control https://twitter.com/TMobileHelp/status/982334382806454272 Hoping this blows up. Time to short.

I'm wondering. Why would encrypting the password be any more worse than hashing ? If the private key of encryption is well kept, I don't see why they couldn't do that. I understand though that no one being able to know the password except the user is utmost security, but why not encrypting it ?

People reuse passwords. The mere possibility of someone being able to see it is bad.

Re: TMobile confirms they store passwords in plaintext, don't see why it's a problem

#33
God, they're making matters worse--

  So, you never worked for us in Austria though. But thank you very much for sharing your opinion.
->

  Thanks for stating that you seemingly haven’t understood what we’re trying to tell you.
->

  Oh, I do get it. I hope you enjoyed my response

Re: TMobile confirms they store passwords in plaintext, don't see why it's a problem

#34
post #6

"Well, what if your infrastructure gets breached and everyone’s password is published in plaintext to the whole wide world?" "What if this doesn't happen because our security is amazingly good? ^Käthe" This is begging for it.

"challenge accepted"

Re: TMobile confirms they store passwords in plaintext, don't see why it's a problem

#35
post #18

Whats stopping someone from creating a list of what strings trslate to each hash

https://en.wikipedia.org/wiki/Salt_(cryptography)

Hashcat running on a Amazon p3.16xlarge (8 Nvidia Tesla V100 GPUs) does 115 BILLION salted SHA-1 hashes per second. Based on that, most weak passwords are cracked in seconds, even if you have per user salts.

Re: TMobile confirms they store passwords in plaintext, don't see why it's a problem

#36
This is a really common technique in the UK, especially with online banking. “Enter the 1st, 4th, and 7th characters of your password.” Apparently the point is to prevent replay attacks.

The problem with telecom companies is they have customers from a wide spectrum of technical capabilities. Their systems need to be able to support the baby boomer who calls support because they can’t remember their password, pin, or something...

I’m not defending these practices by any means, but these society-spanning institutions are facing challenges of balancing usability and security that many companies do not need to worry about.

If a company wants to implement a system like this, fine. But please tell me before I enter my password so I know not to reuse another password of mine.

Re: TMobile confirms they store passwords in plaintext, don't see why it's a problem

#37
post #6

"Well, what if your infrastructure gets breached and everyone’s password is published in plaintext to the whole wide world?" "What if this doesn't happen because our security is amazingly good? ^Käthe" This is begging for it.

"challenge accepted"

Looks like someone found a XSS vulnerability at T-Mobile Austria website [1]

[1] https://twitter.com/fabricio_giglio/status/98236273592413798...

Re: TMobile confirms they store passwords in plaintext, don't see why it's a problem

#38
post #18

Earlier quoted context omitted.

https://en.wikipedia.org/wiki/Salt_(cryptography)

https://github.com/crypto101/book/blob/master/Crypto101.org#... While that was true before GPUs >To a modern attack, salts quite simply don’t help. Everybody should really move to key derivation functions (ideally scrypt)

What parameters do you recommend?

Is N=14, r=8, p=1 good enough?

Re: TMobile confirms they store passwords in plaintext, don't see why it's a problem

#39

This is a really common technique in the UK, especially with online banking. “Enter the 1st, 4th, and 7th characters of your password.” Apparently the point is to prevent replay attacks. The problem with telecom companies is they have customers from a wide spectrum of technical capabilities. Their systems need to be able to support the baby boomer who calls support because they can’t remember their password, pin, or…

Is it okay to sacrifice security because some members of society are either too old/dumb/misguided/whatever to bother?

At what point do we just have to leave these people behind?

Re: TMobile confirms they store passwords in plaintext, don't see why it's a problem

#40

This is a really common technique in the UK, especially with online banking. “Enter the 1st, 4th, and 7th characters of your password.” Apparently the point is to prevent replay attacks. The problem with telecom companies is they have customers from a wide spectrum of technical capabilities. Their systems need to be able to support the baby boomer who calls support because they can’t remember their password, pin, or…

Is it okay to sacrifice security because some members of society are either too old/dumb/misguided/whatever to bother? At what point do we just have to leave these people behind?

As long as the institutions are insured against fraud, they have a greater incentive for usability than security.
Post reply on HN