News for hackers. Stuff that matters.
Re:T-Mobile Database Breach Exposes 2M Customers' Data by tyleraldrich on Tuesday August 28, 2018 @12:17PM (#17860033)
This isn't necessarily true (and is very dependent on what your password was) - they could have iterated through lists of common passwords w/ special characters, hashed them, and compared them to their DB, forcing a pw reset for everyone that had a match.

edit - just want to state that if they disallow special characters it really is a terrible policy, my point is just that resetting your password isn't proof they are stored in plaintext

Re:T-Mobile Database Breach Exposes 2M Customers' Data by chaoticmass on Tuesday August 28, 2018 @12:56PM (#17860476)
I doubt they did this, but I was just thinking about this problem--

Maybe they could have analyzed the plaintext password and stored information about the types of characters it contained and number of characters. Then they salt+hash the plaintext password and store the resulting hash. Now they know a little about the characters and length of the password without knowing the password itself.

Again, I doubt they did this.

Re:T-Mobile Database Breach Exposes 2M Customers' Data by kevin_thibedeau on Tuesday August 28, 2018 @12:30PM (#17860192)
Not salting passwords in 2018 is also idiotic lunacy.
Re:T-Mobile Database Breach Exposes 2M Customers' Data by tyleraldrich on Tuesday August 28, 2018 @12:35PM (#17860252)
This same exact strategy works with a salt as well.
Re:T-Mobile Database Breach Exposes 2M Customers' Data by lightbyte on Tuesday August 28, 2018 @01:44PM (#17860955)
He might have been referring to user specific salts? It would certainly be a lot more challenging for them to test every common password with every user's salt.