You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sigstore-public-deployment-spec.md
+5-19Lines changed: 5 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,11 +27,6 @@ Fulcio implements a certificate authority for issuing code signing certificates
27
27
28
28
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).
29
29
30
-
These certificates have a validity period of 10 minutes, beginning at the time of issuance.
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:
62
57
63
58
**Workflow Authentication**
64
59
65
-
* GitHub
66
-
* GitLab
60
+
* GitHub Actions
61
+
* GitLab CI
67
62
* BuildKite
63
+
* CodeFresh
68
64
69
65
See the [Fulcio OIDC documentation](https://github.com/sigstore/fulcio/blob/main/docs/oidc.md) for additional details.
70
66
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
-
75
67
## 3. Rekor
76
68
77
69
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
80
72
81
73
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).
82
74
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/)
84
76
85
77
See the transparency service ([Spec: Rekor](https://docs.google.com/document/u/0/d/1NQUBSL9R64_vPxUEgVKGb0p81_7BVZ7PQuI078WFn-g/edit)) document for additional information.
86
78
@@ -91,12 +83,6 @@ Rekor is backed by a transparency log, inspired by the one in Certificate Transp
91
83
* Base URL: [https://rekor.sigstore.dev/](https://rekor.sigstore.dev/)
92
84
* Hash Algorithm: SHA-256 ([RFC 6234](https://datatracker.ietf.org/doc/rfc6234/); OID 2.16.840.1.101.3.4.2.1)
93
85
* 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
100
86
101
87
### 3.3 Sharding
102
88
@@ -169,4 +155,4 @@ The Sigstore project provides the resources necessary to deploy private Sigstore
0 commit comments