feat: Revocations & nonces

Open
#26 1 comment 0 reactions 0 assignees View on GitHub

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

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from n0-computer/rcan

All issues in n0-computer/rcan

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.