manifoldco / manifoldco/torus-cli
Gatekeeper: High Availability
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 603
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
The prototype of the Gatekeeper does not track or share any state, leaving a security vulnerability where a certificate could be turned in to multiple independent gatekeeper instances within the 5minute window for many different sets of credentials.
Therefore, in order for the Gatekeeper to be highly available, it requires some sort of consensus or data sharing mechanism for determining whether or not a certificate has been used. After the certificate window expires, it's no longer valid and can be forgotten.
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. Start by locating the Gatekeeper prototype and its certificate-use handling, then investigate a consensus or data-sharing approach; done means independent instances cannot accept the same certificate during the five-minute window and expired certificate state can be forgotten.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100