Comment on Do you run a private CA? Could you tell me about your certificate setup if you do?

• TCB13@lemmy.world ⁨9⁩ ⁨months⁩ ago

  Why are you pushing for your own CA in the first place?

  source

  • MigratingtoLemmy@lemmy.world ⁨9⁩ ⁨months⁩ ago

    I would not like to use a public domain for my internal network. By extension, I do not want any public CA to know the domains and subdomains I use in my lab and home network

    source

    • TCB13@lemmy.world ⁨9⁩ ⁨months⁩ ago

      Okay that’s fair but if your only concern is about “I do not want any public CA to know the domains and subdomains I use” you get around that.

      Let’s Encrypt now allows for wildcard so you can probably do something like *.network.example.org and have an SSL certificate that will cover any subdomain under network.example.org (eg. host1.network.example.org). Or even better, get a wildcard like *.example.org and you’ll be done for everything.

      I’m just suggesting this alternative because it would make your life way easier and potentially more secure without actually revealing internal subdomains to the CA.

      Another option is to just issue certificates without a CA and accept them one at the time on each device. This won’t expose you to a possibly stolen CA PK and you’ll get notified if previously the accepted certificate of some host changes.

      openssl req -x509 -nodes -newkey rsa:2048 \
      -subj "/CN=$DOMAIN_BASE/O=$ORG_NAME/OU=$ORG_UNIT_NAME/C=$COUNTRY" \
      -keyout $DOMAIN_BASE.key -out $DOMAIN_BASE.crt -days $OPT_days "${ALT_NAMES[@]}"
      

      source

      • MigratingtoLemmy@lemmy.world ⁨9⁩ ⁨months⁩ ago

        My apologies, I didn’t word my concerns properly in the moment. I would like to run a private CA simply because I do not want to use a public domain for my internal network. It makes me deeply uncomfortable to use a public domain and get public certificates for something inherently so private (it’s more philosophical than technical, although I suppose that’s where a lot of opinionated technical decisions come from anyway). Your solution is elegant and simple, but I really do want to do it completely internally, and move towards zero trust security practices as I do. Basically, I want to start training myself on the security side of SRE in my lab, running services which matter to me and working like the more paranoid SRE teams in corporations work…I know this sounds like fantasy, and my needs might change going forward, but I’m also hoping to learn a lot from this and hopefully make this as robust as I can. Having a good security posture makes me feel warm inside :)

        source

        • -> View More Comments