@@ -253,6 +253,37 @@ docker buildx imagetools inspect leplusorg/openid-connect-provider-debugger --fo
253253
254254Replace ` linux/amd64 ` by the desired platform (` linux/amd64 ` , ` linux/arm64 ` etc.).
255255
256+ ### Sigstore
257+
258+ [ Sigstore] ( https://docs.sigstore.dev ) is trying to improve supply
259+ chain security by allowing you to verify the origin of an
260+ artifcat. You can verify that the jar that you use was actually
261+ produced by this repository. This means that if you verify the
262+ signature of the ristretto jar, you can trust the integrity of the
263+ whole supply chain from code source, to CI/CD build, to distribution
264+ on Maven Central or whever you got the jar from.
265+
266+ You can use the following command to verify the latest image using its
267+ sigstore signature attestation:
268+
269+ ``` bash
270+ cosign verify leplusorg/openid-connect-provider-debugger --certificate-identity-regexp ' https://github\.com/leplusorg/docker-av/\.github/workflows/.+' --certificate-oidc-issuer ' https://token.actions.githubusercontent.com'
271+ ```
272+
273+ The output should look something like this:
274+
275+ ``` text
276+ Verification for index.docker.io/leplusorg/xml:main --
277+ The following checks were performed on each of these signatures:
278+ - The cosign claims were validated
279+ - Existence of the claims in the transparency log was verified offline
280+ - The code-signing certificate was verified using trusted certificate authority certificates
281+
282+ [{"critical":...
283+ ```
284+
285+ For instructions on how to install ` cosign ` , please read this [ documentation] ( https://docs.sigstore.dev/cosign/system_config/installation/ ) .
286+
256287## Credits
257288
258289This project is based on NGINX / OpenResty and all the actual OpenID
0 commit comments