Yarn

Recent twts in reply to #nlzhexa

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

Indeed, BitWarden works nice as a credentials manager, and I’m quite happy with the implementation of Passkeys.

Sadly my old Android 9 is not compatible with the mobile app, although I use the web for that case.
That said, that’s what I’ve been using for years and I can’t find a reason to try another (as usually happens with these tools)

I’d suggest of self-host or trying a public instance of Vaultwarden like https://passwd.hostux.net
(donation supported)

⤋ Read More

Participate

Login to join in on this yarn.