In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
Additional Resources:
Okay, so for those of us using third party apps like Thunderbird, everything is done using app specific passwords, which is great
The new feature for Email App Passwords for external email programmes
But if this is a new feature, how did third party apps work before? Could people just not use them if they enabled 2FA?
Basically, yes, they couldn't use them. The old 2FA had a really weird implementation...
This is just wrong, you used the main account password instead of an app password
You could use third party clients with 2FA enabled in the past (at least I could). I think I used my normal password for the clients, so no real 2FA on that side, but that's no different from the new app specific passwords. IMAP doesn't allow 2FA so every mail provider allowing third party clients essentially has a weak point with no 2FA there.
Well fucking finally. I have no idea what took them so long.
I think they resell https://www.open-xchange.com/ so they were dependent on them accomodating Keycloak (identity solution used by mailbox)
I'm not sure I quite understand how this would make them unable to support normal 2fa until now.
Keycloak is one of the most configurable and flexible auth solutions, and there is no way it didn't support otp based 2fa until recently.
Bit of trivia but I think I know why the 4 digit pin thing existed! It's an out-of-the-box feature on freeRADIUS, I ran across it in a pfsense environment in the past. I thought it was neat (esp. in the absence of passwords, this was primary auth with public keys and then 2fa on top) but ultimately too convoluted for most users
How can I enable it? I received the mail but my login is still using pin+otp and in the settings there is no option to migrate to normal F2A, only the old pin+opt thing.
Read the The rollout of Login 2.0 for our customers se tion in the linked post
Maybe most people using Mailbox know about this but I'll still mention that using Mailbox kinda requires having your own domain.
Reason is the same as Posteo (unless Posteo changed something lately) : mail adresses will get recycled after some time when you stop using the service and close your account.
Most other providers blacklist adresses so they can't get reused when an account gets deleted.