Follow-ups found during the server admission and revocation effort
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 42m
- Merged PRs (30d)
- 11
Description
Tracking issue for work discovered during the server admission-control and emergency key-compromise effort (#107) that is real but explicitly out of scope for it — a future feature, a deferred hardening concern, or a decision that depends on later design work. Collected here as sub-issues so nothing gets lost.
Spec questions already routed to the spec author from this effort's design phase: #106 (third-party naked-revoke interpretation).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the parent effort in #107 and the collected sub-issues; #106 is already routed to the spec author for a third-party naked-revoke interpretation. Identify which follow-up has a settled scope and owner before starting; done means the selected deferred feature or hardening concern has an agreed design and an implemented, verifiable resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100