Paid SSL vs Letsencrypt - eviltoast

I’m curious what the benefits are of paying for SSL certificates vs using a free provider such as letsencrypt.

What exactly are you trusting a cert provider with and what are the security implications? What attack vectors do you open yourself up to when trusting a certificate authority with your websites’ certificates?

In what way could it benefit security and/or privacy to utilize a paid service?

And finally, which paid SSL providers are considered trustworthy?

I know Digicert is a big player, but their prices are insane. Comodo seems like a good affordable option, but is it a trustworthy company?

  • 0x0@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    Oh, that… I think i’m using it but it seems.to expect a response from 80 when all I have there is a redirect to 443.

    I thought you meant an nginx plugin.

    • r00ty@kbin.life
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      I have auto redirect to 443. But --nginx works fine. I think it overrides stuff for whatever the specific url used is.

    • Shimitar@feddit.it
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Yes you need both 80 and 443 for certbot to work. Anyway having 80 to redirect to 443 is common and not a security risk.