- Site menu:
- Latest Discussions
- Latest Newswire
- Archives
- Submit Story
- Story HOWTO
- Syndicate
- E-mail Alerts
Public concerned about security flaws in government open source code
|
|
|
Comments (2)
The complainants also seem to be conflating a number of issues here as well.
Just because the software is released under a permissive, open source license doesn't have any bearing on the amount of testing that it has undergone. I find the confusion in this regard mystifying.
Just because the software is released under a permissive, open source license doesn't have any bearing on the amount of testing that it has undergone. I find the confusion in this regard mystifying.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post
Apparently the author of the article doesn't know about these things:
https://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration
https://en.wikipedia.org/wiki/OpenSource_Maturity_Model
https://www.govcode.org/repos
****
It seems to me that there is a broad ranging misunderstanding of government and open source and how it all fits together.
The government can't just simply release all software code... there are national security risks to evaluate.
Some source code may be releasable to the taxpayer, but not releasable to the world. Some source code may not be releasable outside of government, for national security reasons. And some source code will be releasable to the entire world... there's a fine line between all these categories.