oxidecomputer / oxidecomputer/omicron
[wicket] finish up TCP-MD5 BGP auth work
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
This is mostly done, but some questions:
- Should we display information about a key in a way that users can verify it, and if so how? Current proposal is SHA-256 sum which is pretty weak. Can we use a stronger hash?
- Do we want to use the keychain approach for other kinds of keys? (e.g. key/cert pairs?)
Contributor guide
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 by reviewing the existing TCP-MD5 BGP authentication work referenced in the title, then resolve the two open questions about verifiable key information and extending the keychain approach to key/certificate pairs. Done means the design questions have clear decisions and the remaining work is finished.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100