Hayden B
Hayden B
This FAQ item is no longer present
We have documentation for https://docs.sigstore.dev/signing/signing_with_containers/#key-stored-in-google-cloud-kms, no need to include how to create the key too.
Huge +1 to everything you've written @olivekl, this looks like a great plan. Focusing on the user journeys will greatly improve the documentation. > Where should we keep developer docs...
@jonvnadelberg can you take a look at these comments, particularly https://github.com/sigstore/docs/issues/167#issuecomment-1554582533?
Agreed to dropping "are there any privacy issues". "Why not blockchain" - I'd lean towards dropping. It requires a deeper level of understanding about how blockchain works vs a transparency...
I don't think we need a breakdown of every argument. Help text when running the CLI should be sufficient. It also keeps the source of truth with the CLI rather...
The first part of this is a dup of https://github.com/sigstore/docs/issues/117 I do like that idea of exploring automation and having developer focused documentation come from the repos!
We should also document what the SET is not, a proof of an entry being in the log. This has come up a few times that the SET is sufficient...
1 sounds like a good approach
> Staging doesn't include a timestamp authority that is reachable from the general internet (arguably this could be fixed) I didn't catch that we were using the [sigstore/timestamp-authority](https://github.com/sigstore/timestamp-authority/blob/main/pkg/client/timestamp_client.go) client in...