identityd: make backup copies of Node keypair or store it in an hardware vault

Open
#438 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
authentication, security

Research direction

The issue names no files, tests, or entry points. Start by locating identityd's Node keypair storage and boot-time disk-formatting flow, then resolve where backups belong and whether they must be encrypted. Done means the backup and boot-verification behavior are specified and implemented, with tests covering keypair recovery and formatting checks.

Written by the indexing model from the issue text.

Description

type_feature

in case a node loses the disk where the Node Keypair is stored, there would be no other way than to re-register the node as a new one.

We should have a backup somewhere and verify at boot, that if we need to format the system disk, there are no backup copies of the keypair.

Questions:

  • where do we put backups?
  • to encrypt or not encrypt, that's the question
Dominant language
Go
Stars
95
Forks
22
Avg merge
2m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from threefoldtech/zos

All issues in threefoldtech/zos

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.