MFA

SMS: Here is your 30s "MFA" code, I'll send it to you 40 minutes after you need it.
SMS isn't 2FA. Its 1.5FA.
- SMS isn’t even secure. Mitm, social engineering, straight up theft, and more are all ways around it. It should never have been implemented, but especially not when totp exists.
  
  What I despise most in when SMS is not just optional but forced upon me as "backup" to TOTP. "Lost your authenticator app? Send an SMS instead." How about no?
- Dude.
  My wife's phone started acting up the other day. It would keep losing cell service and even when it showed a signal, it still would only work on wifi.
  That happened a few hours after I ported my phone number (on the same family plan) to another carrier. So naturally, I thought the issue was with the carrier.
  Since I planned on porting her number out to my new carrier anyway, I didn't want to troubleshoot.
  Well, get to the new carrier and it's still not working. Go through the whole process of resetting network settings, and then eventually deleting the esim.
  New carrier, though, needs you to receive a text message before they send the esim.
  Naturally, with the esim deleted, it couldn't receive text messages.
  Her issue did end up being her phone. Even after the port went through in full, it was still hit-or-miss with cell service. Worked on wifi though.
- I've heard people in the US still use SMS to communicate with eachother. Fucking crazy.
  
  Only when iPhone users need to send a message to literally anyone else.
  
  Inertia and ease of use are powerful.
  SMS "just works" and works for everyone here.
  While I would like the new fancy features. At least RCS is bringing some and is seamlessly integrated.
  Bonus I have 10+ years of txt history and can scroll/search to find something. And since my phone is Google (I know evil) I can access it all from the desktop seamlessly in one window.
  
  uhhh that's not some unique american thing lol, that's how people here in sweden communicate too
  Barely anyone cares what specific protocol is being used, they just care about what app they have to use and who they can reach, and if anyone isn't using a normal sms app they're generally using facebook messenger or imessages both of which support sms fallback and thus their users don't even know there's a difference half the time.
  
  why not
  
  Blame apple for that. IPhone has this proprietary messaging app pre-installed which is probably super convinient for the ecosystem but uses some obsolete SMS protocol to communicate with android phones. I think recently this has gotten better, but only because beeper and the EU pressing on them
- SMS is good enough. Sure it's not as authenticator or some other MFA method, but it's good enough. Chances of my random account hiding something worth subverting cell operator to get the SMS and my password, are slim to none. At that point don't upload anything worth that much.
- Buy a real phone service. I don't ever remember missing a code.
  
  It's overwhelmingly whatever provider they use for SMS, or some sort of anti spam checking.
  My phone has reception the whole time.

At least it isn't email or SMS MFA.
- Or email OFA. Burger King, Popeyes (I know they are the same company), and just a bit ago, BuyMeACoffee. They let you enter a password; fuck if I know what their requirements are. No tooltip, no failure text. 60 char with special chars? Nope. (a few moments later) 20 chars with no special chars? Nope. Fuck it, let's try 2FA. Get seed, generate code, go to setup verification page (on phone), first box, paste. ONLY THE FIRST NUMBER PASTES AND MY KEYBOARD CLOSES. SCREAMS
  (only factor authentication)
  
  Nothing compared to BOFA, which is arguably even worse and a lot more stupid
- My bank requires SMS mfa
  Admittedly I kind of see why
  
  My bank has its own authenticator app, which doesn't work on my phone. Piece of crap. They now enabled fingerprint login without additional 2FA somehow, and I can also authorise payments with biometrics. Only to change my limits, update address etc. I have to use the app (on an old Pixel 3a as a standby device just for this purpose).
  
  Why?
  Totp is easier, cheaper, and more secure. It makes no sense to go with SMS.

I agree with this sentiment. Steam notably falls into the third category, while otherwise being pretty good.
But I'm quite disgusted now seeing an image of a Yubikey for the first time. I've heard so many good things about them that it's a major disappointment to see now that they use that awful noncomplaint shape of USB plug.
There are two very important reasons for the metal shield around USB plugs: 1. For ESD protection, and 2. to hold the receptacle's tongue in place and prevent it from bending away and losing contact. Every USB device I've owned that was a flat plug (like this Yubikey image in this post) has within a month deformed the USB receptacle it's plugged into to the point that the device no longer works in that port. Compliant USB devices still work in that port's deformed receptacle, because they have a correct metal shield that bends the tongue back into the correct position.
- Yubikey also has usb-c versions with compliant plugs.
- YubiKeys have almost every imaginable form factor these days. Here's the USB-C version without NFC:
  
  Yeah I have an even smaller USB-C one. It sticks out less than 0.5cm from the port.
