Skip to content

Commit 0cefb44

Browse files
committed
Fix signature
1 parent 9fda86b commit 0cefb44

File tree

2 files changed

+1
-31
lines changed

2 files changed

+1
-31
lines changed

.github/workflows/docker-release.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,7 @@ jobs:
3737
username: ${{ secrets.DOCKERHUB_USERNAME }}
3838
password: ${{ secrets.DOCKERHUB_TOKEN }}
3939
- uses: docker/build-push-action@0adf9959216b96bec444f325f1e493d4aa344497 # v6.14.0
40+
id: build
4041
with:
4142
context: ${{ env.IMAGE }}
4243
platforms: linux/amd64,linux/arm64

README.md

Lines changed: 0 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -106,37 +106,6 @@ The following checks were performed on each of these signatures:
106106

107107
For instructions on how to install `cosign`, please read this [documentation](https://docs.sigstore.dev/cosign/system_config/installation/).
108108

109-
### Sigstore
110-
111-
[Sigstore](https://docs.sigstore.dev) is trying to improve supply
112-
chain security by allowing you to verify the origin of an
113-
artifcat. You can verify that the jar that you use was actually
114-
produced by this repository. This means that if you verify the
115-
signature of the ristretto jar, you can trust the integrity of the
116-
whole supply chain from code source, to CI/CD build, to distribution
117-
on Maven Central or whever you got the jar from.
118-
119-
You can use the following command to verify the latest image using its
120-
sigstore signature attestation:
121-
122-
```bash
123-
cosign verify leplusorg/xml --certificate-identity-regexp 'https://github\.com/leplusorg/docker-av/\.github/workflows/.+' --certificate-oidc-issuer 'https://token.actions.githubusercontent.com'
124-
```
125-
126-
The output should look something like this:
127-
128-
```text
129-
Verification for index.docker.io/leplusorg/xml:main --
130-
The following checks were performed on each of these signatures:
131-
- The cosign claims were validated
132-
- Existence of the claims in the transparency log was verified offline
133-
- The code-signing certificate was verified using trusted certificate authority certificates
134-
135-
[{"critical":...
136-
```
137-
138-
For instructions on how to install `cosign`, please read this [documentation](https://docs.sigstore.dev/cosign/system_config/installation/).
139-
140109
## Request new tool
141110

142111
Please use [this link](https://github.com/leplusorg/docker-xml/issues/new?assignees=thomasleplus&labels=enhancement&template=feature_request.md&title=%5BFEAT%5D) (GitHub account required) to request that a new tool be added to the image. I am always interested in adding new capabilities to these images.

0 commit comments

Comments
 (0)