111–120 of 141 posts
PSA: Never, ever mix Keepass2 and KeepassXC when using network shares. KeepassXC does not support the sync protocol from keepass2 that allows multiple people/devices to use the same keepass database. We only found out after losing 200+ passwords.
I'd say there's no good reason to ever use multiple shared access compared to synchronizing with hooks on open.
eg: account.domain.com changes to signon.domain.com at some point and it stops matching.
I've gone in and saved some accounts as just domain.com to prevent this, but when creating new passwords/etc, it always adds the current URL and the problem happens again after some time.
Thanks!
Earlier quoted context omitted.
I use Strongbox on iOS which I highly recommend checking out. It's payed (one time) but open source
> payed (one time) This is true, but pricing is currently $3/mo, $15/year, $60 lifetime. So the one time payment is larger than most.
What I love on KeePassXC: * Runs on Linux/Mac/Windows and there are compatible clients for Android. Make your own cloud with a RaspberryPi referred by a DDNS and you'll have super powers. * Auto-type. Is tricky to get it working but once you get it you'll become addicted. * The UI makes it much easier to copy and paste fields and the notes are clearly visible. I often use the notes to store things like github tokens…
I know there are decent options for both mobile devices but it is harder to pitch a piece of software with multiple vendors than a single, unified vendor when security is a top concern.
What I love on KeePassXC: * Runs on Linux/Mac/Windows and there are compatible clients for Android. Make your own cloud with a RaspberryPi referred by a DDNS and you'll have super powers. * Auto-type. Is tricky to get it working but once you get it you'll become addicted. * The UI makes it much easier to copy and paste fields and the notes are clearly visible. I often use the notes to store things like github tokens…
Technically no, but whether or not that is a problem depends on the threats you're worried about.
I'm personally most worried about 1. credential stuffing, 2. keyloggers/client exploits, and 3. Phishing/MITM attacks.
Using a password database allows me to use different passwords for every site, which defeats #1.
TOTP even if it's in the same database solves for #2 since simply scraping the password isn't enough to gain access.
And #3 isn't addressed at all, even if you use a separate device for TOTP.
What I'm not especially worried about is specific targeted attacks where the attacker is attempting to acquire my database and crack it.
Now, if you store your password database on someone else's cloud, that could become more of a concern, as a mass breach and bulk collection of databases becomes a possible attack vector. But I use syncthing to directly share my DB between devices, so I'm not particularly worried about that.
If you're worried about either of those threats, then a separate TOTP device is absolutely vital. But, for me personally, the inconvenience of it is not worth the additional security.
I use keepass2 at work on a PC/windows and KeepassXC on my home computers (Mac and Linux). The only thing that make me still liking Keepass2 more is its compatibility with plugins. I can't wait for keepassXC to support them.
Why do you want plugins? KeePassXC provides most of what KeePass needs plugins for out of the box in usually much better and more stable and tested quality. KeePassXC will never support plugins the way KeePass does and for good reason. Most plugins are unmaintained and some are outright dangerous to use. Your passwords are too precious to let unverified thirdparty plugins handle them. If you need external functionali…
Earlier quoted context omitted.
You read my mind, as i was just asking myself the same thing. I have recently been thinking of switching over to bitwarden from classic keepass...but now i see keepassXC, and wondered what - if any - compelling feature/need that keepassXC brings...? p.s. - Oh, and the reason for considering even moving to bitwarden is ease of mobile access by several people at once...since schlepping a keepass database via file sync…
KeePassDX works great on android.
Earlier quoted context omitted.
I chose KPXC because I am in easy access to the database, and since I already pay for cloud hosting I just sync the database on the cloud (I use Seafile, I recommend!). Open and convenient :) I'm sure Bitwarden is more than adequate as well though.
I've migrated from KPXC to Bitwarden because of all the sync conflicts and having to diff different versions and figuring out, which data is latest (yes, keepass-diff is a thing). With Bitwarden, I cannot create a new password or change existing one without being online, but I consider that a small price for not having to deal with conflicts anymore.
KPXC is brilliant. Recently I switched to it from BitWarden and I am satisfied. The only issue for me is the autotype support on Wayland (it's not there yet; currently only able to auto fill password and username for xwayland app).
Curious, why did you switch from BitWarden? It’s usually the other way around (though personally I never felt the need to switch from KPXC).
1. I need a tool that can save not just password, but something more general. For example, a desktop software credential (with BitWarden, I need to open a browser or electron app to do that). Another example would be a PIN required each time I use the voice mail. Or certain PIN for my bank accounts (not the one used to login the online banking). I am aware you can save them in the note section, but it feels better when you can customize these fields. These non-password secrets used to be saved in plain text scattered around in various files on my PC. Now I have a centralized and organized access.
2. I know that with some configuration you can have self-hosted BitWarden vault. But I think KPXC + whatever_file_sync_app is simpler.
3. I actually started using KeePassXC because IT forced me so. I hated it initially, but later discovered it's actually a great tool for managing secrets in general.
4. HN Syndrome: preferring "native" app than web/electron.