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.
KeePassXC 2.7.0
121–130 of 141 posts
Re: KeePassXC 2.7.0
#122KPXC 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).
I am curious why you switched from Bitwarden? Usually when people are exiting a password manager it’s migrating to Bitwarden or KeePass but you’re the first I’ve heard moving from Bitwarden itself.
Re: KeePassXC 2.7.0
#123KPXC 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).
> The only issue for me is the autotype support on Wayland Are you using a wlroots compositor like sway or GNOME/KDE?
Re: KeePassXC 2.7.0
#124Earlier quoted context omitted.
Not sure what you mean but the default KeepassXC on Fedora 35 with Wayland does not do autofill in Firefox.
I'm on Debian Bullseye stable with Wayland GNOME out of the box, and autotype works fine.
Re: KeePassXC 2.7.0
#125Earlier quoted context omitted.
I'd say there's no good reason to ever use multiple shared access compared to synchronizing with hooks on open.
What is synchronizing with hooks on open?
Re: KeePassXC 2.7.0
#126Been a happy user of KeePassXC for over 4 years now. I keep the password databases and keys synchronised across devices using Syncthing. Once I've set this up, it's pretty transparent and I haven't had to tinker with it.
Same setup, the DB only came out of sync (conflict) a few times but that's because with my setup Syncthing is only doing it's thing when I'm on my local network...
I see. You've chosen not to use remote sync?
Re: KeePassXC 2.7.0
#127Earlier quoted context omitted.
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).
Sorry for the late reply. BitWarden is great. I really don't have anything to complaint (before BitWarden, I was using browser built-in password manager). However, I changed. I start to value the following: 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…
Re: KeePassXC 2.7.0
#128I wish it had templates for credit cards.
The other critical feature I want is for it to store my expired passwords, once I change them. I have had stupid services where the old passwords were still in use somewhere or the other, and I don't want to delete them. Right now I just copy past them in the notes, but there should be an easier way.
https://keepassxc.org/docs/KeePassXC_UserGuide.html#_history
Re: KeePassXC 2.7.0
#129Earlier 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.
I assumed people would switch from Keepass + database synced on a private server to something else when they started working in teams and need better/easier permission models. :)
As you have mentioned it, I have written the tool keepass-diff (https://github.com/Narigo/keepass-diff/>) to help me for exactly these conflicts and I could quickly resolve the issues with it. It was still useful enough to let me keep using Keepass. Was it not working for you or was it too hard to use because of how it needs to be set up first? Would you have stayed with Keepass + sync if something similar to this was integrated into UI clients?