(no title)
MaxGabriel | 1 year ago
To be clear this is what we're trying to avoid. An easily typeable code like that can be typed into a phisher's website.
MaxGabriel | 1 year ago
To be clear this is what we're trying to avoid. An easily typeable code like that can be typed into a phisher's website.
dpifke|1 year ago
I appreciate you guys are trying to protect people, but no other financial institution I deal with requires this level of annoyance, and at some point I'd rather switch to a less "secure," but more usable service.
(I put secure in scare quotes, because some suggestions, like trading true 2FA, where I have two separate secrets on two separate devices, for a single WebAuthn factor, are actually accomplishing the opposite, at least for those of us who don't click links in emails and don't use ads on Google for navigation.)
Edit to add: or maybe save the third factor for suspicious activity, such as "new device adding a new payee," rather than every signin. It's been months since I onboarded a new vendor, and I'd be OK with only having to do the cut-and-paste-the-link dance a couple of times a year, rather than every single time I want to check my balance.