llnl / llnl/remote-mirror-security
Handling internal mirrors
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Based on the parsed .gitconfig we should be able to determine a remote mirror's origin. If the origin falls within a trusted domain, we should allow for separate handling (e.g. a "pass-through" policy).
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
Start by locating the code that parses .gitconfig and identifies remote mirrors. Trace how a mirror's origin is currently represented, then determine how trusted domains and a possible pass-through policy fit the existing security flow. Done means the intended handling is defined and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, ruby
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100