magic-wormhole / magic-wormhole/fowl
Put unix-sockets (back?) into the protocol
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 163
- Forks
- 14
- Avg merge
- 14h 58m
- Merged PRs (30d)
- 3
Description
When we upgraded to a named-services and "consent" model for each peer, the "anything goes, any Twisted endpoint string" part was lost.
It would be nice to be able to use Unix sockets again, though, so the protocol should be upgraded to allow that.
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 locating the implementation of the named-services and consent protocol, then trace how Twisted endpoint strings are parsed and authorized. Define how Unix-socket endpoints fit that protocol and verify that forwarding and peer consent still work for them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100