Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add scenario 12 for chaining from a trusted key #96

Merged
merged 3 commits into from
Aug 23, 2021
Merged

Add scenario 12 for chaining from a trusted key #96

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9a974b5
Add scenario 12 for chaining from a trusted key
mnm678 Aug 19, 2021
26ae329
Combine implications and use registry terminology
mnm678 Aug 20, 2021
fdcd10b
Update scenarios.md
mnm678 Aug 23, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions scenarios.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -275,6 +275,18 @@ A signer determines that a signed artifact is no longer trusted. This could be a
1. Attackers attempting to replay revoked signatures should be detected by the verification.
1. Revoking the signature for a single artifact should not require revoking the signer's key or signatures for all other artifacts by the same signer.

### Scenario #12: Chaining from a trusted key

If a user does not have a specific key for a given artifact, verified using a third party system, they will need to determine the trusted signing key(s) for an artifact by chaining from a trusted key.

1. The user determines the trusted key(s) for a specific artifact using delegations from a trusted root.
1. The user downloads and verifies an artifact using Notary v2 and the trusted key(s) discovered in the previous step.

**Implications of this requirement**

1. Users must be able to to access a chain of trust that links the signing key for a particular artifact to a trusted root.
1. Users must be able to configure roots of trust.

## Open Discussions

* What is the relationship between a signature, an artifact and a registry?
Expand Down