You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: "Use ZIP archives to sign multiple files at once. (ZIP archives can also be signed and verified using the [JAR format](#jar-sign).)"
94
+
description: "Use ZIP archives to sign multiple files at once or to add additional files, like [SLSA provenance attestations](#create-provenance-file) (ZIP archives can also be signed and verified using the [JAR format](#jar-sign).)"
| `<xml-file>` | Root element name and namespace: `root-element-name`, `root-element-namespace` | [SBOM restrictions](examples#sbom-restriction)
751
751
752
+
## SLSA attestations {#create-provenance-file}
753
+
754
+
SignPath can create SLSA attestations for any of the supported build systems. See the [definition](/origin-verification/slsa-attestations) for more details.
755
+
756
+
Creating a SLSA attestation requires multiple directives:
757
+
758
+
*`<include-in-provenance>` to include a reference to a file in the generated provenance.
759
+
*`<create-provenance-file>` inside a root level `<zip-file>` to create a SLSA provenance.
760
+
*`<create-verification-summary-file>` to create a SLSA verification summary.
761
+
*`<create-attestation-signature>` to sign the provenance and turn them into a SLSA attestation or SLSA verification summary attestation (VSA).
762
+
763
+
The parameters for all these directives, except `<include-in-provenance>`, which does not have any, are listed below.
#### Verification of SLSA verification summaries (VSA) {#slsa-vsa-verification}
792
+
793
+
To verify a SLSA verification summary attestation (VSA), you need:
794
+
795
+
* The verification summary attestation file (e.g. `slsa-vsa.dsse.json` in the example above)
796
+
* The attestation signer certificate. For SLSA attestations created by SignPath, you can download [SignPath_SLSA.pem] for fully supported systems and [SignPath_SLSA-Beta.pem], which is a self-signed certificate, for all systems with preview support (See the [definition](/origin-verification/slsa-attestations) for a list of all supported systems).
797
+
* The publisher certificate
798
+
799
+
{:.panel.info}
800
+
> **`resource-uri`**
801
+
>
802
+
> SLSA specifies a `resource-uri` field with the intention of allowing a consumer to ensure that the software artifact was obtained from a trusted source. SignPath populates this field with information from the publisher certificate, in the form of
0 commit comments