-
Notifications
You must be signed in to change notification settings - Fork 395
OpenShift native signatures #14
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
Conversation
0c44ed5 to
653fd7a
Compare
| // SignedClaims map[string]string `json:"signedClaims,omitempty"` | ||
| // Created *unversioned.Time `json:"created,omitempty"` | ||
| // IssuedBy SignatureIssuer `json:"issuedBy,omitempty"` | ||
| // IssuedTo SignatureSubject `json:"issuedTo,omitempty"` |
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.
What's up with all of these commented out fields? Something to be used in the future?
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.
Those fields exist in the upstream OpenShift objects, and we do not use them (In particular these should be filled in by the server, to have something to display in an UI, so we want to neither fill them in (the server will override that) nor read them (we want to make independent policy decisions without trusting the server)).
This ~ only acknowledges their existence, and unlike uncommented fields we do not need to define the used types etc.
b3f068a to
ea18e1e
Compare
fc7b499 to
a2e8c82
Compare
27c8657 to
3ebb1e8
Compare
321ab65 to
9a6b762
Compare
|
Updated against the final merged API from openshift/origin#9181 . I'm afraid this still requires a cluster-wide signature privilege, but it does work and it is hopefully already useful. |
|
See also containers/skopeo#93 for the necessary |
Read imagestreamimage to read signatures. Add signatures one by one. The signatures are shared for a single image across any namespaces, so we don’t delete (others’) signatures. Note that this currently requires a cluster-wide signature write privilege, system:image-signer! A minimal configuration to make this work, though leaving permissions wide open, is > oadm policy add-cluster-role-to-group system:image-signer system:authenticated Signed-off-by: Miloslav Trmač <[email protected]>
9a6b762 to
f1bc742
Compare
Actually it does, because even |
This adds support for storing signatures in Atomic Registry, assuming server-side support per (merged) openshift/origin#8371 and (currently unmerged) openshift/origin#9181 .
(Marked as WIP because the server side is missing, and because this currently requires a cluster-wide “update signatures” privilege, which seems impractical, so future changes of the API cannot be ruled out. Also, this is currently done as 2 commits to preserve the 2 possible ways to upload signatures, after the decisions are final they should be squashed.)