News for hackers. Stuff that matters.
Re:Downsides of Google Authenticator by BoppreH on Friday February 28, 2020 @11:09AM (#22443731)
> You're supposed to keep offline backup keys. Any sort of synchronization feature adds a ton of attack surface.

I find that a terrible design decision, because now every website has to implement their own backup code flow. PayPal, for example, is one of the most critical applications when talking about authentication, and while they support 2FA they don't give you any backup codes at all: https://www.paypal-community.com/t5/My-Account/Backup-codes/...

Now I cannot synchronize devices, I'm hosed if I ever lose my phone, and I'm still relying on PayPal customer support to do a proper out-of-band authentication. The worst of both worlds.

Re:Downsides of Google Authenticator by jdeibele on Friday February 28, 2020 @12:48PM (#22444636)
At one point I was able to use two copies (phone and iPad) of Symantec VIP Access with Paypal. I changed phones and I wasn't able to use the new copy.

However, I was able to set up Authy as a secondary authenticator.

I don't have SMS as 2FA for PayPal.

Re:Downsides of Google Authenticator by criddell on Friday February 28, 2020 @01:08PM (#22444849)
The offline backup can be a printout of the QR code.
Re:Downsides of Google Authenticator by lima on Friday February 28, 2020 @04:16PM (#22446449)
The best available solution is to implement WebAuthn support and allow users to add multiple devices. No backup code, no phishing.