SaaSHub helps you find the best software and product alternatives Learn more →
Acme-dns-certbot-joohoi Alternatives
Similar projects and alternatives to acme-dns-certbot-joohoi
-
mkcert
A simple zero-config tool to make locally trusted development certificates with any names you'd like.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
acme-dns
Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
acme-dns-certbot-joohoi reviews and mentions
-
Is it okay to use letsencrypt for internet facing websites? I was going to buy a digicert cert. what's the downsides to letsencrypt vs paid public CAs?
Check this out https://github.com/joohoi/acme-dns-certbot-joohoi
-
my solution to domain, certificates, ports etc (zero cost and no external server or third-party service needed)
we can use tool such as certbot to get certificates from let's encrypt (in traditional way). and to get one using DNS-01 challenge you can use something like acme-dns-certbot. even further the addition of TXT DNS record can be automated using a provider (in our case duckdns) specific tool/plugin for example certbot_dns_duckdns
-
Ask HN: What's your solution for SSL on internal servers?
DNS alias mode:
* https://dan.langille.org/2019/02/01/acme-domain-alias-mode/
* https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mo...
* https://www.eff.org/deeplinks/2018/02/technical-deep-dive-se...
You want the name "internal.example.com". In your external DNS you create a CNAME from "_acme-challenge.internal.example.com" and point it to (e.g.) "internal.example.net" or "internal.dns-auth.example.com"
When you request the certificate you specify the "dns-01" method. The issuer (e.g., LE) will go to the the external DNS server for the look up, see that it is a CNAME and then follow the CNAME/alias, and do the verification at the final hostname.
So your ACME client has to do a DNS (TXT) record update, which can often be done via various APIs, e.g.:
* https://github.com/AnalogJ/lexicon
You can even run your own DNS server locally (in a DMZ?) if your DNS provider does not have an convenient API. There are servers written for this use case:
* https://github.com/joohoi/acme-dns
* https://github.com/joohoi/acme-dns-certbot-joohoi
* https://github.com/pawitp/acme-dns-server
-
A note from our sponsor - SaaSHub
www.saashub.com | 2 May 2024
Stats
joohoi/acme-dns-certbot-joohoi is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of acme-dns-certbot-joohoi is Python.
Sponsored