I want my self hosted things to use https. For example, I have Jellyfin installed via docker, and I want it to use https instead of http.

I don’t care about necessarily doing this the “right” way, as I won’t be making Jellyfin or any other service public, and will only be using it on my local network.

What is the easiest way to do this? Assume everything I host is in docker. Also a link to a tutorial would be great.

Thanks!

  • @TCB13@lemmy.worldEnglish
    14•5 months ago

    Yes, LetsEncrypt with DNS-01 challenge is the easiest way to go. Be it a single wildcard for all hosts or not.

    Running a CA is cool however, just be aware of the risks involved with running your own CA.

    You’re adding a root certificate to your systems that will effectively accept any certificate issued with your CA’s key. If your PK gets stolen somehow and you don’t notice it, someone might be issuing certificates that are valid for those machines. Also real CA’s also have ways to revoke certificates that are checked by browsers (OCSP and CRLs), they may employ other techniques such as cross signing and chains of trust. All those make it so a compromised certificate is revoked and not trusted by anyone after the fact.

    • @Findmysec@infosec.pubEnglish
      4•5 months ago

      Running a CA is cool however, just be aware of the risks involved with running your own CA.

      All they say that if the private key is stolen then you’re screwed. Think about it, if an attacker can:

      1. Get into your network.
      2. Presumably bypass key-based ssh/container runtime protections
      3. Access pod/VM which is running the CA
      4. Bypass default MAC settings (Apparmor on debian, SELinux on RHEL)
      5. Steal private key without you knowing from your logs

      You have a much bigger problem my friend

      • @TCB13@lemmy.worldEnglish
        1•5 months ago

        While I agree with you, an attacker may not need to go to such lengths in order to get the PK. The admin might misplace it or have a backup somewhere in plain text. People aren’t also prone to look to logs and it might be too late when they actually noticed that the CA was compromised.

        Managing an entire CA safely and deploying certificates > complex; Getting let’s encrypt certificates using DNS challenges > easy;