What was previously only available as a beta version for selected testers is now being activated for all customers: the new Login 2.0.
Before today, mailbox.org’s 2FA mechanism was unorthodox. In the login screen, you typed in the TOTP in the password field and then added a 4 digit static pin at the end. This got people confused, as it’s different than the usual login+password then TOTP. Now it’s just like that.
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.
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.
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.
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
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: !privacyguides@lemmy.one
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:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
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.
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
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.
Okay, so for those of us using third party apps like Thunderbird, everything is done using app specific passwords, which is great
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.
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