Privacy Guides
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.
- This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
- 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.
Additional Resources:
- EFF: Surveillance Self-Defense
- Consumer Reports Security Planner
- Jonah Aragon (YouTube)
- r/Privacy
- Big Ass Data Broker Opt-Out List
view the rest of the comments
Why do you think its not safe? If you trust bitwarden to protect your passwords what exactly do you think is going to happen?
Even if bitwarden is compromised in someway in the future, all that data is still encrypted and would still be highly unlikely to actually be accessed in any usable form.
The only risk is if you use a bad master password. Which is the biggest risk of using a password manager regardless.
I think a bigger concern is if someone managed to access bitwarden on a logged in instance. Think, leaving your laptop open, or someone steals it from you. If theres two apps for logging then both apps need to be accessible/compromised.
This seems more like a user issue then a security issue. If you are avoiding this feature because you have to idiot proof your security against yourself, your probably going to be compromised at some point anyway.
As for your example, this seems easily avoidable by
If you are going to write "user issue" in the future, maybe stop and think. You might be calling someone dumb and be defending bad design at the same time.
I think if people read that comment and think they are being called dumb, that's completely on them and probably a good time to look themselves in the mirror.
Nothing wrong with the design. Its literally just making thing easier at no cost to the user.
The point of 2FA/MFA is that you need two separate things in order to gain access. By having them both be the same then suddenly the attacker only needs to get one factor. Sure, it's probably low risk, but it's still risk.
Basically then it degrades to a very strong password that can’t easily be phished.
Which is still pretty good in my book, but not as good as a second device.
Not really. You still should be using MFA to access the vault itself before you can even get to the Token.
Yeah, of course. A very strong password that can’t easily be fished that is stored in Bitwarden. I thought that was implied.
"Basically then it degrades to a very strong password that can’t easily be phished."
I'm disagreeing with this, in that you are still (hopefully) using 2FA with your vault. Therefore whatever your accessing in that vault whether its a TOTP token or a password is still protected by MFA and not just a "very strong password".
Putting a TOTP token inside a vault protected by a strong password and another form of authentication is no less secure then having it be separate from the vault.
Now, this is where I get the impression you are not listening to me and are just arguing for arguing’s sake.
I’m getting off this ride.
Lol OK. Seems like its to much for you to consider you poorly communicated your point anyway.
Considering a password manager that also stores your second factor to be 2FA, assuming that it requires two factors to authenticate with on its own, is basically the same thing as considering logging into a site via SSO that itself requires two factors to be 2FA.
It’s also the same as considering a hardware security key with a PIN-protected Passkey to be 2FA.
Yes but you would still have 2FA.
You would still be using 2fa to access your vault. So in effect anything in that vault has more then 2 factors of authentication as it requires MFA just to get to the password.
Yes but you would still have 2FA.
You would still be using 2fa to access your vault. So in effect anything in that vault has more then 2 factors of authentication as it requires MFA just to get to the password.