Additional Workflows - wizardofhoms/risks GitHub Wiki

The risks CLI offers other commands not explained in the usage tutorial. This page gathers them along with explanations.

Most of the commands below should be seldom used, since the CLI uses sane defaults, and it strives to do things in such as way that users should not have to use other tools to manage identities' data.

The configuration file for risks is located in ~/.risks/config.ini. You can set the graveyard directories, various mappers, GPG settings, etc. Various commands:

risks config get BACKUP_MAPPER
risks config set HUSH_DIR ~/secret
risks config list
risks config unset HUSH_DIR

Since the risks CLI encrypts all filenames on the system (as explained here), it's hard to know which files maps to which tomb/key/coffin. The CLI therefore provides a command that will simply output the resolved/encrypted name of a file. A few examples below:

risks resolve coffin PrimeWizard    # Filename of the GPG coffin for identity PrimeWizard (in ~/.graveyard)
risks resolve tomb SSH              # Filename of the SSH tomb in graveyard/<identity>/
risks resolve key SSH               # Filename of the SSH tomb key in ~/.hush/

The risks CLI has a kv command and subcommands to manage a basic file-based key-value store. While this store is not used by any commands, you might want to store some values specific to an identity (each stores its own key=values in the mgmt tomb).

Those values can then be used in scripts leveraging the risks CLI. A few usage examples might be storing names of VM destinations to be used in conjunction with risks load/save, directories where to put/find files, etc.

risks kv set MY_KEY myValue
risks kv get MY_KEY
risks kv list
risks kv unset MY_KEY
risks kv clean

Documentation to write.

Documentation to write.