rgca
daemon
rgca | daemon | |
---|---|---|
6 | 2 | |
2 | 11 | |
- | - | |
0.0 | 8.3 | |
over 1 year ago | 3 months ago | |
Python | Go | |
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
daemon
-
Running one’s own root Certificate Authority in 2023
I made a web server / microservices thing that issues certs for clients from a CA root it automatically generates. Then internal reverse proxy connections use that cert so the whole path is TLD encrypted with full cert validation.
https://github.com/fsmv/daemon
- Show HN: A web server for using TLS with many back end servers
What are some alternatives?
hckrweb - Hcker News mobile web app
certificates - 🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
pashword - 🔒 Pashword - Never forget passwords ever again! Free and Open Source Hashed Password Generator
lego - Let's Encrypt/ACME client and library written in Go
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit
bettertls - BetterTLS: A Name Constraints test suite for HTTPS clients.
gitgrep - Lightning fast code searching made easy
easy-rsa - easy-rsa - Simple shell based CA utility
hackerer-news
MagLit - 🔥 MagLit - Privacy Respecting Encrypted Link Shortener with Password Protection and Torrent Magnet Links support
dehydrated - letsencrypt/acme client implemented as a shell-script – just add water