mirror of
https://github.com/acme-dns/acme-dns.git
synced 2026-04-27 04:45:48 +03:00
[GH-ISSUE #59] Client implementations #21
Labels
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/acme-dns#21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @joohoi on GitHub (Mar 18, 2018).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/59
Acme-dns needs client implementations for clients in order to be useful. If you have written a client implementation, please let me know, and I'll add a link to it to the
README.mdfor people to find and use.Currently the only publicly available client implementation that I know of is a Certbot authentication hook that can be found at: https://github.com/joohoi/acme-dns-certbot . This can be used as a reference for ways to handle the credential storage and communication towards acme-dns instance.
@MrBMT commented on GitHub (Mar 20, 2018):
I didn't make it, but there's also another Certbot hook written in Go: https://github.com/koesie10/acme-dns-certbot-hook
I found and used this to generate my first LE Wildcard certs, as it was before you'd created your hook.
@joohoi commented on GitHub (Mar 20, 2018):
Thanks! I'll add it to the list.Done.
@danb35 commented on GitHub (Apr 7, 2018):
acme.sh appears to work with acme-dns; its instructions are near the bottom of the page at https://github.com/Neilpang/acme.sh/blob/master/dnsapi/README.md.
@joohoi commented on GitHub (Apr 8, 2018):
Awesome news! I'll add a link to the docs.
@Ajedi32 commented on GitHub (May 15, 2018):
Not sure if this counts as a separate client or not, but pfSense supports it via the ACME plugin's integration with ACME.sh:
@joohoi commented on GitHub (May 15, 2018):
This is cool! Could probably list it under a section of "Other" or similar.
In general though, I feel that the acme.sh client implementation is somewhat lacking, as it expects a single set of acme-dns credentials for the entire certificate instead of credentials per domain. This approach has caveats that we went into detail in discussion here.
This isn't an issue in typical pfSense installation, but I hope it would get fixed in acme.sh, although the acme.sh architecture might make it hard. acme-dns is a different beast than typical DNS APIs.
@viralpoetry commented on GitHub (Mar 10, 2020):
Hi,
there is now also ACME-DNS DNS Authenticator plugin for Certbot
https://github.com/pan-net-security/certbot-dns-acmedns