Good - 2FA is the responsibility of the user and resetting it kind of invalidates the security it helps bring. I think the bigger issue is that people's 2fa codes are still tied to their phone. You can lose your phone at any moment, which is why i've always disliked apps like Google Authenticator which don't let you export 2fa keys (for good reason). I personally use 1password, but there's definitely room for a cloud…
Google Authenticator now allows you to export your keys to another phone. I keep my keys in analog form - I print QR code for every service. We know how to handle valuables stored on paper.
Gitlab Support is no longer processing MFA resets for free users
131–140 of 228 posts
Re: Gitlab Support is no longer processing MFA resets for free users
#132Earlier quoted context omitted.
Would you be willing to describe the process you use to do this?
Not op, but my usual process is: * when setting up 2FA, a website shows a QR code * I screenshot the QR code, and print it out on an A4 sheet, with an annotation of what service it is for * I scan the QR code from the A4 sheet on two different phones. * Back on the website, I continue 2FA setup process only after the A4 sheet is printed, and both phones show the same codes * The A4 sheet goes in a folder for safe kee…
Re: Gitlab Support is no longer processing MFA resets for free users
#133Good - 2FA is the responsibility of the user and resetting it kind of invalidates the security it helps bring. I think the bigger issue is that people's 2fa codes are still tied to their phone. You can lose your phone at any moment, which is why i've always disliked apps like Google Authenticator which don't let you export 2fa keys (for good reason). I personally use 1password, but there's definitely room for a cloud…
The problem with storing the 2FA keys in 1Password is that you're practically downgrading your account to 1FA because once 1Password is compromised, the second factor lost all of its value, though that compromise is much harder to achieve than a compromised shared machine I'm typing my password in on (which you probably also should never do). I'm saying this as I'm looking at my 1Password database which also contains…
Re: Gitlab Support is no longer processing MFA resets for free users
#134Although framed as a security improvement, I'm sure it's also a massive support burden. When you have hundreds of thousands or millions of users, at some point you probably have support staff who do nothing but helping users reset their MFAs all day every day. It seems fair not to do this for free users. Some services gate MFA to paid accounts which seems like a worse trade-off. With free users you also have less inf…
Re: Gitlab Support is no longer processing MFA resets for free users
#135Earlier quoted context omitted.
Support Manager at GitLab here. We did use to do identity card verification. The issue that we had was that we often didn't have a lot of information about the folks who opened free accounts. Often names would be pseudonyms or match only partially with their ID. Not to mention, of course, the difficulty of verifying the authenticity of IDs from all over the world. We wrote about this back in 2018: https://about.gitla…
I suspect that support cost also played into the decision. Consider requiring payment: It covers your support costs, and provides some ties to a real-world identity as well as rate limiting/imposing a real cost on attackers. For credit cards, AFAIK you can set which security level to apply (i.e. whether you'd rather have a higher fraud risk or more shopping cart abandonement because the customer didn't have/want to d…
I respect this if it’s the case, but just say it, don’t hide behind a “best practice” security blanket when your true motive includes other factors.
> If there is no way to recover, it creates a perverse incentive to not use 2FA in the first place.
Agree. The user has to now perform a cost benefit analysis in her head to determine if she’ll use MFA with the most punitive risk being she loses access to her account forever.
Re: Gitlab Support is no longer processing MFA resets for free users
#136Earlier quoted context omitted.
Sites should be migrating to WebAuthn (and please people do not implement U2F instead of WebAuthn in 2020, for the same reason you wouldn't build a new Flash video site, nothing new supports that technology any more, stop it) I think this is terrible advice because WebAuthn isn't supported by Linux browsers and I still want to be able to login to services on the internet.
Which "Linux browsers" are you thinking of? Firefox only implements WebAuthn, including on Linux, the U2F support in Firefox is essentially a "reverse polyfill" in which the browser pretends it can do U2F but actually is just wiring some commonly used parts of U2F to the WebAuthn implementation to tide you over until your site gets WebAuthn. Chrome on Linux certainly supports WebAuthn although it does have U2F suppor…
https://demo.yubico.com/webauthn
Is this a problem with the backend rather the browser?
Edit: This site works https://webauthn.io/ My mistake!
Re: Gitlab Support is no longer processing MFA resets for free users
#137Good - 2FA is the responsibility of the user and resetting it kind of invalidates the security it helps bring. I think the bigger issue is that people's 2fa codes are still tied to their phone. You can lose your phone at any moment, which is why i've always disliked apps like Google Authenticator which don't let you export 2fa keys (for good reason). I personally use 1password, but there's definitely room for a cloud…
> Good - 2FA is the responsibility of the user and resetting it kind of invalidates the security it helps bring. Actually, no. This is a terrible idea. Think about the psychology of what you are telling people: "You have two choices - one is normal security, which you use on 80%+ of the rest of the internet, and one is 2fa which you only use on the annoying services that badger you into it. On the first one, if you l…
I would argue that this is a negative thing. Sites should at least give the option to disable password reset.
Re: Gitlab Support is no longer processing MFA resets for free users
#138Earlier quoted context omitted.
> Good - 2FA is the responsibility of the user and resetting it kind of invalidates the security it helps bring. Actually, no. This is a terrible idea. Think about the psychology of what you are telling people: "You have two choices - one is normal security, which you use on 80%+ of the rest of the internet, and one is 2fa which you only use on the annoying services that badger you into it. On the first one, if you l…
> if you lose your password you can do a password reset I would argue that this is a negative thing. Sites should at least give the option to disable password reset.
Re: Gitlab Support is no longer processing MFA resets for free users
#139Earlier quoted context omitted.
Screenshot the QR Code and print it? Put it in a vault or store somewhere safe. It’s a standard practice for securing enterprise accounts (AWS root acc. for example)
You can't screenshot it. The app puts a no screenshot request, so you have to scan the qr code from another phone.
Re: Gitlab Support is no longer processing MFA resets for free users
#140Earlier quoted context omitted.
It makes your MFA-protected account safer from takeover, but also creates a new risk of completely losing access to your account and username forever. Github has the same policy, and it deterred me from using MFA for a long time, and when I finally did, I added a large number of alternatives, including the not-so-secure SMS. I think the fear of being temporarily unable to access your account is already a major reason…
> ... but also creates a new risk of completely losing access to your account and username forever. I may have misread the announcement, but it sounds like upgrading to a paid account recovers (npi) the ability to recover your account.