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
Copy file name to clipboardExpand all lines: README.md
+18
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,8 @@ ________
20
20
-[Artifacts](#artifacts-1)
21
21
-[Containers](#containers-1)
22
22
23
+
[Known Issues](#known-issues)
24
+
23
25
[Technical design](#technial-design)
24
26
-[Blog posts](#blog-posts)
25
27
-[Specifications](#specifications)
@@ -160,6 +162,22 @@ The verified in-toto statement may be written to stdout with the `--print-proven
160
162
161
163
Note that `--source-uri` supports GitHub repository URIs like `github.com/$OWNER/$REPO` when the build was enabled with a Cloud Build [GitHub trigger](https://cloud.google.com/build/docs/automating-builds/github/build-repos-from-github). Otherwise, the build provenance will contain the name of the Cloud Storage bucket used to host the source files, usually of the form `gs://[PROJECT_ID]_cloudbuild/source` (see [Running build](https://cloud.google.com/build/docs/running-builds/submit-build-via-cli-api#running_builds)). We recommend using GitHub triggers in order to preserve the source provenance and valiate that the source came from an expected, version-controlled repository. You *may* match on the fully-qualified tar like `gs://[PROJECT_ID]_cloudbuild/source/1665165360.279777-955d1904741e4bbeb3461080299e929a.tgz`.
162
164
165
+
## Known Issues
166
+
167
+
### tuf: invalid key
168
+
169
+
This will occur only when verifying provenance generated with GitHub Actions.
`slsa-verifier` will fail with the following error:
174
+
175
+
```
176
+
FAILED: SLSA verification failed: could not find a matching valid signature entry: got unexpected errors unable to initialize client, local cache may be corrupt: tuf: invalid key: unable to fetch Rekor public keys from TUF repository
177
+
```
178
+
179
+
This issue is tracked by [issue #325](https://github.com/slsa-framework/slsa-verifier/issues/325). You *must* update to the newest patch versions of each minor release to fix this issue.
0 commit comments