Supply Chain Security
Agent 1.1.2 is our first signed release. You can check every file below without trusting us.
What is signed
Each file is signed with our release key. Each has a .sig file next to it.
- SHA256SUMS: SHA256SUMS (.sig)
- Build record (provenance): provenance-1.1.2.json (.sig)
- SBOM, agent (CycloneDX): sbom-agent-1.1.2.cdx.json (.sig)
- SBOM, backend (CycloneDX): sbom-backend-1.1.2.cdx.json (.sig)
Public key: cosign.pub. Its SHA-256 is dd9309ca6a2290b6eb7d7f2e42eff02011fbb19228ac5d956381dc56a01d6566 (also in cosign.pub.sha256). Check it before you trust it.
Check it yourself
With cosign (version 2.2.4 and 3.1.3 both work):
cosign verify-blob --key cosign.pub --insecure-ignore-tlog=true --signature sbom-agent-1.1.2.cdx.json.sig sbom-agent-1.1.2.cdx.json With only OpenSSL:
base64 -d sbom-agent-1.1.2.cdx.json.sig > sig.bin
openssl dgst -sha256 -verify cosign.pub -signature sig.bin sbom-agent-1.1.2.cdx.json Each should print Verified OK. Change one byte of the file and it fails. Then check the files against the signed list: sha256sum --check SHA256SUMS (the agent package line only works if you have the package, which we send on request).
What this does and does not cover
- It shows the files were released by the holder of our key and have not changed since.
- We use a key we hold ourselves. We do not use a public transparency log, which is why the command says
--insecure-ignore-tlog=true. - The build record is a signed statement of which workflow and which source commit made the release. It is not an independent third-party certification.
- The agent package itself is not on this site. Ask for it and check it against the signed list.
- Only agent 1.1.2 is covered. Earlier versions are not signed.
Questions?
For detailed security information or custom attestation requirements: