• 1 Post
  • 36 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle


  • I actually agree. For the majority of sites and/or use cases, it probably is sufficient.

    Explaining properly why LE is generally problematic, takes considerable depth of information, that I’m just not able to relay easily right now. But consider this:

    LE is mostly a convenience. They save an operator $1 per month per certificate. For everyone with hosting costs beyond $1000, this is laughable savings. People who take TLS seriously often have more demands than “padlock in the browser UI”. If a free service decides they no longer want to use OCSP, that’s an annoying disruption that was entirely not worth the $1 https://www.abetterinternet.org/post/replacing-ocsp-with-crls/

    LE has no SLA. You have no guarantee to be able to ever renew your certificate again. A risk not anyone should take.

    Who is paying for LE? If you’re not paying, how can you rely on the service to exist tomorrow?

    It’s not too long ago that people said “only some sites need HTTPS, HTTP is fine for most”. It never was, and people should not build anything relevant on “free” security today either.


  • gencha@lemm.eetoSelfhosted@lemmy.worldPaid SSL vs Letsencrypt
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    16
    ·
    19 days ago

    People who have actually relevant use cases with the need for a reliable partner would never use LE. It’s a gimmick for hobbyists and people who suck at their job.

    If you have never revoked a certificate, you don’t really know what you’re doing. If you have never run into rate-limiting issues with LE that block a rollout, you don’t know what you’re doing.

    LE works until it doesn’t, and then it’s like every other free service on the internet: no guarantees If your setup relies on the goodwill of a single entity handing out shit for free, it’s not a robust setup. If you rely on that entity to keep an OCSP responder alive for free so all your consumers can verify the validity of your certificate, that’s not great. And people do this to save their company $1 a month for the real thing? Even running the shitty certbot in compute has a larger cost. People are so blindly in love with this “free” garbage. The fanboys will never die off





  • gencha@lemm.eetoich_iel@feddit.orgich🔪🧴✂️iel
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    1 month ago

    Brauche mehr Details.

    Ich schraube den Deckel ab und halte ihn mit dieser Hand fest. Die andere Hand führt die Flasche zum Mund und ich trinke. Dann setze ich die Flasche ab und schraube den Deckel wieder drauf.

    Gibt es hier alternative Ansätze die ich noch nicht kenne, oder kommt es bei diesem Prozess zum Deckelverlust?


  • gencha@lemm.eetoich_iel@feddit.orgich_iel
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    1 month ago

    Habe mir das neulich erst nochmal angeschaut. Meine Welt ist etwas blasser geworden als ich realisierte, dass es sich um eine Produktion aus Frankreich mit Synchro handelt. Für mich war das ur-deutsch bis zu diesem Tag





  • Bro, I’m an AWS Cloud Solution Architect and I seriously don’t know what you’re talking about. And, no, when I waste time on Lemmy, then there is literally nothing better to do.

    AWS made S3. People built software to integrate S3 as a storage backend. Other people didn’t want to do AWS, and built single-node imitations of the S3 service. Now you use those services and think that is S3, while it is only a crude replica of what S3 really is. At this point the S3 API is redundant and you could just as well store your assets close to your application. You have no real, global S3 delivery service anyway. What’s the point?

    Most people misuse AWS S3. Using stuff like minio is even more misguided.