dehydrated
certificates
Our great sponsors
dehydrated | certificates | |
---|---|---|
36 | 40 | |
5,886 | 6,154 | |
3.4% | 3.0% | |
2.3 | 9.5 | |
about 2 months ago | 3 days ago | |
Shell | Go | |
MIT License | Apache License 2.0 |
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
-
Dehydrated: Letsencrypt/acme client implemented as a shell-script
From this commit:
https://github.com/dehydrated-io/dehydrated/commit/b116e6bc2...
-
Running one’s own root Certificate Authority in 2023
I've had a lot of success with https://github.com/dehydrated-io/dehydrated . It exposes the different parts of the process (deploy challenge to DNS, deploy cert to filesystem, etc) as hooks, so it's pretty easy to integrate with anything and however you want, if you don't mind writing a bit of bash. There's a few scripts out there that use Cloudflare that you can use as well.
-
How do you renew SSL certificates?
Depend on host's capability... - lego - dehydrated - caddy - in case it already works as a web server, it will automatically issue and renew certs
-
SSL cert for DSM on Synology
Take a look at this great project : https://github.com/dehydrated-io/dehydrated/wiki : many dns providers are documented.
-
Write Posix Shell
> Oh, and that 500-line shell script probably ends up being a 5000-line Python monster anyway.
The dehydrated ACME client is 2400 lines of bash/zsh:
* https://github.com/dehydrated-io/dehydrated
And its external dependencies are OpenSSL and cURL. The acme.sh shell ACME client is 8000 lines of shell:
* https://github.com/acmesh-official/acme.sh
The official Let's Encrypt client is written in Python, and the core 'executable' is much longer, and in addition it pulls in a boatload of dependencies:
* https://packages.debian.org/bullseye/python3-certbot
-
ZeroSSL: XSS to session hijacking, stealing a private key (and password hash)
Dehydrated.io, damn few dependencies.
You're welcome.
https://github.com/dehydrated-io/dehydrated
-
Looking for help with VIRTUAL_HOST set up and 502 Bad Gateway (possible bad SSL?)
I prefer dehydrated as an ACME client because it's written in bash and the only dependencies are sed, awk, grep, and openssl. This will also leave you free to customize your nginx config as necessary without having to try to cram your needs into a generator that doesn't account for what you're trying to do. It seems odd to me that the generator would create the intermediary file (as per your quoted output above), but then not put that in the nginx config.
-
Knowing when to tell somone to call it quits...
This project has helped us immensely with cert renewals - https://github.com/dehydrated-io/dehydrated
- Does it really suck this much to set up SSL?
- Canonical releases Ubuntu 22.10 Kinetic Kudu
certificates
-
You shouldn't run NSA-grade Wi-Fi at home
You can roll your own with https://github.com/smallstep/certificates. We maintain major open source projects and contribute a lot to other projects. I don’t think that means everything we do has to be open source. Sorry this one wasn’t. Doing this in pure open source would be a book, not a blog post.
Love Let’s Encrypt — we’re sponsors — but using them for WiFi is a terrible idea. You need internal PKI for WiFi.
- Running one’s own root Certificate Authority in 2023
-
Distributing ACME Let'sEncrypt certs for homelab
letsencrypt was always about moving the public internet off of http, it doesn't really make sense to use it throughout your internal network. but if you really want TLS and ACME for auto renewal, other solutions are available: https://github.com/smallstep/certificates
-
SSH With SSO
You could try step-ca: https://github.com/smallstep/certificates. There’s an OIDC provisioner for SSO and you can sign (short-lived) SSH certificates with it.
-
Web application to manage self-signed certificate authorities/certificates/keys
You could also check out out Step CA: https://github.com/smallstep/certificates and the accompanying CLI. It has an ACME server and other methods for requesting certificates. It can work/integrate with your existing root(s), too.
- Selfhosted CA tutorial
-
ACME setup. Domain required?
This is a lot more complicated setup but it works for me. I run a private CA called step-ca from smallstep and it provides CA and ACME endpoint. I use a .home domain. The trick is the validation for non-http devices which is typically the DNS-01 challenge. For this, I have unbound in pfsense setup to work with acme-dns so I can keep everything internal. Again its complicated but if your learning cyber security it might help get a handle on all things TLS. Btw way behind the scenes I think the ACME plugin is really just running acme.sh bash script which is really good. Final reminder as other have stated. Private CA is great but you need to distro the roots and intermediates out to your clients for trust. If all your trying to do is have an https web gui for pfsense from one device its pretty easy.
-
A convert from Judaism to Catholicism goes to r/Catholicism to ask if it would be appropriate to pass down a century old Jewish prayer shawl to his son. Not everyone is welcoming.
Just a little heads up https://smallstep.com/certificates/
-
Looking for an open source certificate management solution.
Step-ca: Not web based, but the CLI is pretty user friendly: https://smallstep.com/certificates/
-
Using k8s-apiserver as AAA server for microservices?
I was just looking at https://smallstep.com/certificates a few days ago. It looks like they have an operator that fits your description as well as example docs for setting up inter-microservice mtls.
What are some alternatives?
acme.sh - A pure Unix shell script implementing ACME client protocol
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
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.
boulder - An ACME-based certificate authority, written in Go.
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
omgwtfssl - SSL certificate generation for developers who don't TLS good
lego - Let's Encrypt/ACME client and library written in Go
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit
synology-tls - Automatically Update Let's Encrypt Wildcard Certificates for Synology NAS
easy-rsa - easy-rsa - Simple shell based CA utility
portainer-traefik-letsencrypt - This repository will help you install Portainer with Traefik and Let's Encrypt with much ease!
traefik-certs-dumper - Dump ACME data from Traefik to certificates