MagLit VS rgca

On the privacy front, we're never going to compromise the user data, never going to sell it, never going to share it with anybody else. We'll be making writedown self-hostable as well.

On the security front, we're using firebase firestore as the database. So at rest, it's well encrypted.

We're thinking of introducing some sort of encryption via passwords (kinda how I already am doing it on https://maglit.me). E2EE would be quite difficult and would affect the usability.

maglit.me, can use custom links and is privacy respecting

jesus christ use https://maglit.me/ so your link will not be so fucking fat.

There are many services that offer such a functionality. Just search for "password protected link shortener". One example would be https://maglit.me/ by u/NayamAmarshe (I haven't tried it, I only read this post). However if you care for privacy (kind of the point of the whole post) and you have a web server you might want to selfhost the service (has a lot of other advantages as well, link all the easy to remember keywords are still available), which gives you even more options: like again MagLit or YOURLS with the Password Protection Plugin. (disclaimer: I am using a self hosted YOURLS instance myself, but have not used this plugin yet).

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.

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.

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

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.

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!

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