Except when it’s just an email, or worse, a txt message, or worse, a whatsapp message, with no other option for using a proper 2fa generator…
But also, not every site needs 2fa, sometimes I really couldn’t care less if someone managed to hack into something, because I can just make a new account if that happened…
What really bugs me is that TOTP is objectively easier than any other form of 2fa. Just import the library, add the field on your login form, and you’re done.
Email verification is annoying to code, it requires SMTP or an email gateway, is slow for the user, is risky from a security perspective, and to generate the code you probably still have to implement TOTP.
SMS/RCS is even more annoying to code, it almost inevitably requires a third-party gateway, it can work differently if the user is in a different country or on a MVNO or in a low-signal area or just has the wrong astrological sign, is very slow for the end user, is almost useless from a security perspective, and you STILL have to implement TOTP.
WhatsApp messages are somehow even more annoying to code than that, requires an api interaction with Meta (which is never fun and poorly documented), requires the end user to have an account with a specific third party, is slow for the end user, relies on another company’s security posture to determine your own, and you STILL have to implement TOTP.
Making your own app for 2fa is undoubtedly the worst: not only is it annoying to code, it’s an ongoing annoyance that is strained through multiple app stores, adds an additional maintenance and support load, adds additional technical debt, adds an unnecessary attack vector, requires users to download another app, is often unreliable, is often pretty slow for the end user, is a total crapshoot from a security perspective, and guess what? YOU PROBABLY STILL HAVE TO IMPLEMENT TOTP.
Any company that chooses SMS or email verification over TOTP emphatically does not know what they’re doing.
2fa by email is probably slightly easier than TOTP, if the account verification via email is already implemented, but yeah, it’s not like it’s significantly easier…
But all of those data points are “cheap.” They already ask for email; I haven’t signed up for a service that didn’t require an email address in…thirty-ish years? Phone numbers are easily available on the dark web and essentially worthless to data brokers. A connection to WhatsApp would get you almost nothing, since Meta’s already sucking up all of that data. The custom app is the most potentially lucrative of those methods from a data perspective, but it’s also undoubtedly the costliest, which is why you see it the least often; you have to evaluate the ROI, and that algorithm is never favorable.
They don’t care about your security, that much is beyond doubt. And as a result nobody has updated that code since before TOTP was adopted, which I think is the real reason.
The real reason is conversion. The majority of users aren’t good at technology, so you risk them losing their TOTP secret. Then the user either just says “screw this site” and leaves, or they take time getting customer support to reset their key.
So depending on the branch and customer base, it can often be much “cheaper” in the end to send login codes via email instead of using TOTP.
Maybe. And I think that could make sense as the PM’s answer, but I also think that a TOTP app is starting to become mainstream enough that it’s not a huge deal.
You don’t have to implement totp for these alternatives… The “thing” about totp is that there’s a shared secret and a timestamp. Due to potential drift in clocks you need a window and period to know how many time steps to test, and how long each is.
But with an email/SMS/WhatsApp, there’s no shared secret. So you can simply send a random code, and store server side when it was generated. Totp makes no sense in that case.
Not that totp is difficult to implement at all. My implementation for work was what, less than 200 lines of C++ I think? I didn’t implement the sha1 myself though.
You do have to implement TOTP, just not necessarily RFC 6238. Time-based one-time passwords require a shared secret, a shared time and a time-to-live. The shared secret is usually the key for generating the code, but can be the code itself. The shared time is still needed in mail authentication between the code generator and the code validator. The thing that’s usually different is the time to live, but in RFC 6238 it is a parameter, so you can implement mail verification with it and a long TTL.
An earlier version of that comment said “something like TOTP,” but I guess I left that out while I was revising it. My point is you have to implement something that does most of what TOTP does anyway, so why not just use the version that’s already been stress tested?
Seriously. Why would i care if someone logs into most of them. What are they going to do watch a movie on my Netflix account, play my kids roblox games, or change my crew on my Rockstar account? It’s unnecessary bs.
Which also doesn’t matter anymore because companies sell our data all the time or just give it away through their own data insecurities. Or yanno, white pages. com and similar exists and its pretty easy to find anything about anyone anytime.
Yeah, and when you call somewhere else to have service do something manually to your own account, they verify your identity via birthday, address, and the last 4 digits of your card…
Funny story. In Australia the government just transitioned to voice authentication. Then A.I. deepfake happened and they had to undo it 😂
Fr though, it’s a huge problem that phone authentication boils down to information that’s in every data broker in the planet. One company I deal with uses SMS authentication over the phone which isn’t much better security-wise but at least it’s not something public knowledge
These days a lot of sites outsource transactions (and thus credit cards), but older/smaller sites may well be storing full credit card information. The rules/laws around that vary a lot buy jurisdiction.
Yea but like if I go to my billing section you can’t just copy paste the number let alone the cvc or expiry date. So even if they store it, mentioning credit cards is kind of pointless unless there’s additional exploits involved
I don’t care. Likelihood is that’s not going to actually cause me anything but an annoyance anyway, so the cost of preventing it can’t be more annoying
Any account that does payment (like your netflix one), will be used to test out stolen credit cards. This will in turn flag your account for fraud. You might not want that. Unless you do, I don’t know
It will be a problem for you when the police decide it’s a civil issue (which they most likely will). Whether the credit card company will help you with this really depends on their policies, and I’m not sure what Netflix is supposed to do about it.
If they said it was a civil issue, that’d mean no charges against me, which would be even better because then I could just make a different netflix account and have no legal issues.
Idk man. I just don’t think it’s a big deal for me.
It’s not about a specific account, it’s about compromising your info.
The info one company considers enough to verify you when you call or chat with customer service, another company will give out freely. They can then hop and skip through those to get access to one of your accounts they actually want.
Your entire online security is only as secure as your most insecure account.
Well yeah, Netflix knows it’s super annoying when your watch history gets messed up. This is the real reason why Netflix (and all the other tech companies) are suddenly pushing so hard for passkeys… it has nothing to do with how much control and influence it’ll give them ;-)
Tell me that at least you use different email and password for every account because if not, then you just get screwed when they hack one account, also, if any of your social accounts gets hacked, it will for sure be used to scam or hack other people.
And usually, the alternative is a text message to a phone, with most temporary number providers blocked.
Nobody really designed it, and there are ways around it, with some tradeoffs, but specific account -> email -> phone -> bank -> legal identity is the typical authentication chain that’s evolved. It’s because any way of signing up that’s too repeatable gets saturated with bots and spammers.
Can we agree that 43-factor authentication would be bad, at least?
Like, it’d pretty weird if it actually happened, but if you start relying on another service that itself relies on another service as one of the factors, you’re opening the door to that.
My work 2fa can go away. I don’t give two shits if everything in the work app is printed in global papers, just stop making me go through a 5 step process to see my fucking roster.
Every time I have to fill out a 2FA at work, I die inside.
Bro, I am not a nVidia CEO, no Chinese spies are interested in the shit on my work computer. Also why do I need 7 different logins for the 7 apps we use, none of which are of any critical importance, none sharing the same password requirements.
Fuck that, IT. My passwords are taped to my monitor.
Almost all sites should allow me to choose whether I want 2fac. And they shouldn’t prompt for it nearly as often as they do - some services do it for every login, most seem to do it every month at least.
yes I do. I will take convivence over security most days. Just because you don’t, and you have good reasons to want it to stay, doesn’t mean everyone comes to the same conclusion based on similar data.
Although I personally think 2FA is very important in most cases, I agree that mandatory 2FA is annoying. If you want to forego security for convenience, that should be up to you. I’m sure you’re not stupid or ignorant of the risks.
as a developer it is incredibly frustrating and time consuming
Huh? How? Implementing OTP (which I’m assuming most people here are talking about) is pretty trivial, and once you have it set up, it doesn’t require much maintenance.
It fails for somebody every day, it adds a dependency for a known unreliable 3rd party that often mangles the identification data it sends back, it is exploited by that 3rd party for extending their monopoly, and it gives that 3rd party (or any hacker that got access to them) full access to impersonate any user it wants.
That’s the user’s choice, that should not be a consideration when choosing authentication methods as long as you tell them how to store it properly (in a reasonable way, probably shouldn’t mention keepass or anything like that).
in a reasonable way, probably shouldn’t mention keepass or anything like that
I avoid all those big tech sites advocating passkeys in recent times anyway, so I did not really have much chance to test it. But my password manager at least seems to be able to properly store and backup passkeys. It’s the import/export should I want to use other software that seems to be universally lacking still.
Who doesn’t use TOTP/HOTP? The brain-less part usually comes into play when they then recommed (or even require…) propietary shit like Google’s authenticator app as if there weren’t enough secure and open source options.
Amazon, Facebook, and many more support TOTP in whatever authenticator you want. I don’t particularly like either of those websites but they are massive and directly contradict your claim that no corporation uses this normal method of 2FA.
This is uterly idiotic but ok. I have decided I do not need to wear seat belt in the car. Just because you do and you have good reasons to want it to stay, doesn’t mean everyone comes to the same conclusion based on similar data.
The day my taxes go towards paying for people who don’t have 2fa, we can discuss whether it should be mandatory. Also, comparing a compromised Netflix account to loss of life, really?
2FA is a good thing. You don’t want it to go away.
I don’t think the 2FA is the issue this comic is attempting to convey.
Except that it needs another jump for autofill 2fa
2FA on the login form is a thing for some sites,
Except when it’s just an email, or worse, a txt message, or worse, a whatsapp message, with no other option for using a proper 2fa generator…
But also, not every site needs 2fa, sometimes I really couldn’t care less if someone managed to hack into something, because I can just make a new account if that happened…
What really bugs me is that TOTP is objectively easier than any other form of 2fa. Just import the library, add the field on your login form, and you’re done.
Any company that chooses SMS or email verification over TOTP emphatically does not know what they’re doing.
2fa by email is probably slightly easier than TOTP, if the account verification via email is already implemented, but yeah, it’s not like it’s significantly easier…
That is a fair point. But again, you probably have to implement TOTP or something like it anyway, to generate the code.
They know: they’re selling your data. They don’t mind about your security
But all of those data points are “cheap.” They already ask for email; I haven’t signed up for a service that didn’t require an email address in…thirty-ish years? Phone numbers are easily available on the dark web and essentially worthless to data brokers. A connection to WhatsApp would get you almost nothing, since Meta’s already sucking up all of that data. The custom app is the most potentially lucrative of those methods from a data perspective, but it’s also undoubtedly the costliest, which is why you see it the least often; you have to evaluate the ROI, and that algorithm is never favorable.
They don’t care about your security, that much is beyond doubt. And as a result nobody has updated that code since before TOTP was adopted, which I think is the real reason.
Well, you have a point, I have to admit. 🤝
The real reason is conversion. The majority of users aren’t good at technology, so you risk them losing their TOTP secret. Then the user either just says “screw this site” and leaves, or they take time getting customer support to reset their key.
So depending on the branch and customer base, it can often be much “cheaper” in the end to send login codes via email instead of using TOTP.
Maybe. And I think that could make sense as the PM’s answer, but I also think that a TOTP app is starting to become mainstream enough that it’s not a huge deal.
You don’t have to implement totp for these alternatives… The “thing” about totp is that there’s a shared secret and a timestamp. Due to potential drift in clocks you need a window and period to know how many time steps to test, and how long each is.
But with an email/SMS/WhatsApp, there’s no shared secret. So you can simply send a random code, and store server side when it was generated. Totp makes no sense in that case.
Not that totp is difficult to implement at all. My implementation for work was what, less than 200 lines of C++ I think? I didn’t implement the sha1 myself though.
You do have to implement TOTP, just not necessarily RFC 6238. Time-based one-time passwords require a shared secret, a shared time and a time-to-live. The shared secret is usually the key for generating the code, but can be the code itself. The shared time is still needed in mail authentication between the code generator and the code validator. The thing that’s usually different is the time to live, but in RFC 6238 it is a parameter, so you can implement mail verification with it and a long TTL.
An earlier version of that comment said “something like TOTP,” but I guess I left that out while I was revising it. My point is you have to implement something that does most of what TOTP does anyway, so why not just use the version that’s already been stress tested?
A local marketplace service in brazil only allows me to login using whatsapp codes or sms. When i enter the passowrd they ask for a whatsapp code
I don’t want it for like 95% of the logins I have.
Seriously. Why would i care if someone logs into most of them. What are they going to do watch a movie on my Netflix account, play my kids roblox games, or change my crew on my Rockstar account? It’s unnecessary bs.
The bigger issue is gaining account details and personal info for identity theft.
Which also doesn’t matter anymore because companies sell our data all the time or just give it away through their own data insecurities. Or yanno, white pages. com and similar exists and its pretty easy to find anything about anyone anytime.
They don’t sell your ID or credit card information though, which is information a lot of these kinds of services have.
You can’t download your ID or credit card information though lol. Sometimes it shows the last 4 digits in the billing section
Yeah, and when you call somewhere else to have service do something manually to your own account, they verify your identity via birthday, address, and the last 4 digits of your card…
Funny story. In Australia the government just transitioned to voice authentication. Then A.I. deepfake happened and they had to undo it 😂
Fr though, it’s a huge problem that phone authentication boils down to information that’s in every data broker in the planet. One company I deal with uses SMS authentication over the phone which isn’t much better security-wise but at least it’s not something public knowledge
These days a lot of sites outsource transactions (and thus credit cards), but older/smaller sites may well be storing full credit card information. The rules/laws around that vary a lot buy jurisdiction.
Yea but like if I go to my billing section you can’t just copy paste the number let alone the cvc or expiry date. So even if they store it, mentioning credit cards is kind of pointless unless there’s additional exploits involved
Who cares if someone steals your identity? Just go on the dark web and buy a new one.
I don’t care. Likelihood is that’s not going to actually cause me anything but an annoyance anyway, so the cost of preventing it can’t be more annoying
Any account that does payment (like your netflix one), will be used to test out stolen credit cards. This will in turn flag your account for fraud. You might not want that. Unless you do, I don’t know
What? Like they’d try and use a stolen credit card to pay for my service?
They won’t be paying, just tokenizing the cards to see if the data is good.
Sounds like it wouldn’t be a problem at all, for me, and really a problem for the police or netflix or the credit card company.
It will be a problem for you when the police decide it’s a civil issue (which they most likely will). Whether the credit card company will help you with this really depends on their policies, and I’m not sure what Netflix is supposed to do about it.
If they said it was a civil issue, that’d mean no charges against me, which would be even better because then I could just make a different netflix account and have no legal issues.
Idk man. I just don’t think it’s a big deal for me.
deleted by creator
It’s not about a specific account, it’s about compromising your info.
The info one company considers enough to verify you when you call or chat with customer service, another company will give out freely. They can then hop and skip through those to get access to one of your accounts they actually want.
Your entire online security is only as secure as your most insecure account.
Well yeah, Netflix knows it’s super annoying when your watch history gets messed up. This is the real reason why Netflix (and all the other tech companies) are suddenly pushing so hard for passkeys… it has nothing to do with how much control and influence it’ll give them ;-)
Tell me that at least you use different email and password for every account because if not, then you just get screwed when they hack one account, also, if any of your social accounts gets hacked, it will for sure be used to scam or hack other people.
I use the same password where it doesn’t matter at all.
I use different passwords where it matters or where my usual password doesn’t work or was required to be changed.
There are 3 things where I don’t even save the password in a password manager. It stays in my wet memory. They are:
I get the theory, but if it itself relies on some login-based service (like email) it becomes a kind of chicken and egg problem.
Reminds me of all the times I’ve run into “Please provide another email address we can use to verify your signup for this email address.”
So I can’t have an email address unless I already have an email address. It’s the most asinine thing
And usually, the alternative is a text message to a phone, with most temporary number providers blocked.
Nobody really designed it, and there are ways around it, with some tradeoffs, but specific account -> email -> phone -> bank -> legal identity is the typical authentication chain that’s evolved. It’s because any way of signing up that’s too repeatable gets saturated with bots and spammers.
E-mail based 2fa isn’t good, but at least it’s better than having no 2nd factor at all.
Can we agree that 43-factor authentication would be bad, at least?
Like, it’d pretty weird if it actually happened, but if you start relying on another service that itself relies on another service as one of the factors, you’re opening the door to that.
My work 2fa can go away. I don’t give two shits if everything in the work app is printed in global papers, just stop making me go through a 5 step process to see my fucking roster.
Every time I have to fill out a 2FA at work, I die inside.
Bro, I am not a nVidia CEO, no Chinese spies are interested in the shit on my work computer. Also why do I need 7 different logins for the 7 apps we use, none of which are of any critical importance, none sharing the same password requirements.
Fuck that, IT. My passwords are taped to my monitor.
Almost all sites should allow me to choose whether I want 2fac. And they shouldn’t prompt for it nearly as often as they do - some services do it for every login, most seem to do it every month at least.
yes I do. I will take convivence over security most days. Just because you don’t, and you have good reasons to want it to stay, doesn’t mean everyone comes to the same conclusion based on similar data.
Although I personally think 2FA is very important in most cases, I agree that mandatory 2FA is annoying. If you want to forego security for convenience, that should be up to you. I’m sure you’re not stupid or ignorant of the risks.
As a user its annoying, as a developer it is incredibly frustrating and time consuming.
Huh? How? Implementing OTP (which I’m assuming most people here are talking about) is pretty trivial, and once you have it set up, it doesn’t require much maintenance.
It fails for somebody every day, it adds a dependency for a known unreliable 3rd party that often mangles the identification data it sends back, it is exploited by that 3rd party for extending their monopoly, and it gives that 3rd party (or any hacker that got access to them) full access to impersonate any user it wants.
What?
Implement TOTP and let your users use their preferred authenticator and none of what you’re struggling with will apply.
Which also means you can just copy/paste it alongside username and password with the same manager.
👆️
That’s the user’s choice, that should not be a consideration when choosing authentication methods as long as you tell them how to store it properly (in a reasonable way, probably shouldn’t mention keepass or anything like that).
I avoid all those big tech sites advocating passkeys in recent times anyway, so I did not really have much chance to test it. But my password manager at least seems to be able to properly store and backup passkeys. It’s the import/export should I want to use other software that seems to be universally lacking still.
Oh, yeah, and of course there’s someone on the internet talking about the MFA protocol that no corporation uses.
That one is obligatory too.
(Anyway, yes, if you need MFA, use TOTP. That’s a non-brainier. Except that corporations don’t have brains.)
Who doesn’t use TOTP/HOTP? The brain-less part usually comes into play when they then recommed (or even require…) propietary shit like Google’s authenticator app as if there weren’t enough secure and open source options.
Amazon, Facebook, and many more support TOTP in whatever authenticator you want. I don’t particularly like either of those websites but they are massive and directly contradict your claim that no corporation uses this normal method of 2FA.
This is uterly idiotic but ok. I have decided I do not need to wear seat belt in the car. Just because you do and you have good reasons to want it to stay, doesn’t mean everyone comes to the same conclusion based on similar data.
there, now you are getting it.
i dont want you not wearing the seatbelt, it is so easy to do
we live in a society and im tired of paying for stupid doing stupid things
The day my taxes go towards paying for people who don’t have 2fa, we can discuss whether it should be mandatory. Also, comparing a compromised Netflix account to loss of life, really?
comparing cost to society
there is a reason ms forces updates now
Good thing you aren’t in charge of anything, then.
Click login button -> Autofill username, password & totp token -> Done
(And staying signed in not working is an intentional side effect of deleting cookies and temp data on closing the browser…)