Never rely on any cloud service! A good cloud based password manager is end to end encrypted meaning the password manager provider cannot access your passwords and they are secured from the provider and any compromise of the provider. But you do not only need confidentiality but also reliability. The cloud is just someone else’s computer that you store your data on. They can cease their service or stop providing you access to it at any time. Always have a local backup of anything important saved in a cloud.

With Bitwarden for example you can export your vault as unencrypted json and csv format. Those are widely compatible and allow you to easily access and import your passwords.

Do not save your exported passwords unencrypted. I strongly recommend creating a dedicated VeraCrypt or LUKS container or similar and saving the export directly into that without saving it to disk unencrypted in the first place.

Note that shared organizations are not included in the standard vault export and need to be exported separately.

Edit: Someone mentioned that Bitwarden’s export feature does not export attachments. So export them manually if you need to.

1 point

Bitwarden is probably a lot safer if you self host (which I do). You do inherently lose some security by having a server that holds your encrypted password database, but my instance isn’t exposed to the internet.

permalink
report
reply
3 points

are you using the official bitwarden server or vaultwarden? been thinking about selfhosting it myself, but i would need to expose it to the internet, and i’m not really sure if i’m up to the task of properly securing it

permalink
report
parent
reply
2 points

Good tip, I’ll get on it. I use Bitwarden’s cloud server for convenience, but if they were to shut down tomorrow, I’d be screwed

permalink
report
reply
3 points

Only somewhat screwed. The client still has a local offline cache. So you don’t immediately lose everything. The cache is read-only though and doesn’t contain attachments.

Also remember: the normal export function of bitwarden also “just” exports the database entries; not the file attachments.

permalink
report
parent
reply
1 point

If you are the BitWarden server admin, what do you see per user? Just a blob of data called “encrypted password database” or something, along with something like a last modified date and version number for syncing purposes?

permalink
report
parent
reply
2 points

A good cloud based password manager is end to end encrypted

Presumably end-to-end encrypted. Do not trust any of them. There is no good cloud-based password manager.

My personal recommendations:

  1. KeePass (and its numerous alternative clients). The password database is one single file which would never have to leave your local network (or even: computer).
  2. Gopass (pass with modern addins). The password database is a folder of files which can optionally be version-controlled in a Git or Fossil repository. The default encryption is GnuPG, but it also supports age.
permalink
report
reply
4 points

Presumably end-to-end encrypted. Do not trust any of them. There is no good cloud-based password manager.

Bitwarden is open source and audited: https://bitwarden.com/help/is-bitwarden-audited/

permalink
report
parent
reply
2 points
*

You can’t prove that their server is running the exact same code. A self-hosted Bitwarden server might be reasonably secure, but as far as I can tell, Bitwarden('s server component) is not designed for single users.

permalink
report
parent
reply
1 point
*
Deleted by creator
permalink
report
parent
reply
3 points

Even though you don’t know what code is running on their server, the bitwarden client used to communicate with their server is open source & auditable. End-to-end encryption only requires that the client code is trustworthy.

permalink
report
parent
reply
4 points

You can’t prove that their server is running the exact same code

Which is the whole point between e2ee, assuming the server ended up being malicious, as long as the client code is doing its job properly, its fine. All the apps are open source.

Bitwarden('s server component) is not designed for single users.

vaultwarden’s good if you’re selfhosting, incredibly lightweight and compatible with bitwarden clients

permalink
report
parent
reply
5 points

The entire point of E2EE encryption is that you do not have to trust the server.

permalink
report
parent
reply
1 point

I don’t have to trust the server, if I trust the client in an e2ee model. Their server could only be a security issue, if the encryption wouldn’t be e2e. And then the whole application would suck.

permalink
report
parent
reply
4 points

Keepass all the way friends. Synced via flash drive or syncthing>

permalink
report
reply
1 point

Keepass on nextcloud ftw

permalink
report
parent
reply
0 points

Was also going to suggest KeePass and syncthing, it’s been working flawlessly for a long time. In case of conflicts, at least keepassxc allows you to easily merge databases.

permalink
report
parent
reply
2 points

Putting keepass and syncthing together is a match made in heaven

permalink
report
parent
reply
1 point

I originally used Keepass, but then I managed to convince my wife to use a password manager and needed something more user friendly. I switched to LastPass until they started charging, now we’re on Bitwarden

permalink
report
parent
reply

Privacy Guides

!privacyguides@lemmy.one

Create post

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:

Learn more…


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:

  1. We prefer posting about open-source software whenever possible.
  2. 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.
  3. No soliciting engagement: Don’t ask for upvotes, follows, etc.
  4. Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
  5. Be civil, no violence, hate speech. Assume people here are posting in good faith.
  6. Don’t repost topics which have already been covered here.
  7. 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.
  8. Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
  9. 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.
  10. No misinformation: Extraordinary claims must be matched with evidence.
  11. 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.
  12. 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:

Community stats

  • 746

    Monthly active users

  • 628

    Posts

  • 12K

    Comments