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

Checking enable content trust, but not checking prevent vuln images from running results in notary errors #6259

Closed
mhagen-vmware opened this issue Sep 8, 2017 · 5 comments
Closed

Checking enable content trust, but not checking prevent vuln images from running results in notary errors #6259

mhagen-vmware opened this issue Sep 8, 2017 · 5 comments
Labels
impact/doc/note Requires creation of or changes to an official release note kind/defect Behavior that is inconsistent with what's intended priority/p2

Comments

@mhagen-vmware
Copy link
Contributor 

Error while pulling image manifest: download failed: Unexpected http code: 412 (Precondition Failed), URL: https://10.161.107.186:443/v2/definitely-not-default/ubuntu/manifests/test, Message: The image is not signed in Notary.

My understanding is that content trust should just be whitelist and the prevent vuln image should be the notary check? Independent?
@mhagen-vmware mhagen-vmware added kind/defect Behavior that is inconsistent with what's intended priority/p2 labels Sep 8, 2017
@mdubya66 mdubya66 added the impact/doc/note Requires creation of or changes to an official release note label Sep 8, 2017
@mhagen-vmware
Copy link
Contributor Author

@reasonerjt Is this as expected?

@stuclem
Copy link
Contributor

stuclem commented Sep 12, 2017

@mhagen-vmware I see the kind/note flag, but isn't this covered by #6258?

@mhagen-vmware
Copy link
Contributor Author

Nope, 6258 is just dealing with enabling whitelisted mode, this issue is about whitelist/notary interaction. We have 2 check boxes. The first should just enable/disable whitelist, the second should just enable/disable vulnerability scanning. Right now the first one enables both.

@mhagen-vmware mhagen-vmware mentioned this issue Sep 12, 2017
Closed
@mhagen-vmware
Copy link
Contributor Author

Issue moved to vmware/harbor #3202 via ZenHub

@mhagen-vmware
Copy link
Contributor Author

moved this to harbor as that is the appropriate repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
impact/doc/note Requires creation of or changes to an official release note kind/defect Behavior that is inconsistent with what's intended priority/p2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mdubya66 @stuclem @mhagen-vmware