Keypairs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Code review comment (PR #8) from @dob regarding:
priv, pub, _ := crypto.GenerateKeyPair(crypto.RSA, 2048)
Note for the future that we may want to use an ECDSA keypair to match the ethereum ecosystem. Then again, I had a discussion this week about the need for a less computationally expensive encryption method for low latency streaming. I'm not familiar enough with the alternatives. I could see us using the ECDSA secp256k1 curve for handshake and key exchange in the kademlia "tracker" discovery, and then using something lighter for PPSPP.
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
Start with the crypto.GenerateKeyPair(crypto.RSA, 2048) call referenced in PR #8 and read the surrounding key-exchange code. Compare the issue's ECDSA, kademlia tracker, and PPSPP considerations, but note that no algorithm or implementation scope is decided. Done cannot be defined until that design choice is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100