Open Source in the Military?

djmcmath asks: "Does anyone have any experience with Open Source Software and/or GPL'd software in military applications? I'm only asking because I'm involved in work on the combat systems for a new submarine, and had considered an Open Source solution. (I apologize, I must be intentionally vague for obvious reasons.) So ignore the obvious questions (Is it really suitable? Are closed-source proprietary options better? Does MS have a good solution?) and skip to the good stuff. What about the fact that my code would be classified Secret under US Code Umptifratz? I cannot distribute my code (and it's changes) without being tried for treason. What happens to the rest of the combat system code when I submit my GPL'd module?" Open Source and the Military: it's a tricky combination of keeping what can be open, open and keeping your secrets...well, secrets! However, open source in the military need not be as high profile as weapons systems. One of the only major OS projects that I'm aware of that had any form of military involvement was GRASS, the open-source GIS system. I'm sure there may be a few others out there. Does anyone know of other OS projects with military association? If there are any projects out there that interface with classified bits, how did you deal with those issues?

Comments

GLP and software availability

[Account 10]

You only need to distribute the source to the people that you distribute the binary to.

Presumably the binary is covered by the same secrecy rules as the source, so the only people entitled to the source are the miltary.

Although, if the binary is in a bomb, you may also need to distribute the source to the poor sod that you drop it on.

Re:GLP and software availability

[linzeal]

They could just include the source in a leaflet attached to the side of the bomb with a stern finger wagging RMS on it.

Re:GLP and software availability

[FattMattP]

Although, if the binary is in a bomb, you may also need to distribute the source to the poor sod that you drop it on.

That would only be necessary if he's going to execute the code. If the code is in a bomb, it's more likely that it's going to be executing him.

Support?

[gehrehmee]

Open software is typically accompanied by open support. If the usage of your software is as secret as you make it sound, it might be really difficult to get technical support from the community in the same way civillian users might.

I finally got Linux 2.4.CLASSIFIED to work on my CLASSIFIED system, which required me to work around the CLASSIFIED component attached to the CLASSIFIED-CLASSIFIED. However, I'm still having some stability problems. Anybody see anything blatently wrong with this patch? :

--- /usr/local/src/linux/fs/devices.c Sat Sep 22 21:35:43 2001
+++ CLASSIFIED.c Sat Mar 16 14:32:35 2002
@@ -32,7 +32,7 @@

struct CLASSIFIED_struct {
const char * name;
- struct file_operations * fops;
+ struct string_operations * CLASSIFIED;
};

static CLASSIFIED_t CLASSIFIED_lock = RW_LOCK_UNLOCKED;
@@ -62,9 +62,9 @@
Load the CLASSIFIED if needed.
Increment the CLASSIFIED count of module in question.
*/
-static struct CLASSIFIED_operations * get_chrfops(unsigned int CLASSIFIED, unsigned int CLASSIFIED)
+static struct string_operations * get_chrfops(unsigned int CLASSIFIED, unsigned int CLASSIFIED)
{
- struct CLASSIFIED_operations *ret = NULL;
+ struct CLASSIFIED_operations *ret = NULL;

if (!CLASSIFIED || CLASSIFIED >= MAX_CHRDEV)
return NULL;
@@ -95,7 +95,7 @@
return ret;
}

Re:Source Distribution

[Anonymous Coward]

Are you distributing your executables? If you use the OSS for a specific system and only on that system, you are not required to distribute source - everyone that has the binaries (the military) will have the source.

It's actually simpler than that -- this is the US -- therefore, you only need to say aloud one of two magic incantations, "National Security" or "For the love of God, will no one think of the children?" and debate is terminated. In your favor.