certificates VS letsdane

I've been doing this for a while with SmallStep CA: https://github.com/smallstep/certificates

It's a bit of a pain to load a cert onto every device (easier with stuff like Ansible if you have a bunch of linux devices), but manageable. And it lets me do proper trusted TLS for a lot of stuff that would otherwise be self-signed.

One thing I recommend is to add X509v3 Name Constraints extensions to your root CA if you go down this path. It prevents the CA from being abused to MITM you for other URLS (at least for browsers/clients that respect names constraints)

```

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/

The easiest way to do this is to use letsdane https://github.com/buffrr/letsdane

Easiest way would be to deploy LetsDane and then allow a user to set the DoH server for the LetsDane proxy to use: https://github.com/buffrr/letsdane

P.S. Does anyone know why "humbly/" isn't working with HTTPS either? It's the same error that I'm getting. According to https://github.com/buffrr/letsdane, 3b/, letsdane/, proofofconcept/ and humbly/ all have DANE enabled. "humbly" appears to be configured properly (DNSSEC, SSL cert w/ matching TLSA), but I get the same SSL error when trying to resolve with Fingertip. Anybody else??

To securely access an HNS domain using DANE, extra software is required (until we get DANE browser integration!): https://github.com/buffrr/letsdane

Yes but you need a HNS resolver, which can also resolve legacy DNS names. So I have hsd installed on a raspberry pi on my home network, and another running on a VPS -- I set all my devices to make DNS requests from those servers. Set once and forget: now I can visit all HNS names as well as every DNS website. There some caveats to this, and the biggest issue is SSL / TLS / https but we have a solution for that as well: https://github.com/buffrr/letsdane All web browsers work fine with HNS names, but until a major browser implements native DANE verification, the middleware proxy is required.