105
Paid SSL vs Letsencrypt
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Sep 2024
105 points (97.3% liked)
Selfhosted
40134 readers
291 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Neither does Google Trust Services or DigiCert. They're all HTTP validation on Cloudflare and we have Fortune 100 companies served with LetsEncrypt certs.
I haven't seen an EV cert in years, browsers stopped caring ages ago. It's all been domain validated.
LetsEncrypt publicly logs which IP requested a certificate, that's a lot more than what regular CAs do.
I guess one more to the pile of why everyone hates Zscaler.
DigiCert recently was forced to invalidate something like 50,000 of their DNS-challenge based certs because of a bug in their system, and they gave companies like mine only 24 hours to renew them before invalidating the old ones…
hey I don’t make the trust rules. ZScaler is trash imo but hundreds of thousands of clients are ‘protected’ by their trust rules. People downvoting my post because it doesn’t wash with ‘the way things should be’ but in reality SSL certs are like email providers these days - if you aren’t paying with one of the big corps, a good portion of your web traffic (or email) might be blocked. Sad but true. There is a reason Let’s Encrypt and Cloudflare et al are heavily used by Crypto sites, and that is due to the anonymity they provide. If all you care about is encrypting traffic, use Let’s Encrypt. If you care at all about perception of trust, use paid SSL. simple.
these are subdomains of a verifiably certified root domain no doubt
Untrue. I work for a global enterprise company that transacts hundreds of millions of dollars via LE certs.
I believe you, but I also very much believe that there are security vendors out there demonizing LE and free stuff in general. The more expensive equals better more serious thinking is unfortunately still quite present, especially in big corps. Big corps also seem to like the concept of having to prove yourself with a high price of entry, they just can't believe a tiny company could possibly have a better product.
That doesn't make it any less ridiculous, but I believe it. I've definitely heard my share of "we must use $sketchyVendor because $dubiousReason". I've had to install ClamAV on readonly diskless VMs at work because otherwise customers refuse to sign because "we have no security systems". Everything has to be TLS encrypted, even if it goes to localhost. Box checkers vs common sense.
The B2B use case isn’t quite what I was referring to with respect to the type of trust required for first time or consumer transactions such as ecommerce. That said, this enterprise doesn’t sound federally regulated at all because if it were, it wouldn’t be using Let’s Encrypt.