105

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?

you are viewing a single comment's thread
view the rest of the comments
[-] possiblylinux127@lemmy.zip 33 points 2 months ago

Why?

Let's encrypt is free and secure. There is no good reason not to use it.

[-] teawrecks@sopuli.xyz 5 points 2 months ago

I think their question is, what do you mean by "secure"? Because as the saying goes for internet services: usually, if you're not paying, you're not the customer, you're the product.

[-] possiblylinux127@lemmy.zip 9 points 2 months ago* (last edited 2 months ago)

Let's Encrypt is a non profit largely started by the Electronic freedom foundation (eff) to bring https to the internet. Before it was very trivial to spy and modify web traffic but now that https is everywhere it is much harder to do if not impossible. They are also the ones who pushed for all major browsers to adopt https only. In all major browsers you should get a page warning you that a site uses http instead of https. It is a very bad idea to use http in 2024 as it allows anyone along the line to modify traffic and to see what pages you are viewing.

[-] theterrasque@infosec.pub 2 points 2 months ago

I still use http a lot for internal stuff running in my own network. There's no spying there.. I hope ... And ssl for local network only services is a total pita.

So I really hope browsers won't adapt https only

[-] possiblylinux127@lemmy.zip 1 points 2 months ago

I do to. However, that's the exception. I hope you aren't running http over the public internet as that's a massive security issue

[-] Laser@feddit.org 6 points 2 months ago* (last edited 2 months ago)

A lot of paid cert providers were not so great before LE put the spotlight on the issue; it was more of a scheme to extract money from operators who couldn't afford to not offer TLS / SSL. https://bugzilla.mozilla.org/show_bug.cgi?id=647959 was a famous post that made fun of / criticized the system before LE. This hurt security, and if not free, LE wouldn't have worked.

[-] EncryptKeeper@lemmy.world 4 points 2 months ago

Yeah but also even when you’re paying, you’re still the product.

this post was submitted on 12 Sep 2024
105 points (97.3% liked)

Selfhosted

40383 readers
352 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS