Recover
Recovering is putting the chain right after a loss. The loss may be a card, a PIN, the ledger, or access to a cloud account. The answer depends on what was lost and what you prepared.
What was lost
Section titled “What was lost”| Lost | What it means | The answer | Needs |
|---|---|---|---|
| One of two root cards | The root on it can no longer sign. If the card was stolen with its PIN, it can sign for someone else. | Revoke it, publish trust products without it, add a replacement root, re-sign what chained only to it. | The other card; the stored revocation certificate. |
| A card whose PIN is forgotten | After three wrong tries it blocks; the PUK unblocks it, and a full reset destroys the keys. | Treat it as a lost card. | The same. |
| Both root cards | No root can sign. | Start again with a new root, and persuade every client to trust it. A disaster you prepared for by keeping the cards in two places. | The backup of the ledger; a plan for the clients. |
| The ledger | The registry, the attestations and the OpenPGP creation times. | Restore it from its backup. | The backup. Without one, rebuild what the published certificates carry and accept the rest as lost. |
| A revocation certificate | The only way to revoke a master key whose card is gone. | Make a new one now, while the card is still there. | The card and its PIN. |
| A cloud root account | The key is a permission, and the permission is gone. | Restore access through the provider; otherwise it is a lost root. | A replica in another Region covers a lost Region, not a lost account. |
| A software key | Depends on the store. | Restore from the store’s own replication, if it has any. | See where a key lives. |
The same chain, whole again
Section titled “The same chain, whole again”Every recovery has the same shape:
- Contain. If the key can be used by someone else, revoke it first.
- Rebuild redundancy. Add a replacement root so there are two again.
- Re-sign. What chained only to the lost root gets a certificate from the surviving root, over the same keys.
- Publish. New trust products, after an overlap that your slowest client needs.
- Record. What was done, with which keys.
- Practise. Run the drill so the next recovery is not the first.
Replacement, not copy
Section titled “Replacement, not copy”A card is never replaced by a copy of its key, because a card cannot be copied. A lost root is replaced by a new root, made on a new card, that the surviving root vouches for. That is the same transition as any other (moving from one root to another), done in a hurry.
In ritueel
Section titled “In ritueel”The guide for a lost root card walks through it, and the backup and restore guide covers the ledger.