Thanks for all the comments. Currently I use KeepassXD/DX + Syncthing.

I hash my password with fingerprint on Android, keep a seperate database containing that one in another place for backup. Maybe thats stupid, but I cant type on a phone.

On Linux I use KWallet, store the Keepass password there, and have a shortcut fetching that password and inserting it into the Keepass wallet using KeepassXC. Works with one click too.

Problems

  • all entries are either locked or unlocked
  • to have autofill working, the app cant be killed (Android)
  • also, all passwords need to be decrypted for it to work

I dont see that this is the best solution. Decrypted, maybe hashed metadata possible to detect autofill fields, and then selectively unlock the needed credentials, would be better.

  • Stephen304@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    You can actually keep it locked and it still works. It just prompts you to unlock it when you press the auto fill button. It also means that it won’t show autofill suggestions on the login screen and just a generic bitwarden autofill button. You can change how long it stays unlocked for between immediately to any custom number of hours / minutes or only on app restart.

    • Pantherina@feddit.deOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Interesting yes I think thats correct! So it actually does work on Android, just not as well on Linux, if at all with the Flatpak mess.

      • Stephen304@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Yeah I don’t use the flatpak / desktop app at all, since I have the browser extension installed which does autofill and also has the same vault lock options as the mobile app.