• 0 posts
  • 3 comments
Joined 3 years ago
Cake day: June 11th, 2023
  • I’ve never liked this approach - having to enroll certs on every machine always seemed tedious and it’s why I just “dealt with” having HTTPS errors internally for years.

    You only have to do it once per machine and I use NixOS a lot so its easy to just add to a module imported by every system. On other Linux systems it’s just putting the pem file somewhere in /etc/ and running a command to reload it. Android cell phones were pretty easy but I forget the exact details.

    Honest question, why not set up a reverse proxy that uses Let’s Encrypt?

    I have multiple of those for public services. Because I don’t want to expose every service to the internet for HTTP-01 and can’t use DNS-01 due to how my nameservers are set up, this makes sense. Other advantages are not needing to distribute DNS update keys to every single server for security reasons and having shorter domains.

  • Someone can still tamper with and put malicious software on the drive as the kernels and initrds in /boot are not encrypted and could be tampered with. You would need to use UEFI secure boot with UKIs and custom keys enrolled to partially prevent this.