If you are an Admin of a Lemmy instance, please use it to help secure your account!
Admins yes. But maybe regular users should avoid Lemmy’s 2FA implementation for now (unless they have lots of experience with this).
With the current implementation it’s way too easy for an average user to attempt to get this set up & get themselves locked out of their own Lemmy account.
- Lemmy doesn’t display a QR code like every other website/app using 2FA
- Lemmy doesn’t force the user to successfully test that the 2FA is working before saving the changes
- Lemmy doesn’t give the user any backup codes, unclear what the procedure is if you don’t have a backup code, lose your 2FA device and need to reset
- Lemmy’s 2FA implementation is SHA256, not all 2FA apps support that (e.g. I tried adding this to both Google Authenticator and andOTP and came out with 2 different 2FA codes, maybe because Google’s app doesn’t support SHA256)
In the end I got nervous & was unsure which if any of my apps were working with Lemmy’s 2FA so disabled it for now. It’ll get better in a future update, just saying be careful going through the current setup.
I use Bitwarden and was surprised that it supported Lemmy’s 2FA implementation. I tested it in incognito so I could undo it if needed.
Also please test that it works before logging out. If it doesn’t work, disable it immediately.
For me 2FA on Lemmy is busted since it only supports an obscure version of TOTP that nothing I use (authy, Google auth, etc) supports.
There are various GitHub issues filed related to TOTP usability and Lemmy.
Lemmy supports true standard totp. Those apps listed are the obscure ones, they do their own wacky shit with the standards
I disagree. Per RFC, only SHA1 needs to be supported. These apps support SHA1.
Lemmy is using SHA256 which ‘may’ not ‘must’ be supported per RFC.
The standard is SHA1… it is a ‘must be supported’. Every other website I use TOTP with works with all these apps. Lemmy is the outliar via using SHA256.
Edit to add RFC reference:
As defined in [RFC4226], the HOTP algorithm is based on the HMAC-SHA-1 algorithm (as specified in [RFC2104]) and applied to an increasing counter value representing the message in the HMAC computation. ... TOTP implementations MAY use HMAC-SHA-256 or HMAC-SHA-512 functions, based on SHA-256 or SHA-512 [SHA2] hash functions, instead of the HMAC-SHA-1 function that has been specified for the HOTP computation in [RFC4226].The implementation doesn’t verify that you can generate valid tokens before updating your account and doesn’t give you any backup recovery tokens.
I agree with that
Lmao, Authy and Google Authenticator are probably among the most popular 2FA apps around
“Embrace, Extend, Extinguish”
Fuck Google
me, reads: Lemmy (from Motorhead) offers Top of the Pops a two F-k-All option
me visualizes the 2-fingered bird getting offered to the old music show
