ACME: Improve Cloudflare documentation #1292
Open
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
Many guides on setting up ACME certs with Cloudflare in pfSense show filling out all five authentication fields. This is not required for acme.sh to work correctly and potentially exposes Cloudflare credentials with broad access though the pfSense UI and configuration backups. There are several ways that acme.sh can authenticate to Cloudflare, from least to most permissive: 1. Token with Zone.DNS:Edit permission and Zone ID. This only works with certs that cover a single zone. 2. Token with Zone.Zone:Read and Zone.DNS:Edit permission and Account ID. This works with certs that cover multiple zones. acme.sh uses the Account ID to look up all Zone IDs. 3. Global API key and email address. This is not recommended since it provides complete access to the entire Cloudflare account. References: https://github.com/acmesh-official/acme.sh/wiki/dnsapi#dns_cf acmesh-official/acme.sh#2398 acmesh-official/acme.sh@c25947d
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.
Many guides on setting up ACME certs with Cloudflare in pfSense show filling out all five authentication fields. This is not required for acme.sh to work correctly and potentially exposes Cloudflare credentials with broad access though the pfSense UI and configuration backups.
There are several ways that acme.sh can authenticate to Cloudflare, from least to most permissive:
Zone.DNS:Editpermission andZone ID. This only works with certs that cover a single zone.Zone.Zone:ReadandZone.DNS:Editpermission andAccount ID. This works with certs that cover multiple zones. acme.sh uses the Account ID to look up all Zone IDs.References:
https://github.com/acmesh-official/acme.sh/wiki/dnsapi#dns_cf
acmesh-official/acme.sh#2398
acmesh-official/acme.sh@c25947d