Backup Key File In Case User Forgets Keynode Passphrase

[robert-cronin]

make a key file for backup for unlocking the keynode - currently we only have root keypair (i.e. passphrase ). However the user can forget his passphrase and its better that we have a backup keyfile that could still unlock the keynode
@gideonairex

[robert-cronin]

I am actually not sure that kbpgp does anything like this natively but we can achieve similar functionality by storing a mirrored version of the vault keys in a separate file that is somehow protected by that backup key file

[robert-cronin]

I will add this into the next PR as I think it will be relatively straight forward to implement.

[CMCDragonkai]

We have a recovery code system similar to bip39 mnemonics. That should be sufficient to solve this problem. See the screenshots that @faithveloro has worked on.

[faithveloro]

Attaching screenshots here:

[robert-cronin]

I am currently integrating https://github.com/bitcoinjs/bip39 into the key manager for mnemonic generation, my one concern is that kbpgp keys are not currently deterministic (strictly speaking they are but not to us) because the salt/seed is not transparent or definable when generating a new keypair. So my alternative thought was to store this mnemonic in the KeyManager and then have the mnemonic maintain an encrypted copy of the vault keys on file (can do this with symmetric encryption) so if the user ever forgets their passphrase, the whole keynode can be restored via that encrypted file.

[robert-cronin]

another issue here is that the vault keys are currently stored in each vault to localise vault information as well as avoid large cryptographic operations on a single, centralised vault key file in the case of very many vaults. We can just maintain an encrypted file within each vault alongside the existing vault key.

[robert-cronin]

Closing on account of migration to gitlab