KeePass, Syncthing, and Source-of-Truth Protocols: Users Outline Battle Plan for Android Password Security
The recommended stack centers on KeePass, often paired with KeePassDX/XC, for accessing database files on Android. Synchronization leans heavily toward Syncthing for file transfer.
The floor is split on workflow rigidity. Some users, like privatepirate, champion the Keepass DX/XC + Syncthing route while advising the 3-2-1 backup rule. Courantdair flagged the potential risk of storing TOTP secrets inside the main vault. A more strict methodology was detailed by x550, demanding the laptop remain the absolute source of truth, treating the phone copy as read-only to prevent data corruption.
The weight of opinion funnels toward the KeePass ecosystem. The clear consensus favors using Keepass with Syncthing; however, the major operational disagreement remains the synchronization method—specifically, the inherent risk of co-locating TOTP secrets within the primary password vault.
Key Points
KeePass combined with Syncthing is the preferred Android alternative to Bitwarden.
Multiple sources pointed toward KeePass + Syncthing as the heavily favored solution.
The security implication of co-locating TOTP secrets in the primary vault is a stated concern.
Courantdair specifically pointed out the risk associated with embedding TOTP secrets within the main password vault.
The laptop device must function as the undisputed source of truth for database updates.
x550 detailed a meticulous workflow where the phone copy should only be read-only.
Keepass DX/XC paired with Syncthing offers a robust, recommended setup.
privatepirate pushed this combination while also advocating for the 3-2-1 backup rule.
MummifiedClient5000 mentioned Vaultwarden as a functional self-hosting option.
This was noted as an alternative compatibility point, separate from the main KeePass push.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.