Re:Freenginx: Core Nginx developer announces fork
by gav on Thursday February 15, 2024 @03:19PM
(#39388170)
Recently I had to support a client who had a "no CVEs in a production deploy, ever" policy.
The stack included Linux, Java, Chromium, and MySQL. It took multiple person-years of playing whack-a-mole with dependencies to get it into production because we'd have to have conversations like:
Client: there's a CVE in the this module
Us: that's not exploitable because it's behind a configuration option that we haven't enabled
Client: somebody could turn it on
Us: even if they somehow did and nobody noticed, they would have to stand up a server inside your VPC and connect to that
Client: well what if they did that?
Us: then they'd already have root and you are hosed
Client: but the CVE
Us:
So I definitely appreciate any vendor that tries to minimize CVEs.
Re:Freenginx: Core Nginx developer announces fork
by MZMegaZone on Thursday February 15, 2024 @05:12PM
(#39389866)
That's just a braindead policy.
Really, really dumb. Not at all good security, just checking boxes.
Re:Freenginx: Core Nginx developer announces fork
by gwd on Thursday February 15, 2024 @07:56PM
(#39391644)
I mean, yeah, but if that's the way big bureaucratic organizations get sometimes. Bigger means more likely to have a brain-dead policy like this, but also more money... so, do you give up the money, or do you accommodate their policy while trying to minimize the cost?
Re:Freenginx: Core Nginx developer announces fork
by MZMegaZone on Friday February 16, 2024 @01:34AM
(#39393898)
Oh, I'll cash their check. I'll tell them, in professional terms, why they should change their policy, but I'll still cash the check.
On the other hand, since the definition of "supported" is specifically designed to help downstreams, if it were known that some bit of code was widely used in production, we'd be open to declaring it "security supported", regardless of whether we thought it was "finished" or not.