multiformats / multiformats/multiaddr
How to handle SSL/TLS?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 482
- Forks
- 87
- PR merge metrics
- No merged PRs in 30d
Description
If an address is listening for TLS connections, how should that be encoded? Encoding X509 certificates seems particularly tricky. You could base64 encode the certificates, but that is variable length, which the format doesn't seem to handle right now.
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
The issue names no files, tests, or entry points. Start by reviewing the multiaddr encoding rules and the unresolved SSL/TLS and X509 questions; done means the representation and certificate-handling approach are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100