@@ -59,7 +59,7 @@
This Certification Practice Statement ("CPS") document outlines the certification services practices for this
particular instance running the LabCA software. PKI (Public Key Infrastructure) services include, but are not limited to, issuing, managing,
- validating, revoking, and renewing Certificates. The services are provided for [PKI_COMPANY_NAME] internal use only.
+ validating, revoking, and renewing Certificates. The services are provided for PKI_COMPANY_NAME internal use only.
The following Certification Authorities are covered under this CPS:
@@ -71,9 +71,9 @@
| Root CA |
- [PKI_ROOT_DN] |
- [PKI_ROOT_FINGERPRINT] |
- [PKI_ROOT_VALIDITY] |
+ PKI_ROOT_DN |
+ PKI_ROOT_FINGERPRINT |
+ PKI_ROOT_VALIDITY |
@@ -91,29 +91,29 @@
2. Publication and Repository
- This CPS is published at [LABCA_CPS_LOCATION]
+ This CPS is published at [LABCA_CPS_LOCATION]
Records of root and intermediate certificates, including those that have been revoked, are available at
- [LABCA_CERTS_LOCATION]
+ [LABCA_CERTS_LOCATION]
- LabCA certificates contain URLs to locations where certificate-related information is published, including
+ LabCA certificates contain URLs to locations where certificate-related information is published, including
revocation information via OCSP and/or CRLs.
3. Identification and Authentication
- LabCA certificates include a "Subject" field which identifies the subject entity (i.e. organization or domain). The
+ LabCA certificates include a "Subject" field which identifies the subject entity (i.e. organization or domain). The
subject entity is identified using a distinguished name.
- LabCA certificates include an "Issuer" field which identifies the issuing entity. The issuing entity is identified
+ LabCA certificates include an "Issuer" field which identifies the issuing entity. The issuing entity is identified
using a distinguished name.
4. Certificate Life-Cycle Operational Requirements
- Anyone associated with [PKI_COMPANY_NAME] may submit an application for a certificate via the ACME protocol. Issuance
+ Anyone associated with PKI_COMPANY_NAME may submit an application for a certificate via the ACME protocol. Issuance
will depend on proper validation and compliance with this PKI's policies. End-entity certificates are made available
to Subscribers via the ACME protocol as soon after issuance as reasonably possible.
@@ -134,17 +134,17 @@
Certificate revocation permanently ends the certificate's operational period prior to its stated validity period.
5. Facilities, Management, and Operational Controls
- Operating this PKI is under full responsibility of [PKI_COMPANY_NAME].
+ Operating this PKI is under full responsibility of PKI_COMPANY_NAME.
6. Technical Security Controls
- LabCA is not using a Hardware Security Module (HSM) for storing CA private keys. LabCA is intended
- to be used in a lab or intranet environment with sufficient protection against bad actors. It may not be used as
- publicly accessible PKI instance.
+ LabCA is not using a Hardware Security Module (HSM) for storing CA private keys.
+ LabCA is intended to be used in a lab or intranet environment with sufficient protection against
+ bad actors. It may not be used as publicly accessible PKI instance.
7. Certificate, CRL, and OCSP Profile
- Any requirements or policies regarding Certificates, CRLs and OCSP are at full discretion of [PKI_COMPANY_NAME].
+ Any requirements or policies regarding Certificates, CRLs and OCSP are at full discretion of PKI_COMPANY_NAME.
8. Compliance audit
Not applicable.
diff --git a/static/index.html b/static/index.html
index e244430..8e428b5 100644
--- a/static/index.html
+++ b/static/index.html
@@ -27,7 +27,7 @@
- LabCA
+ LabCA