DoD Wary of That "Open" Word

joabj writes, "Why is the U.S. Defense Department still reluctant to use open source software, despite assurances from within the DoD itself? Blogging for Government Computer News, I found at a recent D.C. conference that to some extent the roadblock might be with that word 'open'."

Why?

I gather it is because of the act of taking on the responsibility of making a solution fit the problem. In a commercial or consulting role, someone claims to have a solution ( or be capable of creating one) that will solve the problems at hand. When a manager ( especialy within the DoD) gives the okay for a canned solution, the responsibilites are already diluted, meaning that if the solution has already been working for others, it is safe to assume that it will work for your organization. If it fails to do so, the manager can point to the other successful implementations and list the differences between your actual needs and the products capabilities. The vendor can then tailor the app more closely to your needs and the manager still looks good.

If we apply the same standards to Opensource, we can look at established projects like Apache, Mysql or even Openoffice and they are still safe because others are successfully using the software, it is not really a matter of a central point for support. For a manager to okay a more obscure project for implementation means taking on a much greater and unknown responsibility.

They'll change their mind

They'll change their mind when they go to war with a country that has paid Microsoft more than they have (or a country that Microsoft has purchased). And the entire Defense department falls apart from deeply embedded backdoors that have been sold to the 'enemy'.
    Global corporations are just that, they don't owe loyality to any nation or any nation's war machine. The Americans will probably learn this (as they learn everything) the hard way.

    In a similar vein, I would believe that all the ultra-high tech weapons that the Americans have sold to their more dubious allies do actually have back-doors that allow the Americans to disable these weapons should they be used against Americans by a country that has had a revolution. This was the lesson of Iran in the late 1970's. Hopefully it will be learned before all the high-tech weapons sold/given to Egypt over the past thirty years are used against the Americans and Israelis after the fall of Murabak's regime and the assendency of an Egyptian Islamic Republic.

Good question

The problem is that the modern military has forgotten many of the lessons history taught their predecessors. Rommel was highly regarded, not because he followed some textbook solution or blamed the manufacturer if things went wrong, but because he innovated, experimented and improvised. The same is true of many of the "great" commanders in history - Julius Caesar disarmed the Celtic navy by using hooks on giant poles to rip the sails off. Hannibal got ruddy great elephants over the alps and invented whole new forms of combat. The American revolutionaries created the sniper.

Battles are not won or lost by whoever has the best terms and conditions from the manufacturer. If you're losing, you won't be around to complain, and if you're winning, you generally won't care.

Every time a major power (such as the US) has paid more attention to giving kickbacks to corporate sponsors than it has to producing successful products or successful missions, that power has had its arse well and truly kicked. Sometimes the power wins anyway, but it is not because of its unimaginative and self-serving attitude, it is despite it. It's not very hard to win when you have total land, sea and air supremecy, and can do round-the-clock carpet-bombing campaigns. (But even then, failure of imagination is lethal. Operation Market Garden got slaughtered because of such egotism.)

Personally, I dislike military structures. I find the notion of winning an argument by having the winner define what the argument was to be primitive and tribal. However, if we're going to have such organizations, we might as well make sure they're functional and concious, rather than degenerately repeating every mistake history has ever recorded.

not completely true

I have direct evidence that some parts of the DOD engine is paying for products with open source compenents. Unfortunately, I can't go into details (yet).

C-Span

I was watching a C-Span panel with US Homeland Security Secretary Michael Chertoff earlier today (rebroadcast from Tuesday 9/12) and he was talking about a lot of things. However, I was very positively struck when he talked about interoperability of first responder radio networks and how it's important that we don't lock ourselves into a proprietary network should the feds mandate a specific system.

He specifically refered to making it an 'open source' setup if we were to mandate specific equipment to avoid vendor lockin.

While I don't follow the open source movement too closely, it's a major reference, from where I see it.

Re:Tech or Politics?

It's better to have something that works well when it's ready, than to have a rushed half assed job that's ready much earlier, but doesn't do the job...
Especially in the military, would you want hurriedly built planes falling apart over enemy territory?

