Given the recent attack, I think this is a good opportunity to remind of the importance of using 2FA.
(although it doesn’t appear to make any difference in this case as session cookies were being exploited so login credentials were not needed)
But for me at least, this event has made me go back and take another shot at setting up 2FA.
I am happy to report I finally got it working on all my Lemmy accounts/instances, so I thought I’d share some tips:
I still haven’t figured out how to set up via desktop, use a mobile browser.
Follow these steps:
Check the enable 2fa box on your account settings and click Save
A message will show about a button appearing when the page refreshes
The button usually doesn’t appear for me at first.
You can simply manually refresh the page at this point to make the button appear
The button should now be visible. Click the button.
This opens a otpauth:// link which on a mobile device should be handled by a 2FA app if you have one installed.
Authy does not work: It will generate a code happily but that code will not work when you try to login to your Lemmy account.
Google Authenticator worked for me. It appears the type of TOTP code Lemmy is using is not compatible with some authenticator apps.
I think if you can find a desktop app that registers as a provider for the otpauth:// links it may be possible to do on desktop as well.
You can also pull the secret= value from the link to manually add it to an authenticator on/from desktop.
After several failed attempts previously, I finally figured out Authy was the problem and I have now secured all my Lemmy accounts with 2FA. Annoying that I have to use GA, but that appears to be an Authy issue not a Lemmy one.
2FA might not have made any difference today but it very well might in the future.
It may not be wise to enable 2FA until Lemmy fixes the implementation. It’s currently very easy to get permanently locked out of your account, through no fault of your own. Especially if you don’t have an email address linked to your account.
This happened to me. I was going to try it and when I saw that the option wasn’t what I expected, I intended to close it, but I guess either I didn’t or it’s buggy because it’s enabled now and there’s no encryption key, so no way to login. Then the server logged everyoner out cause of the hack. This was on lemmy.world, btw, I have an account on kbin too.
I sent an email, but no word yet obviously. I’m sure they’re busy.
If you are concerned, I would suggest keeping another browser/device/etc logged in when trying to enable 2FA.
Then if the 2FA activation fails, you can use that second session (which does not get logged out when you enable 2FA) to then disable it again.
For sure! But I don’t think non-advanced users should be enabling 2FA right now. It’s puzzling that Lemmy pushed the feature in its current state to production.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
A community to talk about the Fediverse and all it’s related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
Posts must be on topic.
Be respectful of others.
Cite the sources used for graphs and other statistics.
It may not be wise to enable 2FA until Lemmy fixes the implementation. It’s currently very easy to get permanently locked out of your account, through no fault of your own. Especially if you don’t have an email address linked to your account.
This happened to me. I was going to try it and when I saw that the option wasn’t what I expected, I intended to close it, but I guess either I didn’t or it’s buggy because it’s enabled now and there’s no encryption key, so no way to login. Then the server logged everyoner out cause of the hack. This was on lemmy.world, btw, I have an account on kbin too.
I sent an email, but no word yet obviously. I’m sure they’re busy.
Jeez, that sucks. Hope you get back in soon!
If you are concerned, I would suggest keeping another browser/device/etc logged in when trying to enable 2FA.
Then if the 2FA activation fails, you can use that second session (which does not get logged out when you enable 2FA) to then disable it again.
For sure! But I don’t think non-advanced users should be enabling 2FA right now. It’s puzzling that Lemmy pushed the feature in its current state to production.