Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 12 submissions in the queue.

At What Point Does Storing Passwords in Plaintext Become Criminally Negligent

posted by Fnord666 on Sunday April 08 2018, @02:07PM   Printer-friendly
from the easier-to-check-that-way dept.

An Anonymous Coward writes:

https://www.privateinternetaccess.com/blog/2018/04/another-day-another-breach-at-what-point-does-storing-passwords-in-plaintext-become-criminally-negligent/

The third largest breach ever just happened in Finland. Passwords were stored in plaintext. At T-Mobile Austria, they explain that of course they store the password in plaintext, but they have so good security so it's nothing to worry about. At what point does this become criminally negligent?

Original Submission

 
This discussion has been archived. No new comments can be posted.
At What Point Does Storing Passwords in Plaintext Become Criminally Negligent | Log In/Create an Account | Top | 138 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 0) by Anonymous Coward on Monday April 09 2018, @01:55PM (1 child)

    by Anonymous Coward on Monday April 09 2018, @01:55PM (#664409)

    What if your hash fails to meet complexity requirements because it just happens not to have any capital letters in it? Or as is quite likely, is longer than they will accept?

  • (Score: 0) by Anonymous Coward on Monday April 09 2018, @08:43PM

    by Anonymous Coward on Monday April 09 2018, @08:43PM (#664664)

    Haven't had that happen just yet, but good point nonetheless. The way I wrote my method is does give both lowercase and uppercase letters. I think what I'll end up doing is adding a constant to the end of each password including a symbol, a number, and two letters, one in uppercase and one in lowercase.