I'd want a program (milspeak for "project") that knows how to limit it's objectives, yet also creates a platform for growth and enhancement.

Thus, if we're on a tight timeline, we'd need a quickly-built airframe that at first is limited (cheap already-existing engines, older model avionics and missiles, etc), but allows easy upgrade to newer faster engines, canards, more capable avionics, misiles and strike capabilities, etc.

Re:Tech or Politics?

This is in response to Behlendorf's description of FOSS development as organic, relatively unplanned. It frequently doesn't include deadlines, guaranteed results, even release dates.

While this is frequently the case, it isn't necessarily the case.

Far too many people think that FOSS is just something you download off the web. Something that someone else creates, but which you, as the customer, have no control over. That choosing an Open Source product is like going to the grocery store, and that you only get to pick whatever products are being offered, and that you otherwise have no say in their design.

However, this isn't necessarily the case. I've spoken to a number of groups on this subject at length, and what a lot of people don't realize is that you can continue to use your existing sources of software, but that you simply have to demand that the developer provide it to you under an Open Source license. That's it. You can still contract out the development work to the companies you're using for custom development. You can still buy from your approved vendors list. The license that the software is provided under is a contractual issue, and thus is something that can be negotiated.

Yes, the vendor may want more money in order to provide their software as OSS. However, if you're a really large corporation or organization (like the US DoD), in generally you'll be able to specify these requirements. Either your vendors meet them, or they don't (in which case you take your business elsewhere). Same as any other requirement specified in the tendering process.

FOSS doesn't have to mean "downloaded from some guys website". For a big organization like the US DoD, this probably isn't terribly desirable (unless the software does exactly what you want, and you can either form a business relationship with the developer, do continued development in-house, or are willing to contract out feature additions and bug fixes to a third party -- this is, after all, the biggest strength of FOSS).

(I wonder what would happen if a really big organization like the US DoD went to Microsoft when it comes time to renew their bulk licensing contract and specified that the software must be licensed as OSS, and in return offered them twice the amount of the previous contract. What would win out? Greed and good business sense, or jealous protection of the code and the loss of a major customer?)

Yaz.

Re:Tech or Politics?

Doesn't Microsoft already have shared source with select partners?

Shared Source != Open Source.

Open Source is about more than just being able to look at and build the source code. It's about the freedom to redistribute the software with your changes at will. It's about being able to hire on whatever development company you desire to enhance and improve the software.

Shared Source is mostly just a rouse to appear open, to try to stave off a migration to more truly open options. Shared Source doesn't really give you much in the way of additional freedoms -- Open Source does (and by Open Source, I am specifically referring to software that is licensed in such a way that it conforms to the Open Source Definition [opensource.org]).

Yaz.

Re:Tech or Politics?

I wonder what would happen if a really big organization like the US DoD went to Microsoft when it comes time to renew their bulk licensing contract and specified that the software must be licensed as OSS, and in return offered them twice the amount of the previous contract. What would win out? Greed and good business sense, or jealous protection of the code and the loss of a major customer?)

What would happen is that MS would quickly get on the phone with their lobbyists and start persuading their captive congressmen to start leaning on the DoD to withdraw the FOSS requirement of the contract, but to keep the price at the same amount.

Re:Those are good points, buttttttt....

You have to assume the DoD is both smart and non-corrupt, and the evidence clearly shows that as a gestalt they are neither.

Fair enough in this specific case I suppose -- however, my comments apply to any organization, particularly any large organization (as they have more money, and thus more leverage).

By way of an example, back in 2005 I attended a Health Informatics conference in Toronto, where a colleague of mine asked a panel of self-described "doers" whether or not they had considered Open Source software. I blogged about it here [mac.com]. In essence, they too were treating Open Source software as if it were a product that sat on the shelf, and not as something that you, as a customer, can demand. It is interesting to note that they discussed all sorts of development and partnership problems that OSS could solve for them, however collectively their attitude was pretty much to look for an existing OSS solution to their problems, and when they didn't find one, go to a commercial developer and use whatever license that developer dictated to them.

