Follow-up to #492, from signing 27.1-rc.33 by hand.
The rc.33 SBOMs list 103 Debian packages for the server and nothing but the image for Relay (built FROM scratch). syft can't see the crates in a Rust binary unless the build records them.
Both Dockerfiles build with cargo auditable build (cargo-auditable 0.7.7, installed --locked in the builder stage). It adds the crate list to the binary as a small ELF section; syft, Trivy and Grype read it. Cached dependency builds are unaffected: it wraps only the workspace's own crates.
SBOM attestations move to actions/attest v4.2.2 (pinned by commit); actions/attest-sbom is deprecated.
The GHCR copies are verified after signing, as the Gitea ones are.
Images only build at tag time, so the first real test is rc.34: its SBOMs should list the crates, and gh attestation verify should pass as it did for rc.33.
Follow-up to #492, from signing 27.1-rc.33 by hand.
The rc.33 SBOMs list 103 Debian packages for the server and nothing but the image for Relay (built `FROM scratch`). syft can't see the crates in a Rust binary unless the build records them.
- Both Dockerfiles build with `cargo auditable build` (cargo-auditable 0.7.7, installed `--locked` in the builder stage). It adds the crate list to the binary as a small ELF section; syft, Trivy and Grype read it. Cached dependency builds are unaffected: it wraps only the workspace's own crates.
- SBOM attestations move to `actions/attest` v4.2.2 (pinned by commit); `actions/attest-sbom` is deprecated.
- The GHCR copies are verified after signing, as the Gitea ones are.
Images only build at tag time, so the first real test is rc.34: its SBOMs should list the crates, and `gh attestation verify` should pass as it did for rc.33.
The first signed release (27.1-rc.33, signed by hand) showed the SBOMs
list only the Debian packages in the server image, and nothing but the
image itself for Relay, which is built from scratch: syft cannot see the
crates in a Rust binary unless the build records them.
- Both images build with cargo-auditable 0.7.7, which puts the crate list
in the binary, where syft (and Trivy, Grype) read it.
- SBOM attestations use actions/attest v4.2.2; actions/attest-sbom is
deprecated.
- The GHCR copies are verified after signing, as the Gitea ones are.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #492, from signing 27.1-rc.33 by hand.
The rc.33 SBOMs list 103 Debian packages for the server and nothing but the image for Relay (built
FROM scratch). syft can't see the crates in a Rust binary unless the build records them.cargo auditable build(cargo-auditable 0.7.7, installed--lockedin the builder stage). It adds the crate list to the binary as a small ELF section; syft, Trivy and Grype read it. Cached dependency builds are unaffected: it wraps only the workspace's own crates.actions/attestv4.2.2 (pinned by commit);actions/attest-sbomis deprecated.Images only build at tag time, so the first real test is rc.34: its SBOMs should list the crates, and
gh attestation verifyshould pass as it did for rc.33.