dehydrated-bigip-ansible
acme-dns
Our great sponsors
dehydrated-bigip-ansible | acme-dns | |
---|---|---|
1 | 37 | |
13 | 1,969 | |
- | - | |
0.0 | 0.0 | |
over 2 years ago | 12 days ago | |
Shell | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dehydrated-bigip-ansible
-
Another free CA as an alternative to Let's Encrypt
> I'm using the acme.sh client but the process will be similar no matter which client you choose to use.
Always nice to see some variety in clients along side the official Let's Encrypt one.
While we do use the official Python-based client at works at times, whenever I install it via apt, and it pulls in a whole bunch of dependencies, it's a bit disconcerting to me.
I'm a bit partial to dehydrated, which is a shell script (works under Bash and Zsh): I find it a lot easier to understand. It's handy to put on Linux/POSIX-based appliances like F5s, where the only prerequisites are Bash, cURL, and OpenSSL (and standard Unix tools like sed, grep, etc):
* https://devcentral.f5.com/s/articles/lets-encrypt-on-a-big-i...
* https://github.com/EquateTechnologies/dehydrated-bigip-ansib...
acme-dns
-
Subdomain.center – discover all subdomains for a domain
Getting a wildcard certificate from LE might be a better option, depending on how easy the extra bit of if plumbing is with your lab setup.
You need to use DNS based domain identification, and once you have a cert distribute it to all your services. The former can be automated using various common tools (look at https://github.com/joohoi/acme-dns, self-hosted unless you are only securing toys you don't really care about, if you self host DNS or your registrar doesn't have useful API access) or you can leave that as an every ~ten weeks manual job, the latter involves scripts to update you various services when a new certificate is available (either pushing from where you receive the certificate or picking up from elsewhere). I have a little VM that holds the couple of wildcard certificates (renewing them via DNS01 and acmedns on a separate machine so this one is impossible to see from the outside world), it pushes the new key and certificate out to other hosts (simple SSH to copy over then restart nginx/Apache/other).
Of course you may decide that the shin if your own CA is easier than setting all this up, as you can sign long lived certificates for yourself. I prefer this because I don't need to switch to something else if I decide to give friends/others access to something.
- Easy HTTPS for your private networks
-
I've created a solution for managing internal domains, how do I selfhost this more?
As someone else said, it’s a huge pain to run your own dns services. However, if you want some separation, I recently saw https://github.com/joohoi/acme-dns
-
LeGo CertHub v0.9.0 with Docker Support
v0.9.1 is out and natively supports both https://github.com/joohoi/acme-dns and any dns provider available in https://github.com/acmesh-official/acme.sh
-
How do you deal with SSL certs management?
I have set up an acme-dns server to answer ACME DNS Challenges: https://github.com/joohoi/acme-dns
- How to configure and use acme-dns?
-
What is a good alternative if port 80 is blocked?
The DNS challenge can be easily automated using https://github.com/joohoi/acme-dns - you do need an IP you can run a DNS server on though.
-
Setting up ssl on AGH
If your server is not accessible over the internet, you can still use Let's Encrypt or ZeroSSL to get a certificate. You'll just need to set up a DNS Challenge for things to work. This is a little more complicated, but can work even if your DNS provider doesn't have an API. For example, I use Google Domains and Google DNS (not cloud DNS) for my DNS server, but I've got an instance of acme-dns running on VPS box that handles the DNS auth for me. It's how every machine on my local network has valid certificates - but I annoyingly need to renew them every 90 days.
-
Did Manjaro just forget to renew the SSL certificate?
It's a bit more involved, but you can set up wildcard certificates to update automatically. Certbot has some pre-made plugins for this for several DNS providers. If yours is not on that list, there's a tool called acme-dns which is a minimal DNS server you can run on your server and delegate _acme-challenge.yourdomain.com to. If you don't want to run that on your own, you can also use the publicly hosted server/API for it.
-
Reverse proxy for internally hosted services
In case you're not already familiar with it: one thing I'd recommend is using https://github.com/joohoi/acme-dns to obtain the certificates. You basically just point the subdomain you need wildcard certs for at that DNS server (a one time thing, ie you don't have to do this every three months), and the related tool https://github.com/acme-dns/acme-dns-client can get the certificates in a nice, automated, way without you ever having to expose the private reverse proxy to the Internet.
What are some alternatives?
letsencrypt - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
acme.sh - A pure Unix shell script implementing ACME client protocol
lego - Let's Encrypt/ACME client and library written in Go
duckdns - Caddy module: dns.providers.duckdns
acme-tiny - A tiny script to issue and renew TLS certs from Let's Encrypt
acme-dns-server - Simple DNS server for serving TXT records written in Python
f5-azure-arm-templates - Azure Resource Manager Templates for quickly deploying BIG-IP services in Azure
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water