oxidecomputer / oxidecomputer/omicron
basic hardening of externally-facing server
Open
Nobody has claimed this yet.
mvp
security
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Tracking issue for testing (and probably fixing) basic hardening of the external API/console server, like that we close connections that have been open and idle (several cases).
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 locating the externally-facing API and console server entry points and reviewing how connections are tracked. Test the several idle-connection cases described in the issue, then verify that open idle connections are closed as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100