rgca
certificates
rgca | certificates | |
---|---|---|
6 | 40 | |
2 | 6,168 | |
- | 1.3% | |
0.0 | 9.5 | |
over 1 year ago | 5 days ago | |
Python | Go | |
Creative Commons Zero v1.0 Universal | 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.
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
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?
hckrweb - Hcker News mobile web app
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
pashword - đź”’ Pashword - Never forget passwords ever again! Free and Open Source Hashed Password Generator
boulder - An ACME-based certificate authority, written in Go.
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit
omgwtfssl - SSL certificate generation for developers who don't TLS good
gitgrep - Lightning fast code searching made easy
daemon - a personal web server, one line of config to add a reverse proxy
easy-rsa - easy-rsa - Simple shell based CA utility
hackerer-news
traefik-certs-dumper - Dump ACME data from Traefik to certificates