certificates VS certstrap

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.

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

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.

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.

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.

Just a little heads up https://smallstep.com/certificates/

Step-ca: Not web based, but the CLI is pretty user friendly: https://smallstep.com/certificates/

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.

So setup a CA (I find certstrap simplifies this), load the CA cert into Mosquitto (cafile). Then you can issue any number of certificates that will allow clients to connect (you don't need to touch the broker config when adding new clients).

git clone https://github.com/square/certstrap cd certstrap git checkout v1.3.0 docker build -t squareup/certstrap . alias certstrap='docker run -i --rm -v $PWD:/out squareup/certstrap'

I like certstrap for this sort of thing, personally. I used to bugger about with OpenSSL but that’s far too real ale these days.

There are many ways to do this but my favorite is Certstrap.

Sounds like the issue is with your certificate itself, perhaps look at something which helps with local certificates management like https://github.com/square/certstrap

If you want to create your own CA, Certstrap by Square is really handy and simple to setup. I use this to generate valid certs for all my internal services (NAS, ESXI, etc).

Because OpenSSL is quite complex to use, we'll use certstrap for generation of certificates, install certstrap from here.