News for hackers. Stuff that matters.
Re:Ask HN: A major USA bank is storing passwords in cleartex... by kevin_thibedeau on Tuesday February 18, 2020 @10:47AM (#22356829)
So they can add columns for 2FA but strengthened password storage is not doable?

This was forgivable 30 years ago. It was bad practice 20 years ago. Someone could have demonstrated leadership and developed a ten year plan to fix their legacy problem then.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by moviuro on Tuesday February 18, 2020 @11:24AM (#22357137)
> developed a ten year plan to fix their legacy problem then

They did. And Pi factor came in. And budget was cut because those pesky fintech are a threat, and clearly money was better spent on a more modern offer than on those "security" concerns.

And yes, it's possible to add 2FA to the front layer. However, the remnants of COBOL code running on the mainframe for the last 25 years weren't designed to handle passwords length 9 or more, and the last guy who knew how that code was built has retired some 15 years ago.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by marcus_holmes on Tuesday February 18, 2020 @11:44AM (#22357333)
That COBOL layer that underlies almost all of our infrastructure.

It was written when the cost/benefit calculation of writing it involved "downsizing" thousands of clerks who were doing the job manually.

It can't be replaced because the cost/benefit calculation of replacing it does not involve anything like those kinds of numbers. The benefits of avoiding even a major security incident just don't compare to the costs.

Y2K taught me this. Nothing has changed since.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by dx034 on Wednesday February 19, 2020 @04:47AM (#22364220)
Some banks are replacing their core banking system with new software. It's extremely expensive, a huge risk (any delay in migration means time where customers can't use ATMs or cards) and the benefit vs just adding API layers on top isn't always clear. At some point everyone needs to modernize but there are very few people who'd want to take responsibility for a project that size.

TSB customers have learned how painful it can be if the migration of a core banking system fails: https://www.independent.co.uk/news/business/news/tsb-it-fail...

Re:Ask HN: A major USA bank is storing passwords in cleartex... by marcus_holmes on Wednesday February 19, 2020 @11:52AM (#22367297)
Not only banks. I bought a house with the money I made on a Y2K project for a water authority's billing system. I doubt they've managed to work out how to replace that mess of COBOL without going broke.
Re:Ask HN: A major USA bank is storing passwords in cleartex... by jdc on Tuesday February 18, 2020 @02:21PM (#22359336)
[...] clearly money was better spent on a more modern offer than on those "security" concerns.

And there's the real problem:

The banks will save their money and stick with plaintext if they can get away it.

Put another way, it's an incentive problem.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by moviuro on Tuesday February 18, 2020 @03:53PM (#22360298)
Have you seen how French banks authenticate users?

With a six-digit PIN.

See

- https://www.labanquepostale.fr/ > "Me Connecter"

- https://lcl.fr/ > "Mon Espace"

- https://particuliers.societegenerale.fr/com/icd-web/cbo/inde... > 12345678 > Valider

Re:Ask HN: A major USA bank is storing passwords in cleartex... by imtringued on Wednesday February 19, 2020 @06:49AM (#22364758)
Speaking about Germany here, the online banking userid is much longer and basically acts a second password. It's not written on your card or used for anything except logging into your account via online banking.
Re:Ask HN: A major USA bank is storing passwords in cleartex... by carterehsmith on Tuesday February 18, 2020 @12:46PM (#22358127)
Yeah, this "we can't extend password beyond 8 characters because legacy systems" argument does not hold water.

My experience: built a Web site/app for: a) major bank b) major corp, back in the days when Web presence was kind of a new thing. ~15-20 years ago.

You build a new (Web) app and treat the legacy system (happened to be some mainframe) as a backend or whatever. Add new tables to hold user's credentials, email addresses, and whatever else. Link the "new" credentials with the old "account id on mainframe" or whatever. Not really rocket science.

BTW - there was no such thing as an "old password table with max 8 character", not for retail customers. Retail customer did not have a password, or email.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by o-__-o on Tuesday February 18, 2020 @11:50PM (#22363117)
Until 3 years ago, J.P. Morgan chase would only store the first 8 characters of your password. They would accept more but silently discard it
Re:Ask HN: A major USA bank is storing passwords in cleartex... by carterehsmith on Wednesday February 19, 2020 @07:17PM (#22371604)
>> Until 3 years ago, J.P. Morgan chase would only store the first 8 characters of your password. They would accept more but silently discard it

Oh, I am sure they do. The big question for this thread is: how come this "8-character all-uppercase" password is a thing in States, but less of a thing in e.g. Europe.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by o-__-o on Monday February 24, 2020 @09:00PM (#22410349)
*did

There was a forced password reset that enabled real password policies.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by IncRnd on Tuesday February 18, 2020 @01:32PM (#22358720)
>> Add new tables to hold user's credentials, email addresses, and whatever else.

Adding a table to hold users' credentials doesn't really solve the problem that is being discussed, which is storing users' credentials. All that does is add a new attack surface, stealing the new credentials, and the original credentials are still in the same position.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by imtringued on Wednesday February 19, 2020 @06:54AM (#22364772)
Yes, you are right but we are talking about potential causes of these strange policy decisions. One source is simply old software that cannot be updated but this sub-thread is trying to debunk that by saying that you can have a modern table with hashed passwords and a generated secret value that conforms legacy restrictions. The secret value can be used as a password on the old mainframe. There will be collisions but they can be prevented by comparing usernames.

There is no technical excuse for not hashing passwords.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by aembleton on Wednesday February 19, 2020 @04:11AM (#22364066)
You can salt and hash the new password; and the old password can be in plain text. The old password being in plain text doesn't matter so much if it is not possible to access the legacy system directly from outside of the banks network.
Re:Ask HN: A major USA bank is storing passwords in cleartex... by carterehsmith on Tuesday February 18, 2020 @07:10PM (#22361819)
>> Adding a table to hold users' credentials doesn't really solve the problem that is being discussed, which is storing users' credentials.

?

Not sure if serious.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by altacc on Wednesday February 19, 2020 @03:39AM (#22363955)
> This was forgivable 30 years ago.

A lot of the mainframe systems running large organisations were written more than 30 years ago and are still the core of the business, so their limitations are the constraints everyone else works around.

> Someone could have demonstrated leadership and developed a ten year plan to fix their legacy problem then.

The large project I work on is 12 years into replacing the mainframe platforms which have run the business for 45+ years, and we're not even halfway through the portfolio. Do not underestimate the complexity of these mainframes and the time & cost needed to fully replace them.

Re:Ask HN: A major USA bank is storing passwords in cleartex... by imtringued on Wednesday February 19, 2020 @06:46AM (#22364749)
We have a legacy database at our company that we simply wrapped with a service. There are still a lot of clients that access the database directly but that number is shrinking. Limitations of the database can be worked around in the service layer so it wouldn't matter to us if we still use the original database in 10 years but it also wouldn't matter if we just migrate it to postgres one day.