-
Notifications
You must be signed in to change notification settings - Fork 44
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
Notary v2 initial scenarios #1
Conversation
Signed-off-by: Steve Lasker <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @SteveLasker for putting this together!
Signed-off-by: steve lasker <[email protected]>
Signed-off-by: Steve Lasker <[email protected]>
Signed-off-by: Steve Lasker <[email protected]>
Thanks for starting this, @SteveLasker, I think it's a great start! I wonder whether we could also add the full power of delegations from the TUF 1.0.0 specification? The reason why I ask is because I think we could radically simplify the signing model for most developers this way. Using the full power of delegations, we can require developers to manage one signing key instead of four ( |
Signed-off-by: Steve Lasker <[email protected]>
Signed-off-by: Steve Lasker <[email protected]>
Signed-off-by: steve lasker <[email protected]>
Signed-off-by: steve lasker <[email protected]>
Signed-off-by: Steve Lasker <[email protected]>
I've incorporated feedback, and created a cleaner PR #7 |
End to end scenarios, accounting for PR #1 feedback
End to end scenarios, accounting for PR notaryproject#1 feedback Signed-off-by: Justin Cappos <[email protected]>
Signed-off-by: Steve Lasker [email protected]