rgca
dehydrated
rgca | dehydrated | |
---|---|---|
6 | 36 | |
2 | 5,902 | |
- | 3.4% | |
0.0 | 2.3 | |
over 1 year ago | 2 months ago | |
Python | Shell | |
Creative Commons Zero v1.0 Universal | 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.
rgca
-
Running one’s own root Certificate Authority in 2023
Shameless plug, there's also https://github.com/linsomniac/rgca
I've been using it at work for the last year for our certs and it's been quite nice. It can do pre/post hooks as well, so it directly commits the updated CA serial files to our git repo.
-
Ask HN: Tools you have built for yourself?
I built a TLS certificate tool targeted towards my company usecase for internal certificates (developers, OpenVPN, internal certificates): https://github.com/linsomniac/rgca
It's big features are that the cert generation can entirely be controlled from the command line, config, or environment, or any combination of the above, and it has tooling for the situation where I have an existing cert but want to add or remove a name from it. It also has pre/post scripts so I can have it do things like add it to the Ansible repo, vault encrypt it, and commit it. Beats the 10+ year old script that didn't work with Subject Alt Names.
-
Do you guys use Python classes in your day-to-day devops code?
Over the last year I've written several CLIs in click and typed and settles on typer because there's a little less repetition. Typer let me do some really nice things in my certificate generation tool like chaining multiple config files, the environment, and the command line to create certs. https://github.com/linsomniac/rgca
-
Ask HN: What Are You Working On? (September 2022)
I've always found the OpenSSL tools painful for managing internal self-signed certificates. At work we make fairly heavy use of them, and are starting to make even heavier use. Our use is more than EasyRSA can provide. So I've been working on a new CA tool:
https://github.com/linsomniac/rgca
In a nod to OpenSSL config files, it can take almost all values: from the command line, from the environment, or from one or more config files. It also allows "pre" and "post" commands so you can run a script after generating the cert, for example for server certs I have a "post" script that will copy it into the appropriate location in the Ansible repo, encrypt the key file, and commit it all.
I still need to implement a "renew" which will take an existing cert, update the expiration date, but also allow adding/removing SANs, possibly other features. But I've been using it to generate all our certs recently and it's working great.
-
Feedback on a Self-signed SSL CA?
At work we use self-signed certificates for internal and developer use. I inherited some scripts that wrapped the openssl CLI but weren't supporting new uses like the prevalence of Subject Alternatives Names. So I reimagined it and have published what I have so far here: https://github.com/linsomniac/rgca With an appropriate config file, the typical use would be: rgca ca new example.com rgca cert new user1.example.com rgca cert new --san test.example.com --san test2.example.com user2.example.com Basically everything can be configured by settings in (possibly multiple) config files, environment variables, and CLI options. Expected use is that things like the subject values (country, state, locality, email) are set in the config file, so the CLI can be short. Instead of: rgca cert new --C US --ST Colorado --L Fort Collins [...] It should be compatible with existing CA setups with OpenSSL CLI tools, it writes the "serial" and "index.txt" files. Looking for feedback on the direction this is going in. Thanks!
-
If OpenSSL Were a GUI
It can also run pre and post scripts to, say update your serial/index in git, and deploy keys to the server, say you are rekeying every 30 days...
Interested in feedback.
https://github.com/linsomniac/rgca
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
What are some alternatives?
hckrweb - Hcker News mobile web app
acme.sh - A pure Unix shell script implementing ACME client protocol
pashword - 🔒 Pashword - Never forget passwords ever again! Free and Open Source Hashed Password Generator
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.
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
gitgrep - Lightning fast code searching made easy
lego - Let's Encrypt/ACME client and library written in Go
daemon - a personal web server, one line of config to add a reverse proxy
synology-tls - Automatically Update Let's Encrypt Wildcard Certificates for Synology NAS
hackerer-news
portainer-traefik-letsencrypt - This repository will help you install Portainer with Traefik and Let's Encrypt with much ease!