keylime / keylime/rust-keylime
Revocation should be retried with ACK given from agent
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 162
- Forks
- 76
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 3
Description
Currently each revocation notice is sent only once, and this could pose a problem for nodes that are either offline for that period or are still going through setup. It seems better to get an ACK from each node that it received the revocation notice, and have some mechanism to try resending it if it is not acknowledged.
Do we know that there isn't currently a mechanism in Keylime for this type of retry?
@lukehinds This one came from our conversation.
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
The issue names no files or tests. Start by locating the revocation-notice sender and the agent-side ACK handling, then verify whether Keylime already has retry logic. Done means agreeing on the ACK and resend behavior for offline or still-setup nodes and covering that behavior with tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100