opensafely-core / opensafely-core/proxy
Limit the users that the proxy will hand out SSH keys for
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 1
Description
I'm not sure how easy this would be (or worthwhile), but was wondering whether we should allowlist the Github usernames that we hand out SSH keys for via this proxy - this would add an extra layer of safeguarding in case of incorrect usernames.
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 in the issue. First trace how the proxy resolves GitHub usernames and hands out SSH keys, then clarify where an allowlist comes from and how rejected users should behave. Done should include agreed allowlist semantics and coverage for allowed and disallowed usernames.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100