Skip to content

Commit b643501

Browse files
authored
Clean up based on review
- remove unnecessary lines from 2.1 code signing certificates - add codefresh and update github actions and gitlab ci - remove SPIFFE section - Fix link to pluggable types - Remove extras in 3.2 Tlog section Signed-off-by: Tracy Miranda <[email protected]>
1 parent d3f2951 commit b643501

File tree

1 file changed

+5
-19
lines changed

1 file changed

+5
-19
lines changed

sigstore-public-deployment-spec.md

Lines changed: 5 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -27,11 +27,6 @@ Fulcio implements a certificate authority for issuing code signing certificates
2727

2828
Fulcio embeds information about the identity of a requester into the SubjectAlternativeName, Issuer, and extensions of a [RFC 5280](https://www.rfc-editor.org/rfc/rfc5280)\-compliant [X.509v3](https://www.itu.int/rec/T-REC-X.509) certificate. The certificates are signed by an intermediate certificate generated from a [GCP Key Management Service](https://cloud.google.com/kms/docs/) key and the root certificate authority is hosted via [GCP Certificate Authority Service](https://cloud.google.com/certificate-authority-service/). Both the intermediate certificate and root certificate are distributed via TUF implemented in the [sigstore/root-signing repository](https://github.com/sigstore/root-signing).
2929

30-
These certificates have a validity period of 10 minutes, beginning at the time of issuance.
31-
32-
* [Fulcio certification specification](https://github.com/sigstore/fulcio/blob/main/docs/certificate-specification.md)
33-
* General OIDs
34-
3530
### 2.2 Authentication
3631

3732
Fulcio issues [RFC 5280](https://www.rfc-editor.org/rfc/rfc5280)\-compliant [X.509v3](https://www.itu.int/rec/T-REC-X.509) certificates encoding identity information. It must authenticate the identities which it encodes into these certificates. For additional information, see [OIDC Usage in Fulcio](https://github.com/sigstore/fulcio/blob/main/docs/oidc.md).
@@ -62,16 +57,13 @@ Dex:
6257

6358
**Workflow Authentication**
6459

65-
* GitHub
66-
* GitLab
60+
* GitHub Actions
61+
* GitLab CI
6762
* BuildKite
63+
* CodeFresh
6864

6965
See the [Fulcio OIDC documentation](https://github.com/sigstore/fulcio/blob/main/docs/oidc.md) for additional details.
7066

71-
#### 2.2.2 SPIFFE
72-
73-
[Secure Production Identity Framework for Everyone](https://spiffe.io/) (SPIFFE) uses X.509 certificates to provide identity. SPIFFE-based OIDC providers use a SPIFFE ID as the URI subject alternative name of the certificate, scoped to a domain.
74-
7567
## 3. Rekor
7668

7769
Rekor implements a transparency service. There is a public good deployment of Rekor run by the [OpenSSF](https://openssf.org/) and contributing organizations at [https://rekor.sigstore.dev/](https://rekor.sigstore.dev/).
@@ -80,7 +72,7 @@ Rekor implements a transparency service. There is a public good deployment of Re
8072

8173
The transparency service has what is termed a ‘pluggable type’ system. A pluggable type, is a custom schema for entries stored in the transparency log. Schemas can be in multiple formats (json|yaml|xml).
8274

83-
The current list of supported types can be found in the [Rekor project](https://github.com/sigstore/rekor/tree/main/pkg/types). Information about adding new pluggable types can be found in the [Rekor documentation.](https://docs.sigstore.dev/docs/logging/pluggable-types/)
75+
The current list of supported types can be found in the [Rekor project](https://github.com/sigstore/rekor/tree/main/pkg/types). Information about adding new pluggable types can be found in the [Rekor documentation.](https://docs.sigstore.dev/logging/pluggable-types/)
8476

8577
See the transparency service ([Spec: Rekor](https://docs.google.com/document/u/0/d/1NQUBSL9R64_vPxUEgVKGb0p81_7BVZ7PQuI078WFn-g/edit)) document for additional information.
8678

@@ -91,12 +83,6 @@ Rekor is backed by a transparency log, inspired by the one in Certificate Transp
9183
* Base URL: [https://rekor.sigstore.dev/](https://rekor.sigstore.dev/)
9284
* Hash Algorithm: SHA-256 ([RFC 6234](https://datatracker.ietf.org/doc/rfc6234/); OID 2.16.840.1.101.3.4.2.1)
9385
* Signature Algorithm: ECDSA (NIST P-256).
94-
* Public Key: change over time
95-
* Log ID: need an OID
96-
* Maximum Merge Delay: Rekor only returns after the merge is complete
97-
* Maximum Chain Length: 10
98-
* STH Frequency Count: N/A
99-
* Final STH: N/A
10086

10187
### 3.3 Sharding
10288

@@ -169,4 +155,4 @@ The Sigstore project provides the resources necessary to deploy private Sigstore
169155
* [sigstore/helm-charts](https://github.com/sigstore/helm-charts)
170156
* [sigstore/scaffolding](https://github.com/sigstore/scaffolding)
171157
* [sigstore/sigstore-probers](https://github.com/sigstore/sigstore-probers)
172-
* [sigstore/policy-controller](https://github.com/sigstore/policy-controller)
158+
* [sigstore/policy-controller](https://github.com/sigstore/policy-controller)

0 commit comments

Comments
 (0)