Shard PIN ownership policies #81

New Issue

Open

opened 2025-02-25 05:04:53 +00:00 by ryan · 0 comments

ryan commented

2025-02-25 05:04:53 +00:00

Owner

Relevant to keyfork mnemonic generate --shard-to-self.

PINs should be transferred with a file containing a PIN and the amount of smartcards provisioned. The PIN should not be human-readable, to prevent people from using the PINs as-is. A program should be built to allow for setting new PINs (admin and user, to the same PIN) based on the stored PIN, and must require all smartcards be provisioned. Something like:

key: "hex encoded aes-gcm key"
pin: "pin encrypted using the above key"
cards: 3

Relevant to `keyfork mnemonic generate --shard-to-self`. PINs should be transferred with a file containing a PIN and the amount of smartcards provisioned. The PIN should not be human-readable, to prevent people from using the PINs as-is. A program should be built to allow for setting new PINs (admin and user, to the same PIN) based on the stored PIN, and must require all smartcards be provisioned. Something like: ```yaml key: "hex encoded aes-gcm key" pin: "pin encrypted using the above key" cards: 3 ```

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#81

No description provided.