Live data from Hacker News

Why are banks still getting authentication so wrong?

jamal.haba.sh

21–30 of 375 posts

Re: Why are banks still getting authentication so wrong?

#21
> TOTP Support: Let users use any standard authenticator

How many of them allow to generate a code related to specific operation (provide a context for what is being "confirmed")? This is the EU requirement that killed everything but SMS and bank mobile apps.

Re: Why are banks still getting authentication so wrong?

#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 help savvy consumers, but probably still too complicated for seniors etc. Watching my elderly relatives with poor vision enter a TOTP code was quite instructive. The UI of Google Authenticator made no sense to them and they didn't understand why it kept changing and getting rejected. They were barely able to enter six numbers in a 30 second window.

Re: Why are banks still getting authentication so wrong?

#24
I don’t think banks are deliberately trying to avoid using TOTP, it’s just that they have to cater to the lowest common denominator, you know, the kind for which anything computer-related is basically black magic.

SMS is an easy target because ~everyone has a cell phone and with things like Apple’s verification code auto-complete, the amount of friction is greatly reduced.

With standard TOTP, now they have to worry about if the user correctly added the secret information to whatever authenticator app. And write corresponding documentation explaining how to do so, for every major authenticator app.

There also has to be a backup flow for when the user loses their authenticator app which is probably just going to be SMS. So why not stick with just SMS in the first place?

I hate using SMS for 2FA, but I understand the business decisions around it. I think as engineers we forget, to be frank, just how bad most people are with technology.

Re: Why are banks still getting authentication so wrong?

#25

Can we get rid of the password expiration too? Requiring that users change their perfectly secure password every 6 months is absurd and gives the impression of security when in reality it only makes things worse.

One hundred percent. I’d be interested to see how many people resort to having weaker passwords just to try to remember the new password every 6 months. I know many folks are proud of their password ‘system’ of using the same word and adding different numbers every time they need to change it. Not helpful.

Re: Why are banks still getting authentication so wrong?

#26

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.

Can you elaborate? Is twilio a bad actor?

Re: Why are banks still getting authentication so wrong?

#27
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.

Re: Why are banks still getting authentication so wrong?

#28

Can we get rid of the password expiration too? Requiring that users change their perfectly secure password every 6 months is absurd and gives the impression of security when in reality it only makes things worse.

NIST only changed that recommendation last year. Expect that update to take at least 10 years to percolate through institutions like banks.

Re: Why are banks still getting authentication so wrong?

#29
Identity providing is a natural monopoly and should be provided by the state in same manner as a passport is provided.

We can discuss the implementation but in Denmark and quite a few other countries, the login problem in online government services and banking is solved by a single state run identity provider (MitID) and hopefully the EU will be succesful with their EIDAS initiative and provide a solution that works across country boundaries.

https://en.wikipedia.org/wiki/EIDAS

Re: Why are banks still getting authentication so wrong?

#30

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.

wait, which bad actor? I use it for everything and hear about it first time
Post reply on HN