This is where organizations are going wrong with OSS. There is nothing wrong with using a commercial developer -- just mandate that the development they do for you is licensed under an OSS license. Canada Health Infoway claimed at the time they had $1.8 billion to spend in the field.

And maybe it's just me, but the customer with $1.8 billion should be the one calling the shots. The problem isn't that they lacked the clout -- only that they lacked the knowledge to know what to ask for. They are at the whim of the development companies they contract out (which has bit these people on the butt before -- there have been a number of cases in this field where organizations have spent millions of dollars and spent years having a custom solution developed, only to find that it no longer suits their current needs (which have changed since development began), and/or won't run on their current deployment environment anymore, necessitating scrapping it and starting all over again).

Yaz.

Hmmm...

The problem is that an Open Source project would quickly become a proprietary project anyway. Take, for instance, VISTA (medical records). Yes, it's open source, hell, it was even developed by the government. However, since the VA's mission is decidedly NOT to provide tech support to the rest of the government, other departments that might use that system are left holding the bag to fully support it IN HOUSE, and that includes a metric ass-load of customization.

Where "Open Source" is really competing is in vertical, single-source support and in that department, it usually doesn't have an advantage. It's not that government is averse to using the stuff, it's just that they don't want to end up with something like the VA and VISTA where they have hundreds of full-time developers devoted to keeping it alive. They'd prefer to sign a vendor on to provide it as a service so they can get on with fulfilling their mission, not pretending to be a software development company.

The benefit of open source is that you "own" the code in the sense of having unfettered access to it and can continue developing it even if the original owner ceases to exist. However, owning the responsibility of perpetual development is precisely what government agencies DON'T WANT -- and, frankly, for good reason. They're not software companies and they're very bad at pretending to be so (take a look at the FBI case management system, for instance). When people make the case for open source on those grounds, you've just presented them with the worst nightmare imaginable, so don't be surprised if they scream and run away.

Re:Hmmm...

What people really don't seem to understand is the reality that it is often more efficient to replace a system wholesale than get a new group of people who have a year of "learning curve" just to figure out what the hell the existing system is doing.

So, pretend you're a department manager with a million bucks to spend on some piece of software and your vendor just ceased to exist. Your existing application is ten years old and full of bugs. Do you spend your million bucks paying the salaries of ten developers to potentially get you to square one after a year or do you spend a half million bucks on licenses and support for a new package and still keep five in-house developers on to work on the transition?

Most people choose option number two. That's just the reality on the ground, so if you're going to make the open source case, frame it in that context. Don't put all your money on "hey! you've got the code!" -- because that's the least of the worries.

Use "Free" Software as in Freedom

Because the DoD allegedly likes freedom and wants to promote it. It is their reason for existance. If "Open Source" is hurting the adoption effort use the original name "Free Software".

"Free Software" intentionally invokes Cold War

The term "free" is an intentional echo of cold war terminology and works for military types. Freedom is what they are all about and they are never supposed to obey an unlawful order. The American ideology of the Cold war carried over from the defeat of the German dictatorship and Japanese Empire but was firmly rooted in American history, writing and law. The core of that ideology is that free, moral people working in honest cooperation and competition are happier and more prosperous than people toiling under centralized dictatorships. Interesting expressions of these ideas can be found in the writing of Robert A. Heinlein, especially Starship Trooper [wikipedia.org], which is recommended reading in the US Marine Corps. Free software is an honest effort to make things work, guided by a free meritocracy. It works and has become best of class because people agree not to screw each other over, standards to modularize their work make it so things are interchangeable and the fittest work survives.

Officers with higher degrees will instantly appreciate the peer review nature of free software. People who have published scientific articles understand first hand the practical requirements of repeatability too. To them, if you can't repeat it yourself you have to take it on faith and no military person wants faith in anything but the almighty when they can have proof instead.

The non free people tried to call free software, "software communism" but failed and may have it thrown back in their face. Any military person will tell you that Communist contries are really nasty little fiefdoms, where who you know is more important than what you know and the top guy is in absolute lawless control of everything until murdered. This more resembles the distrustful, back stabbing and intentionally wasteful world of non free software in methodology and results.

I'll quote the gnu.org sites, see what you think:

... what else could we say about a system based on dividing the public and keeping users helpless? ... One [non free propaganda] assumption is that software companies have an unquestionable natural right to own software and thus have power over all its users. ... [another is that] we would have no usable software (or would never have a program to do this or that particular job) if we did not offer a company power over the users of the program. [gnu.org] and Consider these four practices of the Software Publishers Association (SPA): [gnu.org]

1. Massive propaganda saying it is wrong to disobey the owners to help your friend.
2. Solicitation for stool pigeons to inform on their coworkers and colleagues. Raids (with police help) on offices and schools, in which people are told they must prove they are innocent of illegal copying.
3. Prosecution (by the US government, at the SPA's request) of people such as MIT's David LaMacchia, not for copying software (he is not accused of copying any), but merely for leaving copying facilities unguarded and failing to censor their use.

All four practices resemble those used in the former Soviet Union, where every copying machine had a guard to prevent forbidden copying, and where individuals had to copy information secretly and pass it from hand to hand as ``samizdat''. There is of course a difference: the motive for information control in the Soviet Union was political; in the US the motive is profit. But it is the actions that affect us, not the motive.

Thats funny

The last time I checked, the DOD has an enterprise license for RedHat Enterprise Linux.

So what

They already use "Open Fire", "Open Range" and "Openpray" why not opensource.

All things considered...

As much as we bitch at the government for hiding this secret project and that wiretapping, why should we be SURPRISED that they don't like the word 'Open'?

Appearance is everything

As someone in the military, I can tell you for sure that appearance and impression matters MUCH more then function or realism. It's all about how it looks or how it sounds, not what it does or how well it does it. There's a reason our fighter planes aren't called the Kitty or the Puppy. Heh heh, the F-22 Puppy, that'd be funny.

If the DoD write some software ...

If the DoD write some software, then it either has to be 'secret' (not released to the public), or 'open' (given as source code for all to use).

Copyrights and patents are 'private' rights. The DoD, being part of the US Government, can't hold any 'private' rights. They can buy (the right to use some) closed source software, sure, but if they create any software then they cannot sell it.

Have to keep it secret or give it away.

For one, fear of being too open.

You have to admit, at first glance it is a bit worrisome to use a product that is totally open for all the worlds eyes and ears to see. Combine that with the fact that most of the guys in charge aren't particularily computer savvy, and it isn't hard to see why open source would held back.

MS has worked quite well for most things that the military has needed in the past. At least it was when I was in. I can see how "open" might be construed negatively.

And that my friends....

...is why OpenBSD is so infamous for being insecure.

NMCI

I work in a military environment. Recently our computers were transitioned to NMCI. Result: All open source is strictly prohibited. My workspace had designed a really awesome database powered by MySQL and other open source technology. When NMCI came online we were SOL. When we asked for help, we were advised we could spend a $xxx,xxx and purchase a Microsoft SQL Server license instead. When we pushed the issue, we were told that we were welcome to submit MySQL to NMCI for approval but that no one knew how to file the paperwork and no one had ever seen any software approved before. My take: It's a money scam. Somehow NMCI and Microsoft profit from each other with an exclusive agreement.

Why don't the change the name from "Open Source"

to "Free To Examine" ??

So basically, what you're saying is...

...that the wrong people are making the decisions on which software to use. They're going off its label rather than its functionality.

and MS Open License & MS Open XML!

I guess that means the DoD will no longer buy MS software licenses. After all, Microsoft now calls that the Microsoft Open License:
http://www.microsoft.com/licensing/programs/open/ [microsoft.com]

And I guess there is no way they could use the new MS Office Open XML file formats either:
http://www.microsoft.com/office/preview/itpro/file overview.mspx/ [microsoft.com]

What is really missing:

Open Minds.

The "Donald" Issue...

Its probably a Rumsfeld problem, you can imagine the situation

Today's Agenda
1) Break Geneva convention
2) Set up illegal prisons overseas
3) Hide report into WMD
4) Cover-up issues around troop deployments
5) Should we approve Open software use?
6) Prepare for Senate investigation commitee meeting