- No problems with yubikeys or the receptacle they are plugged into yet.. no idea what you do while these sticks are plugged in.. doesnt seem like a major concern per the reviews
- I've had my ubikey fido2 token knocking around on my keychain for about 7 years now. Scratched and beaten, works perfectly and never had a port damaged, it doesn't put enough pressure on it.
- It is kind of annoying that Steam doesn't enable the usage of third-party OTP apps. To be fair, when they first implemented the feature, that wasn't widely used and plenty of websites only enabled the use of one specific OTP app like Authy or Google Authenticator. They recently added a QR code login feature, which makes sense, but that still shouldn't stop them from enabling MFA via third party OTP apps.
  
  Some third party apps allow you to import your Steam OTP, such as Gnome Authenticator
  However to obtain it in the first place you need to either use SteamDesktopAuthenticator (GitHub), an android emulator on your PC, or a rooted device to export your key...
- iirc it's possible to somehow export the secret key used by steams 2fa
  
  It absolutely is, the issue is that most mfa apps spit out 6 character outputs, while Steam requires 5. They’d need to implement the alternative algorithm, but 1password for instance flat out refuses since it’s non standard.
- It is actually possible to use Aegis for Steam, that's what I do. It's a pain to setup if you're not rooted (I think you need to use an Android emulator on a computer and then export the Aegis DB to reimport it on your mobile IIRC) but it's possible. Look at https://github.com/beemdevelopment/Aegis/wiki/Adding-Steam-to-Aegis-from-Steam-Desktop-Authenticator Steam is still very welcome to go fuck themselves with their shitty app, though.
  
  can we please make shitty MFA illegal? Where is the EU and the US government when you need them.
- I think the good people at yubikey want to provide people with every possible form factor, for whatever is convenient for them.
  If your organization issued you a yubikey, but you don't like the form factor, I'm sure you could purchase your own and have them add it instead.
  You can also use a USB extension cable, to add a bunch of flexibility between your yubi key and your computer, especially if you leave it always attached. That would remove the lever problem you mentioned

Uuuuugh. I just had this problem after dropping my phone. Can't log into the phone without the phone being logged in. Solution: disable 2fa on a logged in device. If I can disable it from another device why can't I verify it from another device? This is so broken!

my favorite instance of google MFA was when i went to log into my google account for some reason. Google hit me with the MFA, cool whatever, i'll MFA, google does the usual "heres how we do it because we give you no options because fuck you" and im like, cool, ok just gotta wait for this to work.
And then it proceeds to not work, at all. Thanks google, very cool. Fortunately, i had a secondary auth app setup so i used that, and it worked, weird how that works huh? BTW, it wasn't sms, it's googles integrated android MFA service, which as far as i can tell, is literally a fucking requirement to using MFA.
Also, i remembered again, that logging into my google account, automatically logs me into every google account i have. Yknow, because security. Anybody know how to disable that one btw? Google seems to be an endless labyrinth of options everytime i try and do something with it so.
- logging into one google account does not log me into all my google accounts, as far as I know

Wait, can you eli5 why multifactor authentication (MFA) (and maybe also 2-factor authentication apps) is “fuck off” levels?
Is it privacy concerns or something bigger like more points of failure for overall security? Or smaller like not every one has/wants a smart phone?
- If I read it correctly the "fuck off" level refers to some proprietary app for the selected login. The other two are standard code app and yubikey.
  
  This is also how I read the meme. Codes are fine, tokens are fine. Your proprietary spyware app is NOT fine (Microsoft) and I hope you get fucked.
  
  I was reading it as "it never fucking works right" LMAO
- I already have an authenticator app. If some service wants to force me to install their own app for their login, they are indeed welcome to fuck off.
- Standard authenticator (software or hardware) are, well, standard. You can pick anything compliant and use it with any compliant service. Requiring a specific app means that you have to install yet another app, which may or may not be well made, and may or may not snoop on you, and usually will only work with one service, assuming you have a compatible device to run it to begin with.
  It's more than an inconvenience; not insurmountable, but way more work than just having a standard thing that works perfectly well and is based on known and proven algorithms.
  
  Don't forget the dark pattern, where they need to allow push notifications to get two factor to work, but those same push notifications are now used to badger the user and create more advertisement touch points
- I can try:
  You see, a lot of really smart people worked very hard to make standardized multifactor authentication so different companies can make products that work with the MFA on different sites and services.
  The standardized versions are very cross compatible and very very secure.
  Some dumb dumbs want to be different and make you install some application on your smartphone so that you can do the exact same thing but only for their site/service. This is widely considered a bad idea, and it makes people sad. Having to install yet another app, just so you can do something that could, and should be possible with the very good existing technology that's been created by those very smart people I mentioned before, is stupid, inconvenient, and frustrating for anyone who understands how these things work, and how secure they actually are.
  Since the app that the dumb dumbs made was created by them, for them, and they don't share how that app functions, it can very justly cause concern with those that enjoy their privacy, since the app could be doing any number of potentially nefarious things. When you compare that with the known and trusted methods of authentication created by the smart people, it's understandable that people would not appreciate having to use some proprietary application to do something that's already able to be done in a safe and predictable way.
  .... I think I may have used too many big words. You did ask me to eli5....

