I suspect AT&T (and others) don't do that because it'd be bad marketing to say "Hey! You're phone #'s aren't secure!" Petzl seems to have gotten over that problem, and is quite happy to warn you how you can kill yourself with their products.
-
-
This stuff has had plenty of coverage in very mainstream tech media: https://arstechnica.com/information-technology/2017/05/thieves-drain-2fa-protected-bank-accounts-by-abusing-ss7-routing-protocol/ … Again, that's a ridiculous argument.
-
...and we *know* they're aware of these problems, because phone companies offer services like account PINs to prevent them!
-
That only prevents a proper subset of the problems, of which they probably actually know only about a small fraction. It doesn't imply they have a solution or even know about the dizzying variety of other possible problems.
-
AT&T should be liable for $100-$10000 worth: a multiple of the money they are in contract for. Then, they could be expected to commit a percentage of that money towards security and insurance. It won't cover millions of accounts for $200,000,000 each, but maybe $1000.
-
Or you could actually let liability be defined by the contract and by the kind of product they offer. If people really want the phone companies to provide "identity" services for them, they should convince phone companies to provide such services and pay for them.
End of conversation
New conversation -
-
-
How come nobody is blaming the sites that allow phone based 2FA (Google, exchanges), aren't they the ones encouraging irresponsible behavior? "Secure your account with this" The phone service is merely a platform; I.e. If you store your keys on evernote it's not evernote's fault
-
I've said elsewhere in this thread that I also blame those exchanges, Coinbase in this case. To be clear, I think Coinbase should shoulder most of the responsibility here, with AT&T a minority part. That'd be socially useful too, as it'd reduce "race to the bottom" UX pressure.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.