US Government Studies Open Source Quality
anadgouda writes "US Department of Homeland Security has released a report on open source quality in an effort to study the security of open source. 31 popular open source packages were studied as part of this effort. From the article: 'Coverity's report, Stacking up the LAMP stack: a study of open source quality, was produced as part of a $1.24m, three-year DHS Science and Technology Directorate effort to evaluate and improve the security of open source.'"
So, does anyone have the numbers as to how much of the government uses open source? Is it mostly an applications thing (OpenOffice) right now, or are Linux and the BSDs much in use?
Religion for nerds. Stuff that really matters
This study would be extremely valuable if they had submitted BZilla bugs for each and every defect they encountered. It's hard to tell from the article whether they did or not. One thing that I have learned from running ~arch in Gentoo is that if you don't submit bugs, things aren't going to get fixed.
BBH
I feel very conflicted by this report. On the one hand, I'm happy to see a report that favors open source. On the other hand, in the wake of the Katrina political fallout, it's difficult to say whether this report helps or hurts. The last thing LAMP needs right now is to get caught up in Brown/Chertoff/GWB affair. The only thing worse would be to have the UAE issue a similar report. :-)
If you don't want crime to pay, let the government run it.
Open-source software is a serious threat to this country. These terrorist schemes, or "development projects," as the terrorists refer to them, are designed to rot away the core values of our great nation that we hold so dearly. One in particular, known as "Linux," is especially suspect. It is "developed" by terrorists worldwide, many of which are communists, and many of which do not even support our great commander in chief! It is apalling! How can we trust the security of our nation to these rogue "developers?" Surely they may have hidden devices in their programs, hidden in elaborate matrices of computer programming, that when activated by the terrorists, will disable the software and send them all of our secret data! It can only be expected.
The terrorists are cunning, they are secretive, and they will destroy us if they have their way. This world-wide "open source" terrorist movement must be deconstructed and eliminated. There is no other way to protect our Great Nation! We say to you, as the purveyors of truth and all that is good, avoid this "open source" and its proponents like the plague! They wish to destroy everything we hold dear. You, my good American, are the first line of defense. Report users of "open source" to the authorities. Gather any information on them that you can. You may even consider running their dastardly "software packages" in your own free time, so that you may come to know your enemy - for knowledge is the greatest tool that we have in this fight.
Stand proud, my fellow Americans, and beware this new emerging beast. It will surely be the end of us all if we do not take action now.
Quoted from President George W. Bush's State of the Nation Address, January 2007.
hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
Trolltard,
Department of Homeland Security is not the Federal Emergency Management Agency.
One would expect that being about open-source and all, and with a purpose of helping open-source developers improve the quality of their code, they would publish the report on a governement website somewhere. C'mon, where's the link?
the report have a better coverage on this page: http://www.eweek.com/article2/0,1895,1909946,00.as p
/. or not
from this TFA:
"Anti-virus vendor Symantec Corp. is providing guidance as to where security gaps might be in certain open-source projects."
PS:i am not sure if it has been published on
everyone downmodding this post will be prosecuted for reading my post without first buying a license!!!
I've always thought it VERY odd to think about "Open Source" as a thing.
t ware_pricing.html really puts into better perspective.
Basically, it says ALL software can be deconstructed to being about the service (at least so long as the technology curve continues, in practice, to limit its lifespan).
It'd be like saying: We studied the quality of software compiled with the Watcom 10.0 C++ compiler. "Open source" cuts across so many levels of skill and projects. You can pretty find projects that support (or destroy) whatever thesis you'd like to put forward
Even more, somebody pays for the development of the software, one way or another.
This artlice (from ONLamp) http://www.onlamp.com/pub/a/onlamp/2005/07/21/sof
--
graphicallyspeaking
graphically speaking
Could it be that something good came from the US Department of Homeland Security?
I don't think there is any question. Open and closed source will both be around for the forseeable future.
To what extent is a different matter...
As long as there are people (and this would be the vast majority today) who care less about what license their software has than how well it does the job, then there will always be a market for closed-source software. On the condition that it is better than the available OSS solutions.
I think OSS will play this kind of role in the future, providing everybody with a basic set of software, and upping the ante for the quality of commercial software.
Commercial software on the other hand, will increasingly be for those who need and are willing to pay for the improved quality it offers (and will per definition be forced to offer in order to exist).
I'm glad to see that one of the first Digg Trolls chose to reply to my post. Have a good one buddy!
hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
Damn you didn't even read the f**kin summary!
"...has effectively given the Linux, Apache, MySQL and Perl/PHP/Python (LAMP) stack a healthy rating. LAMP "showed significantly better software quality" above the report's baseline with an average of .32 defects per 1,000 lines of code, according to Coverity. The average for open source projects analyzed is .42 per 1,000 lines."
What would be interesting to know is how they determined a baseline of .32 defects per 1000 lines of code as their baseline, and how so called commerical products, like Oracle, Windows, MSSQL, etc. fared against the same baseline.
thats really the question isn't it? is Open Source more or less secure than any of the closed systems?
--My signature is six words long.--
The parent is wasting valuable time on Slashdot that should be spent finalizing his Independent Study project for the College of Wooster. He has precious little time left.
...New Zealand's recent analysis of open source, which focuses on legal issues.
CAD is a good example. I have heard a lot of good things about a new open source CAD program but what if you have a lot of vendors that use Solidworks or Autodesk?
Office is another good example. Many local and state governments have tried Applix or Star Office (now OpenOffice) for a few years. The day that they got rid of it and went to Office 2003 the county workers were more productive than ever. They had a terrible time with sending files to and getting files in Office format. I tried to convince them that it would improve and that they shouldn't sign away their life, but they needed something that would just work. For them, Windows XP and Office 2003 just worked.
If you look at a lot of the government studies of who uses and gets the most benefit out of open source it tends to fall into two categories:
- REALLY BIG TECH COMPANIES. They have their own support and development staff and can contribute back to open source projects.
- Really tiny startups with a good techie or two. They are not big enough for the big vendors to care about. So the support they get for much of the open source tools is as good, or better than, what they get from big closed source vendors.
In the middle you have a lot of medium companies that really don't want to manage software developers or handle support in house. I am all for open source but their are a lot of issues yet to be solved.- Education. I can not take a course on Linux at my local Community College. I can get my MSCE or Cisco cert there.
- Support. I can make Linux work for me and my company but not every company can. Where is the Linux Geek Squad? Yea all those scan-disk, defrag, run adaware and scan for virus "techies" give me the creeps but they seem to fill a need. Where can the mythical grandmother go to get a DVD installed in her Linux box or find out how to fix Thunderbird if the mail folder blows up? I will not even go into the poor state of some documentation for open source programs.
- Teaching. If you are going to send people out in to the real world as system administrators and/or programmers, they will have a better chance to find a job if they know Windows and Linux. Heck, they should know as many different systems like Z/OS and OS/400!
In conclusion, open source security depends on people admitting that bugs exist. If they act all high-and-mighty, nothing happens and it's just as bad as whatever software product is out there nowadays that people just love to hate.is good for the gander?
I wonder what "bugs that can corrupt a machine's memory space, memory leaks, buffer overruns and crashes" have been uncovered by looking at the source code of closed source softw... oh. wait. no source. heh.
This might well mean that open source software will, at some point in the future, be considered more secure and well-written than comparable commercial closed source software even by government or PHBs.
You have to wonder about the difference in "errors per thousand lines of codes" metric though. Does one project use
int a;
a = 5;
and the other
int a=5;
?
SCO employee? Check out the bounty
While not used on every desktop, I know of a lot of F/OSS being used everyday in the military. It would be stupid to not use it. Why would companies like Redhat and Novell spend money on getting their software certified to run on classified systems if it wasn't going to get used? While we may be selling out to Microsoft a lot, there are times when those of us who know better manage to convince the decision makers of the right tool for the job. In some cases, it's a MS product, in others, it's something else.
Uh, FEMA now falls under the unbrella of DHS. DHS was ultimately in charge of FEMA during Katrine. So basically, you're wrong.
From the article, which I'm SURE you read:
Coverity evaluated 15m lines of open source code with Stamford University's Computer Science Department. The report has identified bugs that can corrupt a machine's memory space, memory leaks, buffer overruns and crashes. Coverity said it would now engage with open source developers to improve code, and identify potential reasons for why some projects have more bugs than others.
Yes, the folks who ran the tests plan to submit their findings to the developers to help squash bugs.
Bad with logic _and spelling? What a winner.
An interesting study was done by the U.S. Military (the Airforce, I believe) concerning Open Source and it's place in the department of defense, though it is written in such a way to be useful to non-military personnel and applications. It is a similar, yet IMHO, a more interesting read than the parent.
The report can be found as a PDF at http://www.stsc.hill.af.mil/crosstalk/2005/01/0501 Tuma.pdf
There are more things in heaven and earth, Horatio, Than are dreamt of in your philosophy.
Does anyone have any factual data on what is "normal" (accepting all the problems of counting lines and bugs in the first place). I've seen estimates range from 2 to a 100 per 1000 lines.
Next time give that money back to us and write "USE OPENBSD" on your report. Better yet, just give them the money, and they'll actually do security stuff with it.
I'm not sure what this report is good for. The real battle is on three fronts : SCO vs. IBM, Microsoft vs. EU, and real change at the USPTO.
SCO vs. IBM. A cloud hanging over Linux. It really has to be resolved to clear the name of open source. So far so good, but it ain't over til it's over. Who is to say the Judge won't predudice herself at the last minute, getting her ruling thrown out? It's happened before, right?
Microsoft vs. EU. Looking back at the MS case in the USA...please, what kind of Judge breaks up a company, then goes on nationwide TV spewing a bunch of predudicial remarks against the defendant? He knew exactly what he was doing...giving MS another get out of jail free charge. Judgment set aside within weeks. Hopefully the EU will do a better job at enforcing America's laws.
USPTO: Without huge changes in the way software patents are dealt with, open source will die. Closed source is the only way to (somewhat) hide patent infrigement. How many officials can MS, Apple, Oracle, Sony woo? Answer : all of them.
What does the US government really think of open source? Look around you, they use it sparingly and grudingly.
If you're in the military security business, you know open source is officially categorized as "a key to operational predictability"--that is, your opponent can form strategies based on knowedge of open source software released or used by government agencies. I don't really agree with this, since knowing which closed source applications the government creates or uses can provide the same damn thing, especially to a determined adversary, with rooms full of qualified people hacking on the binaries!
Upon reading the PDF it struck me that if an organisation like the military wanted to use OSS in a more secure fashion, then the use of closed locked down binaries of the code like a default Linux secure network setup is the best option. The problems arise when the individual nodes can be modified willy nilly by malicious code. If you do not include a compiler on the nodes and make sure that binaries cannot be installed by users then you have a blueprint for bullit proof security. Given that the code that is originally compiled into the secure binaries is all visable, it would seem dangerous for the military to use closed source binaries like windows software and remote access sys-admin.
Reminds me of when as a noob, I reported an error in a man page to a project mailing list, hoping somebody close to the project might pick it up and fix it. Nah, the response was: OK, write yourself a new man page.
That attitude still pervades most OSS projects. The result is open source is regarded as by geeks for geeks, and IMHO this, more than any perceived security risks, will keep it off the desktop for a long time yet. Sure, I see quite a few specialist applications coming thru now packaged for MacOS-X. Here's an example (names obscured to protect the ignorant): a multimedia application, gui built on GTK, equal to commercial products of several hundred dollars, well worthy of the suggested paypal donation. But it requires access to the Hardware Abstraction Layer, which is provided by a different oss project, whose raw binaries will do what's needed from the command line, but no gui interface yet, unless you build it, in Qt.
Security problems in OSS are multiplied by forking, and geekishness for its own sake.
Three years, $1.24 Million, and what do we got .....
...
.32 defects per 1,000 lines of code, according to Coverity. The average for open source projects analyzed is .42 per 1,000 lines."
:)
The envelope please
"LAMP "showed significantly better software quality" above the report's baseline with an average of
Wow, LAMP is a pretty damn high quality stack after all....gee thanks Captain Obvious, we didn't really need those tax dollars for anything anyways.
I'm a contractor at DHS and have been trying to get them to use Linux in many of the systems we work on. I've given them the whole spiel about licensing, lower cost, dependability, etc of OSS solutions vs. the proprietary software. I'm hoping their own report will help convince programs within DHS to look to OSS instead of watching most of our IT budget go to software licensing.
if there is one group of people i trust to be able to accurately identify a quality product, it's the government.
go get it
Get a clue. Do you really think OSS is free? I've been a programmer long enough to know that many OSS programmers do a lot of their work while on someone else's nickle. Meaning, myself and others, often spend an hour or more a day working on coding or reviewing OSS while we're at our day job. My boss never knows, to him software is software. Doing some math, averaging only 1.5 hours a day on OSS x 250 work days/year gives 375 hours (roughly 10 weeks) per year the bossman is getting screwed out of work for his company. At $20/hour (not counting cost of benefits), that's $7,500/year. And that's just one person who isn't totally obsessed with OSS! Don't try to fool people, OSS is not "free", but it is crtical. Sort of like everyone doing their part to bring along this technology. Besides, working on OSS makes me a better programmer.
And I wonder how many more millions they can now save by using OSS, now that they know they can be more confident in its quality? Have you ever heard of the word "investment"?
Hmmmmm, wonder what Vista would look like under that scrutiny?...
Hmmmmmm.... Hey, I have a thought: if Microsoft does as it says and allows the Gov't to view it's code (without releasing it), should not this standard of examination be applied to Microsoft's software too so that we could have a better idea of just what level of quality we can expect from the private sector?
*** Don't be dull.***
If I remember correctly Coverity has been discussed on slashdot previously and they used the same diseased statistical thinking back then, too.
I18N == Intergalacticization
It's not a troll if a mod has a political bias that conflicts with the post. If you can disprove something factual in the post, then mod it troll. But don't just mod things down for political persuasion.
I'm involved in one of the F/OSS projects that Coverity analyzed; and yes, they were co-operative with the dev team in sharing their insights.
Well, at least it can be seen that there is overwhelming bias at slashdot. Not that I care, since I still read the news here.
If any MS (or should I say M$) product were to have been put in an article like that, the mobs would have screamed for Gates's head. However, since it is the all-powerful-silver-bullet-snake-oil open source, all I see are excuse makers and doubters. If anyone is to even take themselves seriously, they must be at least OPEN to the idea that something they believe in is not perfect, and possible quite flawed.
Its one thing to sit in an ivory tower, or garage, and pontificate on the utopian ideals of open source and free love without concern of ramification. It is a completely different thing to be tasked with the welfare of a nation and its people and just HOPE that the software is safe and will work as promised. I can appreciate the Linux/OpenSource/FreeLove ideals of slashdot and its readership, but there is a point when a person has to put personal bias asside and consider that there are greater things at risk than personl pride and being 1337.
Pluralitas non est ponenda sine neccesitate
Why no mention of SE-Linux?
One agency study.
1.5 million dollars spent.
How much did the NSA spend developing SE-Linux?
Must have cost more than 1.5 million. And that is now at the core of Linux.
Yes many in the US Government are aware that Open Source software rocks.
Impeach the Liar
Democrats prefer static modeling because then they can argue against tax cuts. Republicans favor dynamic modeling to support a "trickle down" effect.
.... [M]easures of macroeconomic feedback effects are very sensitive to assumptions that are subjective... Given the degree of uncertainty inherent in current methods of macroeconomic forecasting, true dynamic scoring would not allow the consistent and comparative cost estimates"
From the link you provide:
"[I]instituting a formal policy for the use of dynamic scoring would require planning or estimating around future fiscal policy, taxpayers' future behavior, and future business cycles well beyond the window of time for which they can reliably be predicted
"CBO and JCT do currently provide estimates to illustrate potential effects on the economy of significant tax proposals, at the request of Members of Congress, but such estimates are not official and only offered as supplemental information. Even opponents of dynamic scoring have encouraged this practice to continue in the same sort of advisory, rather qualitative (and not quantitative) manner because, as Kobes and Rohaly explain, they 'show how sensitive a proposal would be to various changes in these [macroeconomic] assumptions. However, producing an estimate in the form of a single revenue or cost number would be misleading.'"
Upshot:
1. The CBO uses static scoring for official estimates, and does so only for non-political reasons.
2. Democrats perfer static scoring for official estimates, which sounds like a better method, but no doubt they do so only for political reasons.
3. Republicans prefer dynamic scoring for official estimates, which sounds like an inferior method, and no doubt they do so for political reaons.
So yes, there is a controversy, and the controversy is politically-motivated.
But no, the CBO's decision in this matter is motivated only by sound accounting principles without regard for political ramifications.
There are BSCs that run linux (rh mostly) and the like in wide use.
It's funny how the US security is almost as poor as Windows security!
Now if we could only deny those terrorists root access...
"The whole point of my post is that it's easy for good data to get lost in political debate."
Then why did you bring up unrelated, useless, politically motivated points?
No, it's obvious you were karma whoring, at tleast be a man and own up when you get caught.
And save your protests, no one believes you.
How pathetic are you that you follow me from topic to topic and waste all your mod points at once modding me down?
This definitely adds weight to the "more eyes make bugs shallow" principle of open source.
How many closed-source applications would get this sort of helping hand?
I know that there is a Stamford University, and everyone always jokes that it's for people who want to pretend they went to Stanford, but, this just makes things really confusing. The Register article says Coverity used a verifier from Stamford University, when really the program came from Stanford. In fact, AFAIK, UCONN-Stamford doesn't even have a CS department.
To quote the Wendy's commercial, "Where's the Beef?".
No seriously! Where's this article? I'd imagine three years and 1.25 million dollars would produce a hefty article. I'd love to give it a read! "US Department of Homeland Security has released a report on open source quality"- so where's the release?
It cites one or two figures, and throws around lots of buzz-words, but there's no comparison? No information? No study of reliability? Nothing at all.
PS: As a side-note, if they 'studied' 15 million lines of code over three years, and were able to identify defects, shouldn't we be seeing a nice patchset coming from Coverity sometime soon... Think about it. It's easy to tell someone else to fix it, but a good part of OSS is giving back.
when you see the word 'Linux', drink!
- Tell authors about bugs they find, as they find it
- Submit bugs via the project's bug submission system
- Develop a bug submission standard object format and open testing methodology, maybe even a server and some ontology to help automate this stuff?
- Teach developers ways not to make those bugs again
- Develop open automated bug checkers
- Allocate money to hire programmers to fix important bugs in important open source packages
- Establish a government certification of quality which will be fabulous for open source
- Disclose a roadmap to certification for any given software
- Certify private and academic labs for similar certification
But note that the DHS was established to fight terrorist attacks. Anybody doing this kind of service for OSS and able to provide a certification is nice, but the only valid reason for DHS to do this is if they have special knowhow about potential vulnerabilities of software to cyberwar (NOT - they are using antivirus firms instead of the military to get knowhow) this is really not in their purvue.I am troubled by DHS goons' bullying of people for library use, parking violations, underage drinking or whatever is the latest thing they have to pass the boredom. Cyber security is a great area but they could do best by establishing tools for bug detection and safe code writing. In fact while a government certification and free bug testing is nice it is not what they are supposed to be doing.
Well, at least it can be seen that there is overwhelming bias at slashdot.
- Saying that one race group is inferior to another constitutes a "bias": correct.
- Saying that some software is better than other software constitutes a "bias": incorrect
The two are not analogous. The flaw in your argument is the implicit assertion put forth that "all software is created equal" (so to speak) and that any preference of some software over another must therefore constitute a bias. Here's a cluestick for you: Software really does differ.
I suppose you would also slate a mechanic for "hypocrisy" and "bias" if he said that a Ferrari is better than a Hyundai.
That is perfectly logical. Software that comes OUT of a compiler should certainly be tested for quality. Watcom processes source code, and produces a resulting change, so it's valid to ask questions about that. Likewise, Open Source is a process, with its own unique qualities and product attributes. Also, it's an ALTERNATIVE process to the main ones used to develop software, so the idea of evaluating the different outcomes from each alternative is entirely valid.
Reminds me of when as a noob, I reported an error in a man page to a project mailing list, hoping somebody close to the project might pick it up and fix it. Nah, the response was: OK, write yourself a new man page.
What project was it? Is it anything we care about?
How about linking to your 'bug report' so that we can see this supposed reply?
That attitude still pervades most OSS projects.
What OSS projects are you referring to? Not all OSS projects are equal. You are generalising.
What evidence do you have of most OSS projects having a bad attitude?
I'll probably be modded down for this...
This war has already happened, and open source is just picking off the last few closed source soldiers.
All the apps on my machine are open source (except windows itself), and where the apps go.... Eventually so will the OS. It's just gonna take a lot longer. The app war isn't even fully finished yet. Look at Gimp/Photoshop. They are still kind of duking it out, but gimp is the inevitable winner, and a few graphics profs already realise that and are jumping ship, if for no other added insentive than saving $1.5m on 500 photoshop stations or something.
Open Source has already won. Just let the last few battles play out in the pathetic ways that they will.
rhY
I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.
This article is kind of dump. It compares LAMP to everything else FOSS.
I don't need that, I need to know how FOSS compares to Proprietary Software
I was contacted by an NSA analyst about one of my projects. It's an IRC client with an IRC over SSL feature. The SSL feature doesn't verify certificates (I knew this) and the analyst noted this issue was raised while they were auditing my software. They asked if I planned to fix the problem and when.
Once I was an intern at a govt lab and part of my duties included hacking together a patch for some security type software. I was allowed to release the patch back to the original authors so long as the govt was left out of it.
So they can and do reach out sometimes.
The US Navy replaced Sun with Yellow Dog Linux, originally on Apple hardware and now on some other PowerPC based hardware, for sonar processing on subs.
The kiddies must have mod points today. That was about as humorous as a fart joke, even for someone who is no fan of GWB and is wearing tinfoil.
No, it couldn't be. Your website bites. Having seen it one can see the desolation of the field from which your opinion grew. I'm sorry.
Help stamp out iliturcy.
The Open Source model does not typically conform to the requirements for getting a high rating (Evaluation Assurance Level 4 or higher) for Common Criteria (http://niap.nist.gov/cc-scheme/). Note that it could, but typically FOSS projects do not have this kind of rigor.
A rating of EAL 4 is a typical benchmark that NATO governments use for "low threat" environments.