getlantern / getlantern/unbounded
Add guardrails to prevent control plane messages from leaking into the BroflakeConn
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 57
- Forks
- 1
- Avg merge
- 20h 26m
- Merged PRs (30d)
- 13
Description
There's no problems with this currently, but it's a complicated and brittle subtlety which may confound future engineers.
In particular, the rules around passing control plane vs. data plane messages are ambiguous in the router code.
We should implement more formal rules around what kinds of messages can find their way back to workers and why.
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 by tracing the router code and the paths between control-plane or data-plane messages and BroflakeConn workers. Define and document formal message-routing rules, with completion indicated by guardrails that prevent control-plane messages from reaching BroflakeConn.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100