libp2p / libp2p/go-libp2p-pubsub
Authorisation: Any plans?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 364
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
It would be highly useful if one would be able to authorize the subscription to and publishing of events. There are some small steps taken in that direction, e.g. [here](https://github.com/libp2p/go-libp2p-pubsub/blob/master/pubsub.go#L794), but this is not fully implemented yet. Are there any plans to do this in the near future?
[go-rpc](https://github.com/libp2p/go-libp2p-gorpc) recently received a very simple and powerful authorisation mechanism by providing a function to the rpc server, this could be a good guideline. For pubsub a split would make sense for publish and subscribe.
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 in pubsub.go around line 794 to understand the existing authorization-related steps, then review the go-rpc authorization mechanism linked in the issue. Define the scope for separately authorizing event publishing and subscription, with completion demonstrated by both paths enforcing the chosen authorization behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100