I use 1Password, and iCloud Passwords. I had migrated from 1P to iCloud, but ran into issues that forced me to continue with 1P. I pay for a family plan on 1Password.

⤋ Read More

I use KeePassXC because I really only use one device. I imagine it would be challenging to rsync the database around if I needed my passwords on more machines. It’s probably fine if you’re deliberate enough, but I don’t think it would take long before I’d lose a password by editing an outdated version of the repository and overwriting the main copy.

I like the simple architecture of Pass, and it would indeed lend itself well to a Git repository, but I don’t like that service names are visible on the filesystem. pass-tomb might mitigate this somewhat but it seems messy and I don’t know if it would work with Git without compromising the security of the tomb.

What’s so good about Bitwarden? Everyone seems to love it. I like that it can be self-hosted. I certainly wouldn’t want a third party in control of my password database.

⤋ Read More

@mckinley@twtxt.net You definitely have got a point!

It is kind of a hassle to keep things in sync and NOT eff up.
It happened to me before but I was lucky enough to have backups elsewhere.
But, now I kind of have a workflow to avoid data loss while benefiting from both tools.

P.S: my bad, I meant Syncthing earlier on my original replay instead of Rsync. 🫠

⤋ Read More

@mckinley@twtxt.net I can’t say for sure. I didn’t even know how three-way merges work till I looked it up. I guess it’s more of git thing that would prove useful in the case of using passwordstore/pass.
As for Keepass, all I do is syncing it’s database file across devices using syncting. Never felt the need to try anything else.

I guess it is safe enough for my use case, with Backup database before saving on and custom Backup Path Placeholders as Backup plan in case of an Eff up.

⤋ Read More

Participate

Login to join in on this yarn.