To view parent comment, click here.
To read all comments associated with this story, please click here.
And if it were a commercial product they would have been royally screwed. Ring up the company then pray that the actual problem is fixed rather than simply be told, "here is a work around, the problem won't be solved until months later (or the next release)".
You either have flexibility or perceived 'teh cheapness'. The fact is, if the DHS refuses to work with the community of security issues, how is it the problem of open source that they, the DHS, spent 1500 or so man hours on something that could have been avoided? why not setup security audit groups consisting of DHS IT personal and vendors to improve quality?
The whole point of open source is community; the fact that IT is a cost centre within a company, working together with other companies and organisations should not be an issue - you make no money from software, the fact that work with others on fixing common issues isn't going to lead to loss of competitiveness - so there are no excuses as to why it isn't possible.
To me it seems that businesses still live in an era where they're an island - where they can't seem to get their head around the idea of working with companies on common issues which all face, whilst at the same time still competing with each other in the product sphere.






Member since:
2005-07-06
I think the news is not that there are actual bugs in OSS but that the department of Homeland Security has spent 1562 man(person) hours fixing them.