I mean by the time he got to item 5 he was unlikely to go for openness.

They Can Still Be Grateful....

....that they don't have to use the word "free".

"Freedom Sauce"...

would be my suggestion for a DoD-friendly monicker.

Also, I recall whenever I install Oracle (closed source) I have to click an agreement that I will not use the software in the design or production of biological, chemical or nuclear weapons. I've never encountered such a clause when using open source software, so maybe this might be something that would appeal to the DoD, who I presume would rather not be tracked down by one of Larry Ellison's hit squads.

A handful of reasons

1) Liability. Contractors want somebody to sue if something goes wrong. The DoD will blame the contractor.
2) Specs. Usually, the system is being developed is meant to replace another system that is in-place. The only things to be changed are what are specced out. This doesn't prevent things from being entirely rewritten, but it usually stays on an existing DoD platform.
3) Speaking of platforms, check out the existing specced out platforms. Lots of people go with DIICOE, or GCCS for various reasons. Some might include a desire to get something included as a DIICOE segment, which is profitable, or GCCS, because it's ubiquitous.
4) STIGs. If there isn't a STIG written for it, you're going to have a harder time getting approval to operate it on a classified network. Even if all of your major apps are covered, you'll have to get extensions regarding applications that are not covered. Extensions are not intended to be waivers... so, you're only supposed to get an extension if you intend to replace it. It is hard to justify an extension for new software. Why not just write it in a compliant fashion? Because the security audit will be more of a PITA, they avoid any step into the unknown. Some of this is just inertia.
5) Security through obscurity. It sounds asinine, but the DoD doesn't rely on security through obscurity.... they rely on anything that is considered a good practice, obscurity is just one of those many practices. It's not that they are using telnet or anything silly like that. It's just that they want as many layers as possible.
6) Common open source is embraced. Everyone runs Apache. It's as ubiquitous as IIS. It's the things that are considered more "out there" that aren't.

