Verify Before You Run: How an OpsChain Release Is Signed, and How You Check It
A platform that governs your operations is the most privileged binary on the host. Before it runs anything, you should be able to prove that what you downloaded is what we built, that it has not been altered, and that it came from us. "Should" is not enough; it has to be three commands you can run and a result you can file.
This post explains how an OpsChain release is signed and how you verify one.
Three axes of signing
macOS. The binaries carry a Developer ID Application signature by LimePoint Pty Ltd (Team ID 5VMU6KAJU2) and are notarised by Apple. Gatekeeper admits them without a bypass. codesign shows the authority chain and the team identifier; the Install page shows the certificate's SHA-256 so you can compare it.
Windows. opschain.exe carries an Authenticode signature by LimePoint Pty Ltd. Get-AuthenticodeSignature reports it valid; the certificate's SHA-256 is on the Install page as well.
Every platform. The release's SHA256SUMS.txt lists the digest of every archive, and the sums file itself is sealed with a cosign signature under the OpsChain release key. The public half of that key is pinned in the product repository and shipped beside the release; the installer script carries it too. Verify the seal, then the digest, and you have verified the archive without trusting the download path.
How the seal is made
The release train builds the six platform archives and publishes them to a private release. Signing then runs on hosted runners that hold the certificates: the macOS job signs and notarises both architectures, the Windows job applies Authenticode, and a seal job writes SHA256SUMS.txt over the final set and signs it with the release key. The train refuses to continue if the signing key does not match the pinned public key, and it records the certificate fingerprints from the signing jobs into the release manifest. The public release is assembled only from that sealed set, and the Install page renders its facts from the manifest: nothing on that page is typed by hand.
The three commands
Download the archive for your platform together with SHA256SUMS.txt, its signature and the release public key from the public releases repository. Then:
# 1. The pinned key is the one you expect (byte-identical to the key in the product repository)
diff opschain-release.pub <(curl -fsSL https://raw.githubusercontent.com/LimePoint/opschain-releases/main/opschain-release.pub)
# 2. The sums file is sealed by that key
cosign verify-blob --key opschain-release.pub --signature SHA256SUMS.txt.sig SHA256SUMS.txt
# 3. Your archive matches the sealed sums
shasum -a 256 --ignore-missing -c SHA256SUMS.txt
On macOS, add codesign -dv --verbose=2 ./opschain and expect TeamIdentifier=5VMU6KAJU2. On Windows, Get-AuthenticodeSignature .\opschain.exe | Format-List and expect Valid with LimePoint Pty Ltd as the signer.
The package managers and the installer
Homebrew (brew install limepoint/tap/opschain) and Scoop (scoop install limepoint/opschain) install the same archives; their manifests are regenerated from the sealed sums on every cut, so a manager install verifies the digest for you. On Linux, the installer script resolves your platform, downloads the archive and SHA256SUMS.txt, verifies the digest before extracting anything, verifies the cosign seal when cosign is installed, and never runs sudo itself. Download it and read it before you run it; it is short on purpose. This release ships archives for Linux, not .deb or .rpm packages; a later release adds those beside the archives.
What you can file
The Install page for a release carries the digest table, both certificate fingerprints and the pinned key block, all generated from the release manifest. Your verification output, the manifest and the release's integration report form a record of what you installed and why you trusted it. For an estate under CPS 234 or SOCI obligations, that is the supply-chain evidence the control asks for, produced by the same discipline that governs the changes the binary will run.
OpsChain v5 is available by invitation. Request access, and when your download arrives, run the three commands first.
Key takeaway
Developer ID and notarisation, Authenticode, and a cosign-sealed sums file under a pinned key: three commands verify an OpsChain download before it runs, and the Install page shows every fingerprint from the release manifest, none typed by hand.
Ready to see OpsChain in action?
Book a personalised demo and see how OpsChain can transform your operations.
Book a DemoFounder & CEO, LimePoint
Goran is the founder of LimePoint and the creator of OpsChain. He is passionate about helping enterprises automate and govern their operations at scale.