Scott Gress
Scott Gress
As of version 4.63.0 Fleet added SLSA attestations to our released binaries and container images. This includes the Fleet server, fleetctl command-line tool (CLI), and Fleet's agent (specifically the Orbit component).
A software attestation is a cryptographically-signed statement provided by a software creator that certifies the build process and provenance of one or more software artifacts (which might be files, container images, or other outputs). In other words, it's a promise to our users that the software we're providing was built by us, using a process that they can trust and verify. We utilize the SLSA framework for attestations which you can read more about here. After each release, attestations are added to https://github.com/fleetdm/fleet/attestations.
Any Fleet release can be verified to prove that it was indeed created by Fleet, using the gh
command line tool from Github. See the gh attestation verify
docs for more info.
After downloading the Fleet server binary, here's how to verify:
gh attestation verify --owner fleetdm /path/to/fleet
Verify the fleetctl binary (CLI):
gh attestation verify --owner fleetdm fleetdm /path/to/fleetctl
Currently, you can verify Fleet's agent (fleetd) on macOS and Linux. To verify, after installing fleetd on a macOS or Linux host, run this command::
gh attestation verify --owner fleetdm /usr/local/bin/orbit