All of that aside, there have been open source initiatives, but contractors have been reluctant to bite. Reasons vary, but this is the essential dynamic. The DoD retains the rights to most of the source code for projects that they fund, so, they already have the source code... they give it to anybody that they please, including the next contractor to work on the project. Contractors don't want to share source with each other for competitive reasons. Since they're all bidding to produce identical products, giving other contractors the ability to develop experience with a product can only hurt their business, this experience is their primary bargaining chip when bidding (that and the ability to undercut their competitors, or qualify for special considerations, such as being a small business).

Then there is the concern of enabling foreign interests to develop commensurate technologies. Nobody wants to share code to decode IFF signals, or to build similar systems. Thinking that the government would publish code to do these things is just asinine.

You always have your crumudgeons who also will just resist open source... which is the same even outside of DoD interests, but the DoD comes with a host of other concerns. All of these in mind, I'm not sure that the DoD is necessarily stilted against open source. Some sectors of the DoD have embraced it quite readily... these are just the faster-moving sectors who adopt technologies more readily. The DoD is a very large entity, and, as such, slow adoption, when combined with very well established platforms results in this exact behavior.

And just how much money

does the open source community spend on lobbyists ?

$0.00 ?

And you wonder why its not used.

"Open" misnomer

I recently advised a few people at work to consider OpenOffice as an alternative to the use of MS Office. I was met with an answer I didn't expect. One commented that "it looks interesting, but I don't want just anyone to be able to read all of my files." This took me aback a minute until I realized that they assumed "Open" meant their data/files/Harddrive where "Open" to inspection by anyone "online". It takes a while to explain to this class of computer user just what is meant by the labels used by the "Open Source" community.

