FSF statement on the Bash “shellshock” vulnerability
fsf.org
fsf.org
This is not the time. The statement is incredibly tone-deaf.
IMHO, it's always the time to advocate libre software.
One thing the Open Source guys just don't frickin' get is that only a very few people have the time or the energy to fully understand everything that goes into their software. Sure, all the source is available, but if I had time to look at it and digest it, I wouldn't have time to do my real, paying job, nor would anyone else.
Which is why we have commercial software. Open or closed source doesn't matter if you don't have time or the background to deal with it. Open Source comes from an academic culture where results don't have to produce economic benefits and people have (or had) plenty of time to bang on this stuff until it works (for a given value of works, that they made up).
I won't say I'm not grateful for what the Open Source guys and gals have done, but damn, people. Can't you at least recognize that the world more closely resembles Hell than Utopia?
Or are resources dedicated to pushing out product and moving on to the next?
Better a hell I know and can see than one hidden. At least there is a chance of seeing the demons before they strike and exercising them without relying on a priesthood, to stretch the metaphor.
> Do you actually have the ability to understand exactly what the patch is doing and all of the potential future ramifications?
Do you even get that _chance_ with proprietary software? (Note: I didn't say commercial; you can have commercial, open-source software.)
> Open or closed source doesn't matter if you don't have time or the background to deal with it.
Yes, yes it does. Mostly because I can pay someone else who does or gain the background myself. This especially true for custom equipment with custom drivers and software. Once the company goes under there isn't a chance at all of getting anything fixed.
> Can't you at least recognize that the world more closely resembles Hell than Utopia?
If Hell means having access to the shear abundance of software I do, then yes.
Take QGis as a singular example. I couldn't pay for Arc; I just don't have those funds. QGIS gives me all the same features for free. While I can't contribute much in the way of code, I do try to help up doing support, helping with docs, writing tutorials, and evangelizing. Ditto for PostGIS (and by extention PostgreSQL) and Grass
If free software didn't exist, a lot of the types of work I do just wouldn't be possible.
Their tone seems to be more geared towards "look at how easy it is for anyone to get the fix", which isn't really all that great: most people don't have a toolchain in place that allows them to deploy new versions of bash from source in any automated fashion, so at the end of the day everybody just waits on a "vendor" fix anyway.
OpenBSD has shown that small organizations can audit and maintain code with a focus on security and correctness. Why hasn't the FSF, with its greater level of resources, managed to do the same?
It's simply a matter of different goals. The OpenBSD project has security as a primary goal. They often throw out features, flexibility or portability on the grounds of preserving security.
GNU instead prioritizes those features, flexibility and portability, occasionally losing out on security.
Security is hard and involves a lot of sacrifice with little evidence of success aside from "oh look, we haven't had any vulnerabilities for a while".
I believe a better message would be that "Even when the vendor who supplied you bash isn't helping you can fix it." but that will depend on what the Apple experience is with bash, which is currently not so hot.
Sadly but not surprisingly, when your labor pool consists of volunteers, few of them sign up for this thankless task. I don't know how to solve this problem.
I never liked "given enough eyeballs, all bugs are shallow". In the worst case, it devolves into "someone else will do it".
There's unwieldy projects like OpenSSL that probably have far too critical of a task for few too few developers, but generally, most open source products are developed by paid developers and are doing just fine