Closed dmitris closed 2 weeks ago
was able to verify an OCI image using trustedroot.json, the command was similar to this one, therefore changing from Draft to "Ready to review":
$ oci-image-verification -ociImage docker.internal.com:4443/name/xyz:1.0 -onlineTlog=false -requireTlog=false -ignore-sct=true -requireTimestamp=true -expectedIssuerRegex='.*' -expectedSAN='spiffe://cd.cisystem.project/cd/build12345' -trustedrootJSONpath=trustedroot.json
Verification successful!
{
"mediaType": "application/vnd.dev.sigstore.verificationresult+json;version=0.1",
"signature": {
"certificate": {
"certificateIssuer": "CN=[common name]",
"subjectAlternativeName": "spiffe://cd.cisystem.project/cd/build12345"
}
},
"verifiedTimestamps": [
{
"type": "TimestampAuthority",
"uri": "",
"timestamp": "2024-10-10T01:28:22Z"
}
],
"verifiedIdentity": {
"subjectAlternativeName": {
"subjectAlternativeName": "spiffe://cd.cisystem.project/cd/build12345"
},
"issuer": {
"issuer": "",
"regexp": ".*"
}
}
}
Summary
PR expands the oci-image-verification example with additional options for running it in a "private infrastructure" environment and to allow to extract non-Rekor-based timestamps from the OCI image being verified.
This is done in the mode of exploring the sigstore-go library and for now is a Draft - but I would appreciate any comments especially on whether the timestamp extraction is done correctly. When trying the
oci-image-verification
on an internally signed image (with TSA), I'm getting an error going back to ASN.1 parsing error (see my question on Slack):as mentioned in the Slack message, the "underlying" error is (???)
Release Note
NONE
Documentation
n/a