Skip to content

Commit

Permalink
docs(getting-started): add information about slsa attestor (#456)
Browse files Browse the repository at this point in the history
* docs(getting-started): fix missing dot in file name
* docs(getting-started): mention the slsa attestor in getting started

---------

Signed-off-by: Rémi REY <[email protected]>
Co-authored-by: Matthias Glastra <[email protected]>
  • Loading branch information
rrey and matglas authored Jun 1, 2024
1 parent b495cf7 commit f499ffb
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions docs/tutorials/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ openssl pkey -in testkey.pem -pubout > testpub.pem
> including Github Actions </span>
- This file generally resides in your source code repository along with the public keys generated above.
- `.witness yaml` is the default location for the configuration file
- `.witness.yaml` is the default location for the configuration file
- `witness help` will show all configuration options
- command-line arguments overrides configuration file values.

Expand All @@ -47,13 +47,16 @@ verify:
><span class="tip-text">💡 Tip: You can upload the recorded attestations to an [Archivista](https://github.com/in-toto/archivista) server by using the `--enable-archivista` flag!</span>
- The `-a {attestor}` flag allows you to define which attestors run
- ex. `-a maven -a gcp -a gitlab` would be used for a maven build running on a GitLab runner on GCP.
- Witness has a set of attestors that are always run. You can see them in the output of the `witness attestors list` command.
- Defining step names is important, these will be used in the policy.
- This should happen as a part of a CI step

```
witness run --step build -o test-att.json -- go build -o=testapp .
witness run --step build -o test-att.json -a slsa --attestor-slsa-export -- go build -o=testapp .
```

><span class="tip-text">💡 Tip: The `-a slsa` option allows to generate the [SLSA Provenace](https://slsa.dev/spec/v1.0/provenance) predicate in the attestation. The `--attestor-slsa-export` option allows to write the Provenance in a dedicated file. This is a mandatory requirement for SLSA Level 1</span>
### 4. View the attestation data in the signed DSSE Envelope

- This data can be stored and retrieved from Archivista
Expand Down

0 comments on commit f499ffb

Please sign in to comment.