Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

KeePassXC 2.7.0

keepassxc.org

Post reply on HN
Print view View original

131–140 of 141 posts

Re: KeePassXC 2.7.0

#131

Post by Narigo »

mixedCase wrote: post #42
mettamage wrote: post #41

I've heard this one recommended over and over again. Are there any "I wish I knew this beforehand" type of tips? Also, how would people compare this to something such as 1Password?

Multiple devices is a slight pain, you have to keep everything synchronized yourself, and conflicts mean you can lose passwords in your sync service debris (if you even have that feature). I switched to Bitwarden in order to deal with this.

Did you try diffing the conflicting databases through a tool like keepass-diff before switching?

I'm the author of keepass-diff and built it for my own needs. Looking through the comments here about why people switched from Keepass to Bitwarden, it feels like the compare feature is something that should be integrated to UI clients as many people seem to face this problem. I always assumed it was more because of permissions and better ability to work with it as a team...

Re: KeePassXC 2.7.0

#132

Post by mixedCase »

Narigo wrote: post #131
mixedCase wrote: post #42

Earlier quoted context omitted.

Multiple devices is a slight pain, you have to keep everything synchronized yourself, and conflicts mean you can lose passwords in your sync service debris (if you even have that feature). I switched to Bitwarden in order to deal with this.

Did you try diffing the conflicting databases through a tool like keepass-diff before switching? I'm the author of keepass-diff and built it for my own needs. Looking through the comments here about why people switched from Keepass to Bitwarden, it feels like the compare feature is something that should be integrated to UI clients as many people seem to face this problem. I always assumed it was more because of permi…

I did not, I wasn't aware of keepass-diff and certainly it would've been able to solve the problem. But to tell you the truth I don't think I would use it. This is something that I really don't want to have to worry about regardless of what device I'm using.

Re: KeePassXC 2.7.0

#133

Post by npteljes »

electrotype wrote: post #101
npteljes wrote: post #100

Earlier quoted context omitted.

How does this system handle conflicts?

How exactly, I don't know the details. But there is a built-in "synchronize" feature.

What would happen if the synchorized safe is open on two computers at the same time, they both add a new entry roughly at the same time?

I like the idea of this sync but I don't know how the internal implementation would handle this. Dropbox and Nextcloud both sync the files themselves, and in case of a conflict, they preserve both versions, and let you pick which one you'd like to use as the "canonical". It's a pain but at least the data is preserved.

Re: KeePassXC 2.7.0

#134

Post by gnramires »

Narigo wrote: post #129
vetinari wrote: post #91

Earlier quoted context omitted.

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.

The sync conflicts happened to me whenever I left keepass databases open and changed it on multiple devices. Usually, those changes were adding new accounts into the databases or changing a password on one while adding something on the other. This regularly happened when working in a team. I assumed people would switch from Keepass + database synced on a private server to something else when they started working in t…

I have checked a few settings on KPXC, and it has 'Automatically save after every change', 'Automatically reload database when modified externally' (and 'Safely save database') all enabled, not sure it helps (as I mentioned, never had any problems).

Not sure if NextCloud could be causing some issues? As I mentioned, I believe Seafile automatically overwrites (to newest version) and it's been fine (there's history if you lose something, which shouldn't happen anyway).

I do think this merge functionality would be very nice in KPXC, but for other reasons: I sometimes use the browser databases to save passwords (when I forget to open KP) and I need to merge the new entires.

Re: KeePassXC 2.7.0

#135

Post by abdullahkhalids »

iamateapot wrote: post #128
abdullahkhalids wrote: post #108

Earlier quoted context omitted.

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.

KeePassXC has a history function? https://keepassxc.org/docs/KeePassXC_UserGuide.html#_history

I didn't know this was a thing. This works I think.

Re: KeePassXC 2.7.0

#136

Post by Narigo »

mixedCase wrote: post #132
Narigo wrote: post #131

Earlier quoted context omitted.

Did you try diffing the conflicting databases through a tool like keepass-diff before switching? I'm the author of keepass-diff and built it for my own needs. Looking through the comments here about why people switched from Keepass to Bitwarden, it feels like the compare feature is something that should be integrated to UI clients as many people seem to face this problem. I always assumed it was more because of permi…

I did not, I wasn't aware of keepass-diff and certainly it would've been able to solve the problem. But to tell you the truth I don't think I would use it. This is something that I really don't want to have to worry about regardless of what device I'm using.

Thanks for the insight! I guess it's a hard problem to solve with these conflicts. I'm wondering how it could be automatically resolved if a user has the same thing open multiple times with changes to the same password...

Re: KeePassXC 2.7.0

#137

Post by [deleted] »

longstation wrote: post #123
ayushnix wrote: post #11

Earlier quoted context omitted.

> The only issue for me is the autotype support on Wayland Are you using a wlroots compositor like sway or GNOME/KDE?

I am using both KDE and GNOME. When Firefox is under xwayland, it works. When switched to wayland, it stops working.

[deleted]

Re: KeePassXC 2.7.0

#138

Post by ayushnix »

longstation wrote: post #123
ayushnix wrote: post #11

Earlier quoted context omitted.

> The only issue for me is the autotype support on Wayland Are you using a wlroots compositor like sway or GNOME/KDE?

I am using both KDE and GNOME. When Firefox is under xwayland, it works. When switched to wayland, it stops working.

Looks like a known issue.

https://github.com/keepassxreboot/keepassxc/issues/2281

I'm considering adding support for keepassxc in tessen but autotype works only on wlroots based compositors like sway right now.

https://github.com/ayushnix/tessen/issues/19

Re: KeePassXC 2.7.0

#139

Post by vetinari »

Narigo wrote: post #129
vetinari wrote: post #91

Earlier quoted context omitted.

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.

The sync conflicts happened to me whenever I left keepass databases open and changed it on multiple devices. Usually, those changes were adding new accounts into the databases or changing a password on one while adding something on the other. This regularly happened when working in a team. I assumed people would switch from Keepass + database synced on a private server to something else when they started working in t…

I've used 'Automatically save after every change' and 'Automatically reload database when modified externally', as the other comment says, with syncing via Syncthing. It wasn't in team, but between multiple devices - laptop, desktop, phone and with a NAS in the sync chain, so there is something always on.

Yet, the sync conflicts happened anyways. The first time it was quite shock, why my password doesn't work, but then I found the conflict password file and the password from there worked.

Your tool made it much easier, big thanks for creating it.

Maybe, if the keepassxc had in the UI, that it detected a sync conflict (that would involve a knowledge how the misc sync tools work) and offered merging them, I would probably stayed.

Ultimately, I switched to vaultwarden, on the same above-mentioned NAS. It does not have all the features of the keepassxc, but it is good enough for me, the sync problems disappeared, and the browser integration works a little bit better (doesn't complain that the main app isn't running, while it is).

Re: KeePassXC 2.7.0

#140

Post by vetinari »

gnramires wrote: post #119
vetinari wrote: post #91

Earlier quoted context omitted.

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.

Since logging in is an online activity, that means every modification should automatically sync to the database as well. Thus I've never had conflicts, I think Seafile handles conflicts very well (mostly silently?). Never had an issue really (although the Android app is slightly clunky).

Logging in doesn't have to be on the public internet. It doesn't have to be a some intentionally isolated network either, but think setting up IoT devices: you log to the AP they created, create credentials and then connect them to some other network with Internet connectivity. So while you are connected to their AP, you don't have sync.
Post reply on HN