Quick sharding mnemonics without a wizard #61

New Issue

Open

opened 2025-01-14 21:59:41 +00:00 by ryan · 4 comments

ryan commented

2025-01-14 21:59:41 +00:00

Owner

keyfork mnemonic generate --size 256 --shard --certificates ./certificates --threshold 3 --max 5

``` keyfork mnemonic generate --size 256 --shard --certificates ./certificates --threshold 3 --max 5 ```

ryan commented

2025-01-14 22:00:32 +00:00

Author

Owner

Note that this is functionally equivalent to:

keyfork mnemonic generate --size 256 | keyfork shard split --threshold 3 --max 5 ./certificates

Note that this is functionally equivalent to: ``` keyfork mnemonic generate --size 256 | keyfork shard split --threshold 3 --max 5 ./certificates ```

ryan commented

2025-01-14 22:24:07 +00:00

Author

Owner

We can also include an --encrypt-to option to encrypt a mnemonic to a previously-known disaster recovery certificate, that works either independently of, or in combination with, the previous shard commands.

We can also include an `--encrypt-to` option to encrypt a mnemonic to a previously-known disaster recovery certificate, that works either independently of, or in combination with, the previous shard commands.

ryan commented

2025-01-14 23:07:35 +00:00

Author

Owner

keyfork mnemonic generate --size 256 --shard --certificates ./certificates --threshold 3 --max 5 --encrypt-to dr1.asc --encrypt-to dr2.asc --shard-to shard1.asc --shard-to shard2.asc

dr1 and dr2 are OpenPGP certificates. shard1 and shard2 are previously-created Shardfiles. certificates are OpenPGP certificates used for sharding. An operator for every shard must be present to decrypt the same metadata packet, with the same certificates and m-of-n threshold being reused.

``` keyfork mnemonic generate --size 256 --shard --certificates ./certificates --threshold 3 --max 5 --encrypt-to dr1.asc --encrypt-to dr2.asc --shard-to shard1.asc --shard-to shard2.asc ``` `dr1` and `dr2` are OpenPGP certificates. `shard1` and `shard2` are previously-created Shardfiles. `certificates` are OpenPGP certificates used for sharding. An operator for every shard must be present to decrypt the same metadata packet, with the same certificates and m-of-n threshold being reused.

ryan commented

2025-01-16 21:32:42 +00:00

Author

Owner

keyfork mnemonic generate --size 256 --encrypt-to self --start-server could be used to:

generate the mnemonic
encrypt the mnemonic text to the default OpenPGP key
start a Keyfork server with the mnemonic

Starting the Keyfork server is only a valid option of --encrypt-to, --shard, or --shard-to are passed, to ensure the mnemonic is in some way preserved.

`keyfork mnemonic generate --size 256 --encrypt-to self --start-server` could be used to: 1. generate the mnemonic 2. encrypt the mnemonic text to the default OpenPGP key 3. start a Keyfork server with the mnemonic Starting the Keyfork server is only a valid option of `--encrypt-to`, `--shard`, or `--shard-to` are passed, to ensure the mnemonic is in some way preserved.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/keyfork#61

No description provided.