dehydrated
cfssl
Our great sponsors
| dehydrated | cfssl | |
|---|---|---|
| 36 | 24 | |
| 5,886 | 8,457 | |
| 3.4% | 1.4% | |
| 2.3 | 7.5 | |
| about 2 months ago | 8 days ago | |
| Shell | Go | |
| MIT License | BSD 2-clause "Simplified" 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
-
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
cfssl
- Running one’s own root Certificate Authority in 2023
- Selfhosted CA tutorial
-
i must be the only guy that understands certificates
cfssl is kinda outright better version of that.
-
SSL certificate problem: unhandled critical extension
The Cloudflare SSL tools at https://github.com/cloudflare/cfssl might help. Here's what it shows for one of the example Snake Oil certs:
-
Private CA management
I've used this in the past and it worked great. https://github.com/cloudflare/cfssl
- Linux Certificate Authority root stores have a too simple view of 'trust'
- Creating an internal Certificate Authority in 2022 that is accepted by modern web browsers.
-
How to create users in Kubernetes
The first step is to create the source key that represents our user. This key is created using a tool like openssl but another popular tool to use is cfssl, created by Cloudflare. Some folks think cfssl is easier to use, and it definitely looks easier to script. But for this example we will use openssl. You can also choose to create the key using a number of different algorithms. For this example we will use ED25519.
-
[Legal notice] IoT Core will be discontinued on Aug. 16, 2023
TLS/SSL worked well with client certificates generated by the CFSSL API.
-
Feedback on a Self-signed SSL CA?
Not sure if relevant but we used tooling from CloudFlare in the past: https://github.com/cloudflare/cfssl
What are some alternatives?
acme.sh - A pure Unix shell script implementing ACME client protocol
OpenSSL - TLS/SSL and crypto library
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.
easy-rsa - easy-rsa - Simple shell based CA utility
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
LetsEncrypt-PRTG - Post request script to install an SSL certificate obtained with Certify the Web or win-acme in PRTG.
lego - Let's Encrypt/ACME client and library written in Go
synology-tls - Automatically Update Let's Encrypt Wildcard Certificates for Synology NAS
certificates - 🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
portainer-traefik-letsencrypt - This repository will help you install Portainer with Traefik and Let's Encrypt with much ease!