lbryio / lbryio/wallet-sync-server
Update test_client with the latest plan for key derivation
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The plan for which components do the encryption, and which/how many keys are derived from root password, is a little up in the air, and it's not my decision now. Once it's decided and implemented, I'll match test_client to it.
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
Wait for the encryption and key-derivation plan to be decided and implemented, then inspect test_client and align its expectations with the settled behavior. Confirm which components perform encryption and which keys are derived from the root password; done when test_client matches the implemented plan and passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100