I’m in desparate need of setting up borgmatic for borg backup. I would like to encrypt my backups. (I suppose, an unencrypted backup is better than none in my case, so I should get it done today regardless.)
How do I save those keys? Is there a directory structure I follow? Do you backup the keys as well? Are there keys that I need to write down by hand? Should I use a cloud service like bitwarden secrets manager? Could I host something?
Im ignorant on this matter. The most I’ve done is add ssh keys to git forges and use ssh-copyid. But I’ve always been able to access what I need to without keeping those (I login to the web interface.) Can you share with me best practices or what you do to manage non-password secrets?
hendrik@palaver.p3x.de 4 months ago
I add such stuff to my password manager. It supports files. But not all password managers do. I have a category for admin stuff where I also save passwords to servers, database credentials, service logins and the expored keys of the harddrives.
CloseSymbol@lemmy.world 4 months ago
Also using my password manager, keepass2 in my case (synced over webdav). A password manager should provide plenty of options to structurize. Password database is a part of scheduled backups, and always present on multiple synced devices, so a total loss is hardly imaginable.
As SSH keys were also touched as a topic in the OP, I just wanted to add I just found that there seems to be an addon for keepass that makes handling those even easier: lechnology.com/software/keeagent/ (haven’t tried that yet).