It's this same group of people that were convinced once they couldn't use Thunderbird to check their email because "well my ISP automatically sets up and uses /insert outlook or similar client here/".

Schizophrenic DoD

You gotta love the schizophrenic nature of the DoD, on one hand they have elements afraid of open source because of the word "open" and on the other hand the NSA, an arm of the DoD and the group in charge of computer security, not only uses open source based software but has even contributed to it.

http://www.nsa.gov/selinux/ [nsa.gov]

dod

of course we all know that the us dod is a monolithic
entity that only holds one opinion about anything.

Open source renamed for DoD

War on Proprietary Software.

"Open"

You keep using that word. I do not think it means what you think it means.

I'm not unhappy with that

I must say, I'm really not unhappy with that. In fact, I would dislike it very much if any of my open source contributions would be used by the military (of any country). I even once considered blocking access to my web site from .mil domains. I didn't because it would be completely silly, and there is no reason to block only .mil and let all the other military through. And after all, "open" is "open", and anyway, I have neither the time nor the moral authority to decide who is "good" and who is "bad".

But nevertheless, if the military would rather not use any of my "open" code, it makes me feel better, even if it is not rational.

If it's just about semantics...

Why don't we drop the Open from Open Source Software and replace it with Available? Then we can be part of the ASS community.

I mean, the best part about ASS is that it's always available for the asking.

Open source is EVERYWHERE in the defense community

I work for a defense contractor, and there are supposedly some rules from on high that open source is frowned upon, as is any software not written by a company in the United States.

I routinely bring software in to use on various projects, and I favor open source or, more spefically, free software, except in cases where a proprietary product is clearly better (example: BitKeeper is better than any open source SCM tool). It's simple, really. If I can start using it tomorrow rather than ask the businesspeople to purchase something and use it next week if I'm lucky, that's just easier for me.

The reason I say 'tomorrow' is because it's not quite hassle-free. I have to turn in a form to justify putting software X on the classified network. The form, of course, was not written by anyone who even considered the possibility of open source. It asks what company wrote the product (I do my best to oblige and say something like "Free Software Foundation" or "The ____ Project" if I really can't find any organization) and where that company is headquartered (I just try and put anything at all that seems to fit, such as an address found in a whois request).

To the people who really insist that open source has no place on a defense networks, I say, do you have any idea how many Linux machines are already being used on said networks? Do you realize how many GNU tools are being used, even on the proprietary machines? That gcc, for example, is the compiler of choice, at least where I'm working? The people who make these statements have no idea what they're already running.

Not the only reason, but a possible one.

One of the problems is that it is free, meaning they don't pay for it. The Army doesn't ever get something for free. There are policy's against it.

The idea is that, eventually Guido is going to want you to repay the favor. The Army can't get something for free because, later on, it might be seen as biased.

Also, they want to be seen as supporting American buisnesses. When you use open-source, and get it for free, it is almost like you are taking it away from the economy.

Now, I don't dispute that there are more reasons... Someone to blame and all that kind of stuff. But it is not necessarily cloak and dagger, nor just being against change.

What the DoD objects to

#include <std_disclaimer.h>

Good lord, I actually have something to contribute!

In a nutshell, the DoD *really* doesn't like that they don't know who wrote the software, and they also don't like the lack of a central point of contact. They'd rather hire, say, $defense_contractor to write a similar piece of software, because they get a couple of reassuring beliefs (we will not attempt to discuss the VALIDITY of these beliefs, please):
1) that $defense_contractor is using properly trained, vetted programmers, with security clearances if need be; and
2) that if anything goes wrong, they can sue the tar out of $defense_contractor.

These two factors are VERY important to the DoD. Now, you can probably see the utility if the DoD has requested, say, software for their Death Ray [1], but isn't that overkill if they're trying to buy a web browser? Yes it is--but they can't help it. The DoD has LOTS of finicky aquisition rules, and they're pretty much the same whether you're buying Death Ray Guidance Software or a web browser.

