keepass-diff VS tessen

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 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?

I had this problem as well, these conflicts may happen when you keep Keepass clients open and add passwords on two different machines.

I have written a CLI tool in Rust called keepass-diff that may help you with this: https://github.com/Narigo/keepass-diff

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

This may not be as impressive but I wrote a script to eliminate one of the primary roadblocks I faced when I moved to Wayland on my Linux desktop — a script to copy and autotype password store amd gopass data, kinda like rofi-pass

https://github.com/ayushnix/tessen

tessen is a bash script to autotype and copy password store data on wayland compositors. The latest release of tessen adds support for gopass as well, although parsing YAML files isn't supported. If gopass files use the same format mentioned here, tessen should work fine.

I'd be willing to package it for Void Linux but I don't really have any experience with how Void Linux packages work. tessen is just a shell script so you can download it and place it in your $PATH and use it if you want.

As I've mentioned in the isse tracker here, the only thing that's missing from fuzzel is support for using a configuration file. If it gets that, it would replace every other launcher and dmenu program on Wayland for me and would also allow me to go ahead and brand fuzzel as the default dmenu backend for tessen.

I made this post a few weeks ago about tessen's initial release. Since then, I've added a few features that might've prevented rofi-pass users from switching to Wayland based compositors (I was one of them).

I ran into this problem as well when making tessen. fzf doesn't have a GUI like rofi, bemenu, and wofi do, so you can't use fzf to type in data in anything else besides the terminal in which it was opened, at least not without resorting to ugly hacks (which is what the swaymsg window move method is).

Support for wofi has been added as well