Trust and supply chain

Every WAFio release bundle is signed with Ed25519, checksummed with SHA-256 and described by a published manifest. The installer checks the checksum and the signature against the release public key before it installs anything. You can run the same checks yourself on any machine.

ReleaseSigned bundleInstallerChecks bothInstalledBoth passRefusedCheck failsReleaseSigned bundleInstallerChecks bothInstalledBoth passRefusedCheck fails
  • Genuine bundle
  • Altered bundle

How a release is verified

A bundle is built, signed and listed in a manifest. The installer checks the checksum and the signature before it installs, and stops if either one fails.

BuildBundle, SBOMSignHash, versionManifestSHA-256, keyInstallerinstall.shSHA-256 checksumEd25519 signatureBuilt-in public keyInstallBoth passRefusedStopsBuildBundle, SBOMSignHash, versionManifestSHA-256, keyInstallerinstall.shSHA-256 checksumEd25519 signatureBuilt-in public keyInstallBoth passRefusedInstall stops
  • Genuine bundle
  • Altered bundle, refused

Build and sign

Each release bundle is signed with an Ed25519 key.

Publish the manifest

The release manifest lists the SHA-256 checksum and the signature of each bundle, and the public key.

Check at install

The installer has the public key built in and refuses a bundle that is unsigned, signed by another key, or whose manifest names a different public key.

Current release

Loading the release manifest.

Signing key

Release bundles are signed with an Ed25519 key. install.sh has the public key built in and refuses a bundle that is unsigned, signed by another key, or whose manifest names a different public key.

Verify a download

Run these on any machine after downloading. They use the same public key and payload format as install.sh.

  1. Checksum the artefact

    Compare the output with the hash published in the release manifest.

    curl -fsSL https://wafio.cloud/api/download/waf-agent | shasum -a 256
  2. Check the Ed25519 signature

    Fetch the signature JSON, rebuild the payload and verify it against the published key. The final verify needs OpenSSL 3.x. The command finds it automatically (macOS: run brew install openssl@3 once).

    curl -fsSL https://wafio.cloud/api/download/waf-agent/sig | python3 -c 'import sys,json,base64,urllib.request; d=json.load(sys.stdin); open("sig.b64","w").write(d["signature"]); open("payload","w").write("wafio-release-v1\n%s\n%s" % (d["version"], d["sha256"])); k=base64.b64decode(json.load(urllib.request.urlopen("https://wafio.cloud/api/download/manifest"))["public_key"]); open("pub.pem","w").write("-----BEGIN PUBLIC KEY-----\n"+base64.encodebytes(bytes.fromhex("302a300506032b6570032100")+k).decode()+"-----END PUBLIC KEY-----\n")' && base64 -d < sig.b64 > sig.bin && ( O="$(brew --prefix openssl@3 2>/dev/null)/bin/openssl"; [ -x "$O" ] || O=openssl; "$O" pkeyutl -verify -pubin -inkey pub.pem -rawin -in payload -sigfile sig.bin )
  3. Scan the SBOM

    grype checks every dependency listed in the bundle against known CVEs.

    curl -fsSL -o bundle.sbom.json https://wafio.cloud/api/download/waf-agent/sbom && grype sbom:bundle.sbom.json

Report a security issue

Send reports to hello@wafio.cloud. We credit responsible disclosure. A /.well-known/security.txt is published on this domain.

Scope
Portal, control plane, agents and eBPF programs.