spinframework / spinframework/spin
Integrate outbound networking runtime config into all outbound factors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
We consistently enforce allowed_outbound_hosts; we should additionally integrate block_networks and client_tls runtime config where feasible. I think it's somewhat likely that there may be cases where block_networks will be infeasible to integrate, at least rigorously (without tricky DNS races); if so let's discuss how to deal with them case-by-case.
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
No files, tests, or entry points are named in the issue. Start by inventorying the outbound factors that already enforce allowed_outbound_hosts, then assess where block_networks and client_tls can be integrated. Done means the feasible factors enforce the additional runtime configuration and infeasible cases are documented for discussion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100