You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a requirement, or ability to provide Transparency signing log? Specifically when signatures were issued, what was the raw sha256 and authenticode sha256 of the object signed, as well as some obfuscated indicator of what was signed and/or potentially public identifier (guid) of the vendor for whom signature was issued?
Could this be extended to signatures produced by certificates vendored into 3rd-party shims too?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a requirement, or ability to provide Transparency signing log? Specifically when signatures were issued, what was the raw sha256 and authenticode sha256 of the object signed, as well as some obfuscated indicator of what was signed and/or potentially public identifier (guid) of the vendor for whom signature was issued?
Could this be extended to signatures produced by certificates vendored into 3rd-party shims too?
Possibly using something like https://docs.sigstore.dev/logging/overview/ ?
Note one can use rekor transparency log without using fulcio based signatures.
Beta Was this translation helpful? Give feedback.
All reactions