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
##Using artifact attestations to achieve SLSA v1 Build Level 3
1
+
# Using artifact attestations to achieve SLSA v1 Build Level 3
2
2
3
3
This project started to use GitHub Action to create attestations for the release artifacts. Building software with artifact attestation streamlines supply chain security and helps us achieve [SLSA](https://slsa.dev/) v1.0 Build Level 3 for this project.
4
4
5
-
### Verifying artifact attestations built with a reusable workflow
5
+
## Verifying release artifacts attestations with GitHub CLI
6
+
7
+
> [!WARNING]
8
+
> Not all artifacts may have attestations generated for them. Please check the [attestations](https://github.com/integrations/terraform-provider-github/attestations) page for this repository to see which artifacts have attestations available.
9
+
10
+
> [!CAUTION]
11
+
> The attestations are available only for the releases created since the version `v6.9.0` of this project.
12
+
13
+
### Prerequisites
14
+
15
+
First, install GitHub CLI if you haven't already. See the [installation instructions](https://github.com/cli/cli#installation) for your platform.
16
+
17
+
### Verifying attestations
6
18
7
19
To verify artifact attestations generated during the build process, use the `gh attestation verify` command from the GitHub CLI.
8
20
@@ -11,12 +23,6 @@ The `gh attestation verify` command requires either `--owner` or `--repo` flags
11
23
> [!NOTE]
12
24
> Make sure to replace X.Y.Z with the actual release tag you want to verify.
13
25
14
-
> [!WARNING]
15
-
> Not all artifacts may have attestations generated for them. Please check the [attestations](https://github.com/integrations/terraform-provider-github/attestations) page for this repository to see which artifacts have attestations available.
16
-
17
-
> [!CAUTION]
18
-
> The attestations are available only for releases created since the version `v6.9.0` of this project.
If you would like to require an artifact attestation to be signed with a specific workflow, use the `--signer-workflow` flag to indicate the workflow file that should be used.
> Not all the releases may have Cosign signature for the checksum files.
63
+
64
+
> [!CAUTION]
65
+
> The Cosign signatures are available only for the releases created since the version `v6.9.0` of this project.
66
+
67
+
In addition to artifact attestations, you can verify release artifacts using [Cosign](https://docs.sigstore.dev/cosign/overview/). Cosign is a tool for signing and verifying software artifacts and container images.
68
+
69
+
### Prerequisites
70
+
71
+
First, install Cosign if you haven't already. See the [installation instructions](https://docs.sigstore.dev/cosign/system_config/installation/) for your platform.
72
+
73
+
### Verify checksums file
74
+
75
+
> [!NOTE]
76
+
> Make sure to replace X.Y.Z with the actual release tag you want to verify.
77
+
78
+
Download the checksums file and its signature bundle:
0 commit comments