WebAssembly / WebAssembly/WASI
Require sockets to have a named "context"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
The APIs should require a named "context", tho it can be empty for POSIX runtimes. Then the CLI for "granting access" would take the context like so:
--allow-outbound=postgres@tcp://my.postgres.example:5432 --allow-outbound=https@tcp://*:443 --deny-outbound=https@tcp://my.internal.example:443
This would be useful in preventing SSRF. An application which does not support the use of named "context", like a POSIX runtime, would simply use an empty name for these, at the caveat of having weaker protection against SSRF.
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 WASI socket APIs and the CLI path that handles outbound access grants. Define how named contexts apply to the shown allow and deny forms, including empty contexts for POSIX runtimes. Done means the API requires a context and the CLI accepts the proposed context-bearing syntax while preserving the stated SSRF protection goal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, cli, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100