• lambalicious@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    45
    ·
    2 days ago

    I really like their take on, essentially, “don’t drop everything just because there’s yet another CVE”. There being vulnerabilities is the “normal” under our current development of technology. The core is making it a non-tiring normal. When I hear there’s a new CVE I give a quick read to the minutes. If it can’t pass the test of working beyond “requires a user already logged running a specific program from /tmp instead of $PATH, with the computer facing left and the brightness of the monitor set to 72.3% o a Tuesday”, then I leave it for the nightly cronjob to upgrade the container, and even if that somehow does not work then I would be checking tomorrow anyway. The higher-ups are not assigning a fair paid overtime for this, or even any at all, so.

    • nibbler@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      6
      ·
      21 hours ago

      Thing is, like with the recent php, you don’t have the info you claim to base your decision on. Currently it’s ‘any nginx with http2’. Bet you, next week we know about the ‘computer facing left’ detail. But today we have to assume the worst.

      • lambalicious@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 hours ago

        I get that, and I think it maps well. If no solid info is delivered on what the vulnerability is, or how to manually patch, then there is no gain all pain to me paying it more mind. It’s much like asteroid watch: if someone yells “there’s an asteroid coming!” and I ask where, when, what size, and nothing of that has useful actionable info, things are not different than if they instead had yelled “good morning!”.

        I have to assume that the security measures currently in place will suffice for the platforms standing as-is, among other things because higher-ups have not approved for stricter measures or for technical debt solving or for paid overtime, etc.

        Which does get me wondering - we have a mechanism to secure once the correction comes out: we pull from upstream. But is there any sort of similar mechanism (esp. for Docker / Podman) to distribute, pull and apply declared mitigations in the meantime? Such as changes to httpd.conf, etc.

        EDIT: yes I know this is about enterprise or at least hired stuff, whereas this particular community is self-hosted. But IMO, that difference only makes things overall worse. In selfhosting I’m definitively not paid to over-care, nor to sacrifice my mental health. I already have enough with the world as-is. Get me UBI, and then we can start talking about how it feels to sit before a docker pull screen all day while sipping on a margerita.