Live data from Hacker News

Why are banks still getting authentication so wrong?

jamal.haba.sh

31–40 of 375 posts

Re: Why are banks still getting authentication so wrong?

#31
They should all be shamed continually until they adopt the common sense ideas in the article.

Sadly I have to conclude from evidence that these incompetent buffoons think you can compute “how secure our site is” by asking “is it a f*cking pain in the ass for everyone to log in, almost all the time?” If yes, then secure.

Bonus points for “is it impossible to log in when you don’t have your cell phone that you registered with us?”

Re: Why are banks still getting authentication so wrong?

#32

Also, they still expect you to authenticate when they phone you. No, I'm not going to tell you my birthday when you phone me. No wonder so many people get scammed, when banks are training people on how to get scammed.

It's stupid to give out credentials over the phone, but it's stupider still to have a system where one's birth date is a credential that is supposed to remain confidential.

Re: Why are banks still getting authentication so wrong?

#33

What actual real life person is going to switch their bank account because TOTP isn't supported? That's why banks get authentication wrong. Because they are in the business of banking and banking customers do not care about TOTP.

But banks should have to provide better security or they should be at fault if the account is accessed by a third party due to their weak security.

Re: Why are banks still getting authentication so wrong?

#34

Also, they still expect you to authenticate when they phone you. No, I'm not going to tell you my birthday when you phone me. No wonder so many people get scammed, when banks are training people on how to get scammed.

Recently had to call Discover because of unauthorized use of card, apparently to buy Facebook ads of all things. They didn't call me, just locked my account and said I had to call them. I couldn't even pay the balance until I did.

Anyway they needed to verify my identity, so they ask me for some info from the back of the card and a phone number that they can send the OTP to. I give them a phone number, it's not even the one on the account, they send the text to it. The text message says that the bank will NEVER ask for the code over the phone. They ask for the code, I give it to them, identity verified.

Re: Why are banks still getting authentication so wrong?

#35
post #22

OP's problem sounds like failure to plan. If you are going to suspend your cell plan, you should probably check your authenticator works or have a backup option before you travel to another country. I don't know what the viable alternative is. Passkeys have just as many issues when phones are stolen, lost or broken. You cannot expect consumers to store recovery codes. I do agree support of TOTP authenticators would h…

A viable alternative is to offer multiple 2FA options, one of which should be RFC 6238 TOTP. The author would have probably planned ahead by selecting that rather than a proprietary app or SMS.

Re: Why are banks still getting authentication so wrong?

#36

Also, they still expect you to authenticate when they phone you. No, I'm not going to tell you my birthday when you phone me. No wonder so many people get scammed, when banks are training people on how to get scammed.

My rule is simple: if you contact me, you are the one that had to authenticate. Otherwise you are probably a scammer.

Although, I haven’t had many instances of communications from my bank where I cared about them authenticating. Like, if they tell me there is a problem, I can go check it out through the app, website, or whatever the user-initiated channel is. When I feel like it.

Re: Why are banks still getting authentication so wrong?

#37

UBS Switzerland has a decent system. When I first opened the account 15 years ago we had a number pad of codes on paper we entered as the authentication. Then later we got a credit card sized electronic device where we enter a passcode and it gives us a one-time code to enter to login. And now we have an Access app - we go to the website, enter our contract number, point our phone at a QR code on the webpage and auth…

Banks in the US sometimes support U2F, but you can never disable SMS. Maybe one day.

Would be nice if they could do email instead.

Re: Why are banks still getting authentication so wrong?

#38

Some banks do it properly. For example, my local credit union does Google Authenticator (actually TOTP, but they call it Google Authenticator). I use it with Authy on F-Droid.

Please do not use Authy, lacks essential features and it was bought by a bad actor.

I switched from Lastpass Authenticator to Authy after the hack. The lack of the "upcoming key" feature has been a huge paint point.

Any suggestions for what is better?

Re: Why are banks still getting authentication so wrong?

#39
post #22

OP's problem sounds like failure to plan. If you are going to suspend your cell plan, you should probably check your authenticator works or have a backup option before you travel to another country. I don't know what the viable alternative is. Passkeys have just as many issues when phones are stolen, lost or broken. You cannot expect consumers to store recovery codes. I do agree support of TOTP authenticators would h…

> you should probably check your authenticator works or have a backup option before you travel to another country. They may sign you out automatically if you connect from a different country.

TD Authenticate does not require a network connection. I outright disabled network access for the app on my phone.

Don't know how he got logged out but he almost certainly didn't check before leaving the country.

Having said that, the 2FA for TD is atrocious as it provides SMS fallback in addition to their bespoke app.

Re: Why are banks still getting authentication so wrong?

#40
> There’s no excuse anymore.

Implementing "modern" auth flows is challenging with old core systems.

From a risk management and compliance standpoint, this new auth infrastructure would represent a non-trivial expansion in the bank's audit scope.

Until a regulator makes it a requirement to use whatever new auth flow, it is not going to happen at scale.

Post reply on HN