Open Source Warfare: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Definition= | |||
"'''Open source warfare, like what we see in Iraq and increasingly in other locations, relies on networks of peers rather than the hierarchies of command and control we see in conventional militaries.''' This structure provides an open source movement with levels of innovation and resilience that rigid hierarchies can't match. Unfortunately, these attributes are likely not constrained to merely local tactical activity. Open source movements can exhibit emergent intelligence that guides the movement's collective actions towards strategic goals." | "'''Open source warfare, like what we see in Iraq and increasingly in other locations, relies on networks of peers rather than the hierarchies of command and control we see in conventional militaries.''' This structure provides an open source movement with levels of innovation and resilience that rigid hierarchies can't match. Unfortunately, these attributes are likely not constrained to merely local tactical activity. Open source movements can exhibit emergent intelligence that guides the movement's collective actions towards strategic goals." | ||
(http://globalguerrillas.typepad.com/globalguerrillas/2006/02/emergent_intell.html) | (http://globalguerrillas.typepad.com/globalguerrillas/2006/02/emergent_intell.html) | ||
=Characteristics= | |||
'''Global Guerillas on how Open Source Warfare takes on a "Bazaar" format:''' | '''Global Guerillas on how Open Source Warfare takes on a "Bazaar" format:''' | ||
| Line 19: | Line 26: | ||
* Tools are often used in unexpected ways. An attack method can often find reuse in unexpected ways." | * Tools are often used in unexpected ways. An attack method can often find reuse in unexpected ways." | ||
(http://globalguerrillas.typepad.com/globalguerrillas/2004/09/bazaar_dynamics.html) | (http://globalguerrillas.typepad.com/globalguerrillas/2004/09/bazaar_dynamics.html) | ||
=More Information= | |||
#http://spectrum.ieee.org/telecom/security/opensource-warfare | |||
[[Category:Encyclopedia]] | [[Category:Encyclopedia]] | ||
Revision as of 14:24, 7 February 2010
Definition
"Open source warfare, like what we see in Iraq and increasingly in other locations, relies on networks of peers rather than the hierarchies of command and control we see in conventional militaries. This structure provides an open source movement with levels of innovation and resilience that rigid hierarchies can't match. Unfortunately, these attributes are likely not constrained to merely local tactical activity. Open source movements can exhibit emergent intelligence that guides the movement's collective actions towards strategic goals." (http://globalguerrillas.typepad.com/globalguerrillas/2006/02/emergent_intell.html)
Characteristics
Global Guerillas on how Open Source Warfare takes on a "Bazaar" format:
The decentralized, and seemingly chaotic guerrilla war in Iraq demonstrates a pattern that will likely serve as a model for next generation terrorists. This pattern shows a level of learning, activity, and success similar to what we see in the open source software community. I call this pattern the bazaar. The bazaar solves the problem: how do small, potentially antagonistic networks combine to conduct war? Lessons from Eric Raymond's "The Cathedral and the Bazaar" provides a starting point for further analysis. Here are the factors that apply (from the perspective of the guerrillas):
- Release early and often. Try new forms of attacks against different types of targets early and often. Don’t wait for a perfect plan.
- Given a large enough pool of co-developers, any difficult problem will be seen as obvious by someone, and solved. Eventually some participant of the bazaar will find a way to disrupt a particularly difficult target. All you need to do is copy the process they used.
- Your co-developers (beta-testers) are your most valuable resource. The other guerrilla networks in the bazaar are your most valuable allies. They will innovate on your plans, swarm on weaknesses you identify, and protect you by creating system noise.
- Recognize good ideas from your co-developers. Simple attacks that have immediate and far-reaching impact should be adopted.
- Perfection is achieved when there is nothing left to take away (simplicity). The easier the attack is, the more easily it will be adopted. Complexity prevents swarming that both amplifies and protects.
- Tools are often used in unexpected ways. An attack method can often find reuse in unexpected ways."
(http://globalguerrillas.typepad.com/globalguerrillas/2004/09/bazaar_dynamics.html)