[SSL] Update certificate authorities info #16679
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deploying cloudflare-docs with
|
| Latest commit: |
9b86289
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3af8ceea.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://rebecca-ssl-ssl-com-and-entr.cloudflare-docs-7ou.pages.dev |
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 11021221 | Triggered | Generic High Entropy Secret | 9512a1c | astro.config.mjs | View secret |
| 11021221 | Triggered | Generic High Entropy Secret | 9512a1c | astro.config.mjs | View secret |
| 11021221 | Triggered | Generic High Entropy Secret | 9512a1c | astro.config.mjs | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
![hyperlint-ai[bot]](https://avatars.githubusercontent.com/in/718456?s=60&v=4){kind=small}
| @@ -21,7 +21,7 @@ Yes. Cloudflare can issue both RSA and ECDSA certificates. | |||
|
|
|||
| ### Which certificate authorities does Cloudflare use? | |||
|
|
|||
| Cloudflare uses Let’s Encrypt, Google Trust Services, Sectigo, and DigiCert. You can see a complete list of products and available CAs and algorithms in the [certificate authorities reference page](/ssl/reference/certificate-authorities/). | |||
| Cloudflare uses Let’s Encrypt, Google Trust Services, SSL.com, Sectigo, and DigiCert. You can see a complete list of products and available CAs and algorithms in the [certificate authorities reference page](/ssl/reference/certificate-authorities/). | |||
There was a problem hiding this comment.
Suggested change
| Cloudflare uses Let’s Encrypt, Google Trust Services, SSL.com, Sectigo, and DigiCert. You can see a complete list of products and available CAs and algorithms in the [certificate authorities reference page](/ssl/reference/certificate-authorities/). | |
| Cloudflare uses 'Let's Encrypt', Google Trust Services, SSL.com, Sectigo, and DigiCert. You can see a complete list of products and available CAs and algorithms in the [certificate authorities reference page](/ssl/reference/certificate-authorities/). |
Issues:
- Style Guide - (cloudflare.NonStandardQuotes-warning) Use standard single quotes or double quotes only. Do not use left or right quotes.
Fix Explanation:
The original text uses a non-standard apostrophe in 'Let’s Encrypt'. According to the style guide, we should replace it with a standard single quote. The replacement text uses a standard single quote for 'Let's Encrypt'. This change aligns with the style guide's requirement to avoid left or right quotes. No other changes are necessary.
wolruf
reviewed
Sep 18, 2024
src/content/docs/ssl/edge-certificates/custom-certificates/index.mdx
Outdated
Show resolved
Hide resolved
pedrosousa
approved these changes
Sep 18, 2024
src/content/docs/ssl/edge-certificates/custom-certificates/index.mdx
Outdated
Show resolved
Hide resolved
| @@ -8,7 +8,9 @@ description: For publicly trusted certificates, Cloudflare partners with | |||
| different certificate authorities (CAs). Refer to this page to check what CAs | |||
| are used for each Cloudflare offering and for more details about the CAs | |||
| features, limitations, and browser compatibility. | |||
|
|
|||
| banner: | |||
There was a problem hiding this comment.
Hadn't seen this being used yet!
Maybe we can discuss when we should use it in critique?
RebeccaTamachiro
deleted the
rebecca/ssl-ssl-com-and-entrust-distrust
branch
|
Closes #15902 |
vy-ton
pushed a commit
that referenced
this pull request
Sep 19, 2024
* Add ssl.com to certificate-authorities reference page * Update caa-records-added-by-cf partial * Refer ssl.com in other places where CAs used by CF are listed * Add help link to ct-monitoring page * Add ssl.com to custom hostname docs * More information on availability and timeline * Add entrust-distrust and re-order items within migration-guides * Overall review of entrust-distrust and certificate-authorities * Call out CF certificates as alternative to custom issued by same CAs * Fix repeated Digicert info in CAA record content table * Fix SSL.com availability in general CA to cert type table * Update SSL.com browser compatibility with cross-sign info * Add SSL.com DCV tokens validity * Fix issue flagged in Hyperlint check * Update distrust dates * Fix date for Mozilla * Apply suggestions from code review Co-authored-by: Pedro Sousa <[email protected]> * Fix beta capitalization and move content from banner to aside * Update backup-certificates.mdx * Fix apostrophe and remove banner --------- Co-authored-by: Pedro Sousa <[email protected]>
elithrar
pushed a commit
that referenced
this pull request
Oct 15, 2024
* Add ssl.com to certificate-authorities reference page * Update caa-records-added-by-cf partial * Refer ssl.com in other places where CAs used by CF are listed * Add help link to ct-monitoring page * Add ssl.com to custom hostname docs * More information on availability and timeline * Add entrust-distrust and re-order items within migration-guides * Overall review of entrust-distrust and certificate-authorities * Call out CF certificates as alternative to custom issued by same CAs * Fix repeated Digicert info in CAA record content table * Fix SSL.com availability in general CA to cert type table * Update SSL.com browser compatibility with cross-sign info * Add SSL.com DCV tokens validity * Fix issue flagged in Hyperlint check * Update distrust dates * Fix date for Mozilla * Apply suggestions from code review Co-authored-by: Pedro Sousa <[email protected]> * Fix beta capitalization and move content from banner to aside * Update backup-certificates.mdx * Fix apostrophe and remove banner --------- Co-authored-by: Pedro Sousa <[email protected]>
maheshwarip
pushed a commit
that referenced
this pull request
Dec 2, 2024
* Add ssl.com to certificate-authorities reference page * Update caa-records-added-by-cf partial * Refer ssl.com in other places where CAs used by CF are listed * Add help link to ct-monitoring page * Add ssl.com to custom hostname docs * More information on availability and timeline * Add entrust-distrust and re-order items within migration-guides * Overall review of entrust-distrust and certificate-authorities * Call out CF certificates as alternative to custom issued by same CAs * Fix repeated Digicert info in CAA record content table * Fix SSL.com availability in general CA to cert type table * Update SSL.com browser compatibility with cross-sign info * Add SSL.com DCV tokens validity * Fix issue flagged in Hyperlint check * Update distrust dates * Fix date for Mozilla * Apply suggestions from code review Co-authored-by: Pedro Sousa <[email protected]> * Fix beta capitalization and move content from banner to aside * Update backup-certificates.mdx * Fix apostrophe and remove banner --------- Co-authored-by: Pedro Sousa <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
PCX-11622
PCX-11971