вт, 6 мая 2025 г. в 00:16, Marc SCHAEFER <schae...@alphanet.ch>:
> On a standard system (Debian GNU/Linux): > > - install keepassxc, create a master password and a database file > [ alternative: keepass2, but mono dependancy ] > - make sure that database file is on a git, pushable to a > remote repository (I like git-on-SSH), and push/commit it when > required [...] > Do you use setups like this? Or do you prefer cloud solutions like the > ones offered by keepass2, or even a fully web (possibly mobile, too) > solution like bitwarden (I already use it, but it's a bit complicated & > has licencing issues)? 1) git repo will store EVERY version of database file as is. Do you really need it? 2) at computer will you push new data by hand? I think must be some automation for this. 3) how about another sync apps? My case: 3 computers, 2 storages in different locations, one phone. All linked by syncthing: one common directory at every device + some directories on storages + corresponded device (like a photos at phone) I put keepassxc database in ~/Sync folder and use it on every comp + phone (keepass2android), sometimes simultaneously. Even if i does not have link to any other device (sometimes internet is broken), i can use credentials from local copy of database. On storages I configured syncthing to save several copies of deleted/overwritten files in this dir, so i can restore data after some disaster. At some local (in city) vds was installed strelaysrv and was added to configuration of all syncthing instances — for better connectivity over broken internet. I recommend to use syncthing from apt.syncthing.net, but you can use it from Debian repository, work fine (used at previous instance of second storage). -- Stanislav
