this post was submitted on 10 Jul 2023
78 points (96.4% liked)

Fediverse

28518 readers
389 users here now

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

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 2 years ago
MODERATORS
78
submitted 1 year ago* (last edited 1 year ago) by Rootiest to c/fediverse
 

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.

Stay safe everyone! ๐Ÿ”

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 1 year ago

The TOTP feature in Bitwarden works, if you paste in the whole otpauth:// URI to Bitwarden's Authenticator Key (TOTP) field. The URL specifies that the hashing algorithm should be SHA256. If you just import the secret= value into Authy, it probably defaults to using the SHA-1 algorithm, which may be why the codes generated by Authy don't work.

SHA256 is more secure than SHA-1, which I guess is why Lemmy has chosen to use it for its 2FA feature.