Keepass all the way friends. Synced via flash drive or syncthing>
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
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.
Putting keepass and syncthing together is a match made in heaven
Yup, I use keepass and just sync stuff manually.
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
Keepass on nextcloud ftw
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:
- 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).
- 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.
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/
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.
The entire point of E2EE encryption is that you do not have to trust the server.
exactly
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.
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
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.
Vaultwarden is a good Bitwarden API compatible self hosted server that individuals can reasonably self host, with way fewer system requirements than the actual Bitwarden project's server.
but it also supports age
Honestly, i applaud age for being very simple to use and less likely to screw up as a result, but i wouldn't rely on it for files as sensitive as a password database, its relatively new and hasn't been audited.
Yet. I hope it will. (The developer is a great dude though.)
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
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.
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?
The entries are individual DB entries, but fully encrypted, yes.
For organizations you also have encrypted keys in there, which can then - via asymmetric encryption - be shared by organization admins to new organization members. Still E2EE - the server is only the messenger/orchestrator here.
So the most an admin of a server sees is metadata (number of entries, how often they are modified, synced etc).
I think the only "plain" information on the server is the email address of the account itself ... which you need to login with your bitwarden client and which can be used for sending notifications. The password for validation that you are who you say you are is client side derived from your master password. So the server cannot reverse it to your master password. It's essentially also an asymmetric login information; you can produce the necessary information to prove to the server that you know the master password, but the server doesn't know the master password. Cryptography is fascinating.
@ThreeHopsAhead I'm already backing up my KeePass database on an external hard drive. Guess that counts.
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.
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
I'm using Vaultwarden, it's pretty easy to set up with their Docker containers.
To create aencrypted backup with attachments, you can use Portwarden: https://github.com/vwxyzjn/portwarden
Also a good way to migrate from bitwarden to vaultwarden or to switch vaultwarden instances.
My vault is encrypted and I make regular backups of it on an encrypted USB flash drive where I keep my other backups as well. c: