getlantern / getlantern/unbounded
Reverse the Broflake connection flow to improve blocking resistance?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 57
- Forks
- 1
- Avg merge
- 20h 26m
- Merged PRs (30d)
- 13
Description
On Slack, @hwh33 said:
have we considered reversing the connections for Broflake? I think we've seen a lot to suggest that inbound connections are less heavily scrutinized than outbound ones. I'm really not sure how well substantiated that is though.
Concretely, this means making sure that the uncensored peer is the one who initiates the DTLS handshake.
IIRC, with WebRTC, the DTLS client/server roles are determined during signaling. I can't remember exactly how this works. Does it correspond to the controlling agent and controlled agent that are designated during ICE?
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
No files or tests are named. Start by tracing Broflake's signaling and ICE role assignment, then verify how those roles determine the DTLS client/server side; done means establishing whether reversing initiation is supported and validating the resulting inbound/outbound connection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100