Comment on Google Says Sorry After Passwords Vanish For 15 Million Windows Users.

• nekusoul@lemmy.nekusoul.de ⁨1⁩ ⁨month⁩ ago

  Most amazingly, this setup is also unexpectedly resilient against merge conflicts and can sync even when two copies have changed. You wouldn’t expect that from tools relying on 3rd party file syncing.

  I still try to avoid it, but every time it accidentally happened, I could just merge the changes automatically without losing data.

  source

  • Shatur@lemmy.ml ⁨1⁩ ⁨month⁩ ago

    How did you enable merge conflict resolution for KeePassXC databases?

    source

    • nekusoul@lemmy.nekusoul.de ⁨1⁩ ⁨month⁩ ago

      Depends a bit on the clients.

      • KeePass: Will ask you if you want to synchronize/overwrite/discard the database when saving.
      • KeePassXC: Will autoreload the database in the background, so merge conflicts shouldn’t happen in the first place. Otherwise there’s ‘Merge database’ in the menu.
      • KeePass2Android: So I mixed up the names and this is the client I actually use. This one does all changes to an internal copy of the database that is then synchronized on request.

      source
    • PlexSheep@infosec.pub ⁨1⁩ ⁨month⁩ ago

      By ignoring the conflict files

      source
• OfficerBribe@lemm.ee ⁨1⁩ ⁨month⁩ ago

  I store my DB in Dropbox and use KeePass2Android on phone which has built in Dropbox sync.

  source

  • Hexarei@programming.dev ⁨1⁩ ⁨month⁩ ago

    Yeah but then you have to trust Dropbox

    source

    • OfficerBribe@lemm.ee ⁨1⁩ ⁨month⁩ ago

      And I do, have used it for 10+ years I think. Keyfile is also used so even with leaked DB file and password, it should be inaccessible.

      source