39
Why would i abbandon KeepassDX? (lemmy.ml)
submitted 7 months ago* (last edited 7 months ago) by to c/selfhosted@lemmy.world
24 comments fedilink hide all child comments
 

I use KeepassDX on family mobiles with Syncthing for copies between laptop and phones. What would i gain moving to Vaultwarden, knowing that i would never open my network to the outside world? It would be easier to manage for sure, as im having to setup phones and laotops myself in the family and worry that they do silly things like turn off syncthing. But what about offline access to passwords? Does Bitwarden mobile client keep a local copy of database until it can sync?

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 10 points 7 months ago (3 children)

That is another problem i face when i have the app open on desktop and phone at the same time. Its a nightmare.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 16 points 7 months ago

    I use keepassxc and syncthing and have never had this problem.

    I think there's something in the settings to save after each change and reparse if there's a remote change.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 7 months ago* (2 children)

    Doesn't it only lead to problems if you change the same exact data on both copies to different values? It literally never happened to me, I never had a merge problem. It always just asks me to merge, I say yes, and that's it.

    Oh wait I use KeepassXC not DX, dunno what the difference is

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 7 months ago (1 child)

    The problem is that syncing between devices is not implemented in KeePass itself but through an external tool (Nextcloud, Syncthing, or whatever else). The sync client will only see the ciphertext and won't be able to tell which records have been changed, only that two different binary files have a common ancestor and are in conflict.

    The most obvious solution is to lock and close the database when it's not in use (which is a good practice from a security perspective too), and to sync immediately when it is changed.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •