Security
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 5h 52m
- Merged PRs (30d)
- 4
Description
Currently, the public IP has no domain, and therefore no ability to do HTTPS.
Therefore, GitHub has to send the WebHook secret in plain text, and it can (maybe, theoretically?) be sniffed.
So we should probably only allow running benchmarks on branches and tags, not arbitrary commits (as GitHub stores a fork’s PR commits in the parent repo)
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, tests, or entry points are named. Start by tracing how GitHub webhook events select benchmark commits, then determine how branch and tag refs are represented and where arbitrary commit runs are accepted; done means untrusted webhook data cannot trigger runs for arbitrary commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100