In my day job, I am, among other things, involved with the government's Common Criteria Evaluation and Validation Scheme (CCEVS) [bahialab.com]. Due to the DoD's acquisitions rules (DoD Instruction 8500.2), in almost all cases all Commercial Off-The-Shelf (COTS) software must have undergone a CCEVS evaluation. As you might imagine--we are after all dealing with the government--CCEVS evaluation is really REALLY expensive and takes frickin' forever.

Now, this is no barrier to Microsoft, which has had enough money and time to get Windows {2000, 2000 Server, XP, XP Pro, 2003 Server} evaluated. But, as you might imagine, it's a pretty damn big barrier to open source products. Those that have been evaluated (SuSE, Red Hat) have been lucky enough to have some heavyweight patrons (IBM and Red Hat, respectively) on their sides.

Nor is a CCEVS certificate the end of the game. DoD agencies typically must justify why they've chosen solution X over solution Y; and, while cost is a factor, it's far from the most important one. Open source products tend to come with a list of disclaimers as long as your arm (OpenSSL's FIPS 140-2 certificate, for example, says that the certificate is only good for THIS version of the source code, compiled with THAT version of gcc, THESE SPECIFIC static libraries compiled in, etc., etc.), and the guy writing up the justification paper is probably an overworked lieutenant prone to thinking "Fsck this. No one got fired recommending Microsoft."

[1] The notion of a DoD "Death Ray" is entirely a fabrication of my own fertile (if perhaps deranged) imagination. Any similarity to any actual research, prototypes, and/or super-double-secret weapon is entirely coincidental. Please don't put me in GITMO. Thanks.

Don't you believe it...

NMCI notwithstanding, there's tons of open source software running all over DoD as we speak, and very little of it is likely to go away anytime soon.

I have used Open Source within DoD

I have used RedHat Linux and OpenOffice in the Army. They are there and implemented in combat. The soldier isn't aware of this because they work behind the scenes, but open source is being used in several applications.

Could it be?

The viral provisions of many open source licenses scare them off? From firsthand experience I can tel you that it does.

Also, you have the anti-US, anti-DoD attitude of many "open source" developers and advocates.

a few issues

The resistance to open source I have seen is "who do you call when something goes wrong?"

That's the primary issue. Another is having the luxury to point the finger at the COTs vendor...MS, Oracle, etc...when something goes wrong..."It's not our fault, it's that shitty MS upgrade".

Another issue still is concern that, should a open source project be KNOWN to be used for classified processing, the authors could be compromised or the s/w could be targeted/examined for holes.

Another issue is mixing code that touches classified data with MS includes and libraries does not obligate open source release...while mixing with GNU might. Releasing code from the govt oftens requires time, money, effort. Or a competing shop could use that argument against the use of open source. "No one gets fired for choosing MS"...your company loses the contract.

However I have seen a rallying cry lately among a lot of civil service types..."Linux Everywhere!"...there is significant happiness in many areas of government using Linux or other open source. The non-recurrent licensing costs are very appealing to government.

I've worked in several shops that dump $10K-100K a year to MS...it can be a real drain for projects in sustainment.

No problem!

The whole issue is this wimpy, do-gooder pinko commie vibe you get from "open" and "share" and "please don't kill innocent civilians" crap.

Just do a cut and paste and replace "open" with "Dark Top Eagle Hammerfist YMCA Shiny Leather" and you'll see military types lining up around the block for the stuff.

Time to rebrand then.

So call it "flex source" or "agile source" The military loves terms like that.

The choice shouldn't be difficult

How many people have said linux is "killer" software compared to the number of people who have said "Windows will be the death of me"? Export list be damned. We should be promoting Windows to our enemies.

Just use a different word

"Free Sofware" as in the Freedom you are bringing to... *ducks*

administrative talent perhaps

Let's not fool ourselves, open source software takes talented people to run, not the normal graduates of 6-week "learn-computers-fast-to-make-money.com" windows training that is the mainstay of price thrifty contractors that make up the entire backbone of all DOD IT departments. I'm sure there are talented admins in the DOD, I've met some, but they are the exception rather than the rule. "Best and Brightest need not apply"

"Blogging for Government Computer News"?

Nevermind the incorrect capitalization, but does that even mean anything? Yes, this is offtopic, yes this is nitpicking, but seriously: Does that really mean any more than "Smurfing for government computer wews"? Personally I think "grofling for news" sounds cooler, not to mention it's one step ahead of being branded "hip" in that negative way.

Anyway, I stopped reading right there. So the comments here may be gibberish and all non-sense, but can't we at least expect the summaries to be in semi-proper english?

The DoD mindset.

To really comprehend this, I think it goes much deeper than opensource standards, or integration. The DoD has an attitude, a philosphy if you will - that everything is behind closed doors and not discussed. It's a world of classified information that is protected to pretty rigorus standards. To adopt or use anything that suggests otherwise (whether or not it actually does) just flies in the face of everything they know and understand. It's just the world they live in.

Re:I see their point

Sadly, this is a fallicy that is widespread in people who are clueless about security. Take a closed source product from Microsoft for example. How many people within MS have access to that code? How many still work for MS? How many outside the US both have had access to the code and no longer work for MS?
How many are pissed that they were fired or laid off?

You have to look at security as a cost v. reward thing. It may be very expensive to obtain and reverse engineer a binary program which is used as part of a security system. But if it uses "Security through obscurity", you only have to do it once. If you use a real security system, it has to be cracked every time the keys change.

Re:I see their point

I would potentially believe that security through obscurity works if so many of our servers that run the critical tasks of our Internet's infrastructure didn't run Apache or other Linux operating systems. The great thing about Open Source software is that you don't have to leave the code the same way you received it. For example, if the DoD wanted to adopt Apache to run all of their webservers, they could always modify or build an entirely new custom Apache-ish server off of the source code. In essence, that could make an exploit that would normally succeed on a standard Apache server fail on the DoD's modified model. As long as they don't turn around and resell it, it's within their rights in the GPL to modify it. That's the freedom in Open Source software. No proprietary software would allow you to do that without first paying them a metric ton of money.

Re:I see their point

"When the source code is available to everyone, that also means that it's easier for the enemy to find security holes to exploit.

"Security through obscurity" isn't a bad thing. If you can manage to keep tight control over who has access to the source code, you've eliminated one more security issue. Obviously, the quality of the code is more important. But still."

Only on Slashdot would this be modded as flamebait. Use some logic people! Open source does not necessarely equal more secure. It often can, but it isn't a guarantee. Open source software usually presents an advantage only when a piece of software is popular enough to have enough devs poking at it. Yes, I know, all it takes is one person to find an exploit but I'm just trying to show that OSS is not inherently more secure.

Take this example: You have two software applications for, I don't know, missile tracking and detection. One is open source, one is closed source. Assume for now that they are equally secure. (Yes, this is possible!) Now assume that you are trying to compromise this system. You can grab one application on sourceforge while the other is completely secret. You have no idea how it works - for all you know it could do things completely different than the open source software. Which one will be easier to compromise? Now, I grant this logic doesn't really work for things like Windows XP where Microsoft and not the DoD create and maintain the software but the point remains for a number of situations that I can imagine.

I still don't understand why this whole "Security through obscurity is evil!" sound bite started. Everyone loves steganography around here, right? And I know the concept of hiding things in plain site is often discussed here in a favorable light. Are these not forms of security through obscurity (minus steganogaphy+encryption)? Would you prefer to store your Rolex in a closet safe or in a hidden compartment in the front panel of your dishwasher? And if you do choose the safe, should you advertise it? Maybe post a sign in the front of your house that says "The safe is in the bedroom closet on the right and contains a $20,000 watch. Come test my great security!" (Obviously a well hidden safe combines the best of both worlds here.)

Security through obscurity is not inherently bad. It has merit in *some* situations and to say otherwise is juvenille.

Re:Name Change

"Public source" can also refer to the Microsoft Shared Source Initiative's look-but-don't-touch "Reference" license, which is considered unacceptable by both the free software community and the open source community.