At work usually I can login without any input thanks to SSO, but occasionally it will ask for a security check. The default is to press a notification in outlook on my work phone, which I only ever use when travelling, so it's invariably off... 🙄
- My work has something similar, but I can change the default.

My brain needs to boot faster. Took me far too long to figure out that wasn't Mother Fucking Authentication, and was instead more likely Multi-Factor
- You are doing gods work sir!

Fuck Duo authenticator and its proprietary ass shit

im definitely an idiot but i couldn't figure out at all how to make a yubikey work with a keepass database on android
- Yubikey is only really useful for authentication with a trusted party, and not decryption. You can technically use store a secret key on it but then its two biggest advantages are gone, namely that you can't copy the key and that it doesn't use the limited storage on the device.
  
  The yubikey can perform a hmac using a secret (supposedly) only available to the key's internals. This is used in addition to the password, so that knowledge of the password without the key, or the key without knowledge of the password, can't be used to decrypt the database. It's kind of a half second factor (I know it's not technically correct to call it that, but I hope you get the idea).
  It's also in their doc (that they use challenge/response): https://keepassxc.org/docs/ and is even featured on yubico's website, which is somewhat weird but why not: https://www.yubico.com/works-with-yubikey/catalog/keepassxc/#tech-specs
  The issue GP had is probably that the keepass app does not support it on Android.
  
  What? They are super-usefully for decryption, specifically because of the inability to copy the key.
- This works for me on KeepassXC / Keepass2Android, and it looks like Yubico has instructions for original Keepass.
  
  thank you, ill give it another shot
- I'm a bit confused. What are you trying to get the yubikey to do?
  
  i use keepass to store all my passwords, the database file gets synced across my devices through Dropbox, i open it with a master password, i would like to improve this by also requiring the yubikey
  i am kind of confused too as to what exactly the yubikey does in this scenario. my vague understanding is that it was somehow synchronized such that the yubikey would generate sequential random 'passwords' which would be checked against the database file (generating its own sequence in the same manner).
  i think it stopped working due to some desynchronization between the yubikey and the database file.

Agreed

MFML.

Passkeys gonna fix all this bullshit.
- No they fucking won't. You know that websites are going to be massive throbbing cocks about it.
  "Due to security issues, passkeys for our service must be kept in
  <Company name>
  ® Secure Passkey App™. Please install the app on your device to continue. This app requires Apple Notification or Google Play services to operate. Must have verified phone number to use."
  
  "Your device has been rooted and therefore cannot be supported."
  
  Fair enough!
  
  Passkeys are an open standard. You need to install a Webauthn-compliant supplicant that talks to the browser. The supplicant can be anything, as long as it does the required protocol. The browser doesn't care.
  At the moment the browsers are the main problem. They need to open their APIs properly.
  
  Please make your device unsecure to give your account the illusion of security.

Sorry, as IT person I have to disagree, app based MFA is just way much easier to maintain instead of HW keys.
Edit: forgot to mention that in Finland companies here has to provide phone if your work require that. In IT I don't want nothing to do with users personal devices, and it sounds insane to me that in US companies force apps to your personal devices.
- If you want to install software on my personal device with elevated privileges then I'll just use a different service than your shitty low effort maintained trash.
  
  Company device of course. Like mentioned, in IT, I want nothing to do with users personal phones
- I've had this argument with different people when asking for a hardware token vs app only two factor.
  I'm not installing a proprietary app on my personal device. I'll use a open standard, I'll use a light weight hardware token. I'm not going to run a invasive binary black box for push authentication 24/7 on my personal device.
  At this point everyone has extra phones that don't get security updates. I just used a old phone installed the app on that phone, and left it in my desk... It's kind of a terrible security dongle at this point.
  
  Has to be company phone of course. In IT I don't want nothing to do with your personal device.
  Here in Finland it is normal (or even required) that company provides you phone and subscription if your work needs that.
- Re-writing a 6-digit code is easier than tapping a USB device?
  
  They're talking about operationally. They don't want to configure and distribute a bajillion dongles to users.
  
  Often times, yes. I don't want to always have to have a USB key on me, but I always have access to MFA apps via my phone, watch, or laptop. I have no idea why you're typing the code out instead of copying and pasting.
  
  Open an app, find the one number for your specific app among the bajillion you have, oh the timer is almost out and you forgot halfway through, tap back in the app, oh the fucking app scroll all the way to the top again.
  
  Pretty sure he's talking about mfa that just asks for confirmation whether that's you logging in on the phone. No typing required.
- App-based TOTP are not phishing resistant and do not require any level of proximity to the login session. The future is more likely passkeys that use device TPMs.
  
  Simple challenge number handles that, for example Azure AD MFA forces that today