feat: Revocations & nonces
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- authorization, security
Research direction
Start with the Authorizer function and the delegation representation, then review issue #25 for the store abstraction. Define how revocation payloads are represented and checked against the used delegation chain, add a nonce so equivalent delegations can differ, and update the RCAN version consistently.
Written by the indexing model from the issue text.
Description
RCAN delegations should be revokable.
Revocations are a payload with:
- version
- public key of the principal that issues the revocation
- the delegation that is revoked
- signature over all of the above
The Authorizer function should support revocations by looking up if the current delegations appear in the used delegation chain (for this we should also implement an abstraction for a store: #25).
To be able to re-issue delegations that were revoked with the same capabilities, we need to make sure that we can create an RCAN that doesn't look byte-identical to the revoked RCAN.
To enable that, we should add a "nonce" parameter to delegations.
These changes imply a new RCAN version
- Dominant language
- Rust
- Stars
- 27
- Forks
- 4
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from n0-computer/rcan
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
n0-computer/rcan#59 ·
-
Difficulty 5/5 Over a week Newbie friendliness 32/100
n0-computer/rcan#43 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
n0-computer/rcan#30 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
n0-computer/rcan#25 ·
All issues in n0-computer/rcan
Similar issues
-
area:web kind:bug priority:p2 ready
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
sims1253/r-typeshed#140 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/craft-libs#2867 ·
Maintainers usually reply within 1 day
-
help wanted needs investigation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100