Description
The build stage of the pipeline generates SBOMs using this logic:
docker-tools/eng/common/templates/jobs/build-images.yml
Lines 128 to 176 in 9791b15
The use of the ManifestGeneratorTask is only used as an "installer" in order to acquire the manifest tool that gets executed in the second step. It's done this way because of the need to have a separate SBOM for each image (see #979). So the SBOM generation occurs in the second step. But the logic for signing the SBOMs actually occurs in the first step via the ManifestGeneratorTask. This means we're not getting the benefit of signing because we're not using the task to generate the SBOMs. And that means none of our SBOMs are signed.
I've logged a related issue for the manifest generator to have another tool that can be used for signing: https://github.com/microsoft/dropvalidator/issues/668
Metadata
Metadata
Assignees
Type
Projects
Status