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.

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

Add scenario for user-specified key #75

Merged
merged 1 commit into from
Jun 7, 2021

Conversation

mnm678
Copy link
Contributor

@mnm678 mnm678 commented Jun 5, 2021

This moves scenario 10 from #66 into it's own pr with a couple of minor clarifications.

@sudo-bmitch
Copy link
Contributor

LGTM

@mnm678
Copy link
Contributor Author

mnm678 commented Jun 7, 2021

@SteveLasker or @justincormack I don't have permission to merge in this repo, could you add this and #47?

@dlorenc
Copy link

dlorenc commented Jun 7, 2021

Lgtm as well!

Copy link
Contributor

@SteveLasker SteveLasker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with minor question, to be clarified later if needed, around collections of artifacts.


**Implications of this requirement**

1. Users must be allowed to configure specific trusted keys for specific artifacts or collections of artifacts.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wording around collections of artifacts might be inferred to something around a repository collection. As artifacts move within and across registries, a repository may have multiple signing keys.
I'll LGTM and we can clarify later if needed.

@SteveLasker SteveLasker merged commit d9e6c58 into notaryproject:main Jun 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants