-
## Bug Report
**Describe the bug**
See https://github.com/fluent/fluent-bit/actions/runs/8380464955/job/22949896795, looks like cosign updates are required to resolve. Signing with the key worke…
-
We should try to turn on this option if possible, stapling or anything the server supports.
-
**Description**
After the migration of OIDC providers to the new configuration in https://github.com/sigstore/fulcio/pull/1743/files
signing from Codefresh is failing when scm_repo_url is not prov…
-
**Description**
In a Bring your Own PKI scenario, a user may want to specify a CRL file ( in addition to a fullchain file ) that can be used to check if the certificate embedded in a signature arti…
-
Copying from the doc, from @segiddins: this bullet has some inaccuracies in it:
* The leaf certificate has SANs, not a subject (the subject is empty, since we only use SANs)
* The leaf's SANs shou…
-
We now have support for SPIFFE IDs, and federation through https://github.com/sigstore/fulcio/pull/107!
This means we can issue certs for subjects like `spiffe://somedomain.com/foo/bar`, and authen…
-
Currently we support a variety of different signers, including Fulcio and Vault PKI, but these all will result in private key material being loaded into memory to sign data locally.
We should be ab…
-
**Description**
Remove the GitHub TSA as it's not used by anything. It's being removed from the production repo too, see https://github.com/sigstore/root-signing/issues/1268
Add `signing_config.json…
-
https://github.com/theupdateframework/taps/pull/141/files
This basically requires two things:
(1) Adding an optional `cert` key-value pair into the signature
(2) Signature verification will inclu…
asraa updated
2 years ago
-
**Description**
See https://github.com/namely/docker-protoc
This solves the issue of a mismatch between the locally installed protoc and the one used to check for updated generated code in t…