secstore (and secstored) is the conventional answer there. It typically runs on your auth server, and factotum will connect to it when it starts, to load your keys. Things are encrypted on disk, and you only need the secstore password.

The ‘feedkeys’ script demonstrates how to do it manually, after factum is already running, in case you can’t reach your auth server when factotum starts (or if you don’t have a stable office server). 

In some sense the simplest answer is to just encrypt the file you are already using on disk, probably using aescbc. But, personally, I would set up secstore anyway; it is more convenient for factum, and it is nice to have an easy way to save other encrypted things, too. Just run it at boot time and use ‘feedkeys’ or something similar to populate factotum after. 

On Dec 20, 2024, at 11:46, Clay Ayers - thedaemon via 9fans <9fans@9fans.net> wrote:


I still haven't managed to understand how to get my keys into factotum without having to manually push them each time. I have a script that runs the echo 'key proto', etc to /mnt/factotum/ctl for all of my passwords, but it's in an unencrypted text file. The instructions don't make sense to me on how to get this to work. I added this reply here because I think it's relevant..?

Reply via email to