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.
Yeah it’s one of the reasons why I madee the later edit comparing enterprise vs selfhosting. In enterprise, real damage to the shareholders is made if you disable your service. Won’t you please think of the shareholders? Whereas in selfhosting… well, the damage is lots lesser, although it does invariably include the potential that your users (family etc) willl turn tail towards the enterprise option.
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 pullscreen all day while sipping on a margerita.It’s not like an astroid. You can disable your service. And there is acreason for lack of detail.
Yeah it’s one of the reasons why I madee the later edit comparing enterprise vs selfhosting. In enterprise, real damage to the shareholders is made if you disable your service. Won’t you please think of the shareholders? Whereas in selfhosting… well, the damage is lots lesser, although it does invariably include the potential that your users (family etc) willl turn tail towards the enterprise option.