nuts-foundation / nuts-foundation/nuts-node
Refactor crypto.SavePrivateKey and crypto.Link
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Both are mainly used for tests and are there for either convenience or for a test which uses predefined keys. This is not really needed.
crypto.SavePrivateKey is also used to migrate your keys from one backend to another. The goal is to use a backend that doesn't support exporting private keys (or you do it outside of nuts and change the SQL db to map accordingly)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by locating all usages of crypto.SavePrivateKey and crypto.Link, separating test convenience from the private-key migration path. Determine how migration should work when a backend cannot export private keys, then update the affected callers and tests while preserving key migration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100