263
edits
Changes
Jump to navigation
Jump to search
Line 20:
Line 20: − + − + − + + + + + + +
GC HTTPS Certificate Guidance (view source)
Revision as of 10:06, 11 April 2019
, 10:06, 11 April 2019→Automated Certificate Management Engine (ACME)
===Automated Certificate Management Engine (ACME)===
===Automated Certificate Management Engine (ACME)===
<u>[https://tools.ietf.org/html/rfc8555 RFC 8555: Automatic Certificate Management Environment]</u><br>
<u>[https://tools.ietf.org/html/rfc8555 RFC 8555: Automatic Certificate Management Environment]</u><br>
''Public Key Infrastructure using X.509 (PKIX) certificates are used for a number of purposes, the most significant of which is the authentication of domain names. Thus, certification authorities (CAs) in the Web PKI are trusted to verify that an applicant for a certificate legitimately represents the domain name(s) in the certificate. As of this writing, this verification is done through a collection of ad hoc mechanisms. This document describes a protocol that a CA and an applicant can use to automate the process of verification and certificate issuance. The protocol also provides facilities for other certificate management functions, such as certificate revocation.'' For details, see the IETF document here: https://tools.ietf.org/html/rfc8555
''Public Key Infrastructure using X.509 (PKIX) certificates are used for a number of purposes, the most significant of which is the authentication of domain names. Thus, certification authorities (CAs) in the Web PKI are trusted to verify that an applicant for a certificate legitimately represents the domain name(s) in the certificate. As of this writing, this verification is done through a collection of ad hoc mechanisms. This document describes a protocol that a CA and an applicant can use to automate the process of verification and certificate issuance <u>on Linux platforms</u>. The protocol also provides facilities for other certificate management functions, such as certificate revocation.'' For details, see the IETF document here: https://tools.ietf.org/html/rfc8555
<br><br>
<br><br>
From the Datatracker, published 2019-03-12: https://datatracker.ietf.org/doc/rfc8555/
From the Datatracker, published 2019-03-12: https://datatracker.ietf.org/doc/rfc8555/
<br><br>
<br>
CAs & PKIs that offer ACME certificates
# [https://www.buypass.com/ssl/acme Buypass]
# [https://letsencrypt.org Let's Encrypt]
# [https://www.entrustdatacard.com/knowledgebase/how-to-use-acme-to-install-ssl-tls-certificates-in-entrust-certificate-services-apache Entrust (Linux)]
# [https://www.globalsign.com/en-au/auto-enrollment-gateway/ GlobalSign]
# [https://www.venafi.com/ Venafi]
# [https://sectigo.com/resources/sectigos-acme-automation Sectigo (formerly Comodo CA)]
===Wildcard Certificates===
===Wildcard Certificates===
