79

Objective: Secure & private password management, prevent anyone from stealing your passwords.

Option 1: Store Keepass PW file in personal cloud service like OneDrive/GoogleDrive/etc , download file, use KeepassXC to Open

Option 2: Use ProtonPass or similar solution like Bitwarden

Option 3: Host a solution like Vaultwarden

Which would do you choose? Are there more options ? Assume strong masterpassword and strong technical skills

you are viewing a single comment's thread
view the rest of the comments
[-] TechieDamien@lemmy.ml 7 points 1 year ago

Option 4: levy existing tools such as gpg and git using something like pass. That way, you are keeping things simple but it requires more technical knowledge. Depending on your threat model, you may want to invest in a hardware security key such as a yubikey which works well with both gpg and ssh.

[-] KairuByte@lemmy.dbzer0.com 4 points 1 year ago

Why use tools not meant for password management, when alternative tools explicitly meant for password management, which have similar levels of security, work just fine?

You’re essentially saying “instead of driving down the road, I like to ride my bike with rollerblades.”

[-] benjacoblee@lemmy.world 2 points 1 year ago

I have a set up like this (age, passage, & git). Bitwarden's browser integration works just fine, for the most part. The thing is, some of my passwords are not browser-based, and I spend large amounts of time in the terminal. Using a CLI-tool in this case lets me save a bit of time

[-] nutshell7827@lemmy.world 1 points 1 year ago

Bitwarden has a cli tool which I find pretty useful. Together with jq you can even pipe the password or store it to a variable.

[-] benjacoblee@lemmy.world 2 points 1 year ago

Ah I didn't know that! Thanks, will be checking it out for sure

load more comments (1 replies)
load more comments (1 replies)
this post was submitted on 28 Sep 2023
79 points (98.8% liked)

Selfhosted

40199 readers
570 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS