This report documents the results of a short email-mediated study by The MITRE Corporation on the use of free and open-source software (FOSS) in the U.S. Department of Defense (DoD) . FOSS is distinctive because it gives users the right to run, copy, distribute, study, change, and improve it as they see fit, without having to ask permission from or make fiscal payments to any external group or person. The autonomy properties of FOSS make it useful for DoD applications such as rapid responses to cyberattacks, for which slow, low-security external update processes are neither practical nor advisable, and for applications where rapid, open, and community-wide sharing of software components is desirable. On the other hand, the same autonomy properties complicate the interactions of FOSS with non-FOSS software, leading to concerns—some valid and some not—about how and where FOSS should be used in complex DoD systems.

The word free in FOSS refers not to fiscal cost, but to the autonomy rights that FOSS grants its users. (A better word for zero-cost software, which lacks such rights, is "freeware.") The phrase open source emphasizes the right of users to study, change, and improve the source code—that is, the detailed design—of FOSS applications. Software that qualifies as free almost always also qualifies as open source, and vice versa, since both phrases derive from the same set of software user rights formulated in the late 1980s by Richard Stallman of the Free Software Foundation .

The goals of the MITRE study were to develop as complete a listing of FOSS applications used in the DoD as possible, and to collect representative examples of how those applications are being used. Over a two-week period the survey identified a total of 115 FOSS applications and 251 examples of their use .

To help analyze the resulting data, the hypothetical question was posed of what would happen if FOSS software were banned in the DoD. Surprisingly, over the course of the analysis it was discovered that this hypothetical question has a real-world analog in the form of proprietary licenses that if widely used would effectively ban most forms of FOSS . For the purpose of the analysis, the effects of the hypothetical ban were evaluated based on how FOSS is currently being used in survey examples. In the case of niche-dominating FOSS products such as Sendmail (ubiquitous for Internet email) and GCC (a similarly ubiquitous compiler), a large amplification factor must also be taken into account when estimating such impacts. The actual levels of DoD use of such ubiquitous applications is likely to be hundreds, thousands, or even tens of thousands of time larger than the number of examples identified in the brief survey.

The main conclusion of the analysis was that FOSS software plays a more critical role in the DoD than has generally been recognized. FOSS applications are most important in four broad areas: Infrastructure Support , Software Development , Security , and Research . One unexpected result was the degree to which Security depends on FOSS. Banning FOSS would remove certain types of infrastructure components (e.g., OpenBSD ) that currently help support network security. It would also limit DoD access to—and overall expertise in—the use of powerful FOSS analysis and detection applications that hostile groups could use to help stage cyberattacks. Finally, it would remove the demonstrated ability of FOSS applications to be updated rapidly in response to new types of cyberattack . Taken together, these factors imply that banning FOSS would have immediate, broad, and strongly negative impacts on the ability of many sensitive and security-focused DoD groups to defend against cyberattacks.

For Infrastructure Support , the strong historical link between FOSS and the advent of the Internet means that removing FOSS applications would result in a strongly negative impact on the ability of the DoD to support web and Internet-based applications. Software Development would be hit especially hard for languages such as Perl that are direct outgrowths of the Internet, and would also suffer serious setbacks for development in traditional languages such as C and Ada. Finally, Research would be impacted by a large to very large increase in support costs, and by loss of the unique ability of FOSS to support sharing of research results in the form of executable software.

Neither the survey nor the analysis supports the premise that banning or seriously restricting FOSS would benefit DoD security or defensive capabilities. To the contrary, the combination of an ambiguous status and largely ungrounded fears that it cannot be used with other types of software are keeping FOSS from reaching optimal levels of use. MITRE therefore recommends that the DoD take three policy-level actions to help promote optimum DoD use of FOSS:

1. Create a "Generally Recognized As Safe" FOSS list. This list would provide quick official recognition of FOSS applications that are (a) commercially supported, (b) widely used, and (c) have proven track records of security and reliability—e.g., as measured by speed of closures of CERT reports in comparison to closed-source alternatives. Initial applications for consideration would include, but not be limited to, the set of 115 already-used applications identified by the survey in Table 2, plus other widely used tools such as Python (http://www.python.org/ ) that did not appear in this first set of results. In formulating the list, quick consideration should be given in particular to high value, heavily used infrastructure and development tools such as Linux ,OpenBSD , NetBSD , FreeBSD , Samba , Apache , Perl , GCC ,GNAT , XFree86 , OpenSSH , bind , and sendmail .
2. Develop Generic, Infrastructure, Development, Security, & Research Policies. The DoD should develop generic policies both to promote broader and more effective use of FOSS, and to encourage the use of commercial products that work well with FOSS. A good example of the latter is the Microsoft Windows Services for UNIX product, which relies on FOSS (GPL ) software to reduce development costs and dramatically increase its power. A second layer of customized policies should be created to deal with major use areas. For Infrastructure and Development, these policies should focus on enabling easier use of GRAS products such as Apache, Linux, and GCC that are already in wide use, but which often suffer from an ambiguous approval status. For Security, use of GPL within groups with well-defined security boundaries should be encouraged to promote faster, more locally autonomous responses to cyber threats. Finally, for Research the policies should encourage appropriate use of FOSS both to share and publish basic research, and to encourage faster commercial innovation.
3. Encourage use of FOSS to promote product diversity. FOSS applications tend to be much lower in cost than their proprietary equivalents, yet they often provide high levels of functionality with good user acceptance. This makes them good candidates to provide product diversity in both the acquisition and architecture of DoD systems. Acquisition diversity reduces the cost and security risks of being fully dependent on a single software product, while architectural diversity lowers the risk of catastrophic cyber attacks based on automated exploitation of specific features or flaws of very widely deployed products.

The author is deeply grateful to the following people, all of whom were gracious enough to review earlier versions of this document and make major contributions to the creation of this revised and greatly expanded version: Ira Rubinstein, David A. Wheeler, Tony Stanco, Frank Petroski, John D. Ramsdell, Bill Neugent, David H. Lehman, Robert F. Nesbit, Fritz Schulz, Dawn Meyerriecks, Flayo Kirk, Jan S. McNutt, Robert E. Cole, Robert Shepherd, William Curtis, Asghar Noor, and Jesse Pirocchi. The author would also like to thank all the MITRE and non-MITRE respondents who helped in the survey. In reverse alphabetical order these contributors include: Jim Van Zandt, Rob Wittman, Shawna Wimpy, George Wilson, Darryl Washington, Nathan Vuong, Gene Vogt, Gary Vecellio, Colin Valentine, Paul Valente, Stephen Upton, Porter Taylor, P Supko, Ed Shrum, Dan Scholten, Jacques Sabrie, Bryan Russina, Jarret Rush, Jeff Ross, Maureen Robinson, Frederick Potts, Bryant Obando, Doug Norman, John Morris, Mike McClimens, Mark Maybury, John Maurer, Karen Mason, Bill Mack, Dan Lowen, Daniel Loehr, Amlan Kundu, Anita King, Stephen Jones, Dan Jones, Mike Jay, David Jacobs, DeAnn Iwan, Bill Horton, Lee Hobbins, Jean Henchey, Ray Haller, Paul Grund, Steven Gosnell, Bob Goldsmith, James Finegan, Allen Epps, Alexander Enzmann, Perry Engle, Darren Dusza, Peter Dugan, Emil Derenzo, Ken Christy, Dave Burgess, Chuck Boeckman, CDR Christopher Biow, Carl Benkley, Matt Beebe, Scott Barman, Richard Baldwin, Pete Attas, Douglas Atkinson, Jon Anderson, and Dock Allen. Finally, I would like to thank the following people, also listed in reverse alphabetical order, for providing post-release corrections to report: John Worrall, David N. Welton, W. Craig Trader, Larry Sevilla, David Neeley, Melchior Franz, Alan Knowles, and Lee Doolan.

— Terry Bollinger, The MITRE Corporation

To receive the most recent version of this MITRE Corporation document, or to recommend any additions or changes to the document, please contact Terry Bollinger at [email protected] .

List of Figures

List of Tables

1. Introduction
1. Purpose

This report documents the results of a short email-mediated study by The MITRE Corporation on the use of free and open-source software (FOSS) in the U.S. Department of Defense (DoD) . The goals of the MITRE study were to develop as complete a listing of FOSS applications used in the DoD as possible, and to collect representative examples of how those applications are being used. Over a two-week period the survey identified a total of 115 FOSS applications and 251 examples of their use (Table 2).

2. Document Overview

This document is extensively linked both internally and to relevant external web sites. To use the links, simply click on the underlined words or phrases in the electronic version. The paper version of the document also shows the addresses of external as both footnotes and as references in Appendix E. Please note that certain links to locations in Appendix F will not work if you do not have a copy of the separate file that contains that appendix.

Section 1 (this section) provides background information on FOSS, an overview of how the survey was conducted, and a summary of results. Section 2 provides an analysis of the survey results, focusing on understanding the types of FOSS users identified in the survey. Finally, Section 3 provides three major recommendations, which can also be found in the Executive Summary at the very beginning of this document.

The survey data and data breakdowns are provided in the form of six appendices. Appendix A lists the full set of 115 FOSS applications identified in the survey, and breaks them down by application area. Appendix B provides descriptions of the individual FOSS applications, with links to the examples of use identified for each tool. Appendix C provides a detailed breakdown by application area of which FOSS licenses are used by the identified applications. Appendix D is a lengthy appendix that provides the full text of every license used by the identified tools, as well as additional related licenses and license information. Appendix E summarizes references from the document, which can also be found as linked footnotes throughout the document. Finally, Appendix F contains a Sensitive But Unclassified (SBU) table of all the example uses of FOSS found in the survey. It is contained in a separate file.

3. Background: Questions and Answers About FOSS
1. What is Free and Open-Source Software (FOSS)?

Free and open-source software (FOSS) is software that gives users the right to run, copy, distribute, study, change, and improve it as they see fit, without them having to ask permission from or make additional payments to any external group or person. The word free in FOSS refers not to fiscal cost, but to the autonomy rights that FOSS grants its users. (A better word for zero-cost software, which lacks such rights, is "freeware.") The phrase open source emphasizes the right of users to study, change, and improve the source code—that is, the detailed design—of FOSS applications. Software that qualifies as free almost always also qualifies as open source, and vice versa, since both phrases derive from the same set of software user rights formulated in the late 1980s by Richard Stallman of the Free Software Foundation .

2. What is GPL Software?

The General Public License (GPL) is the original FOSS license, and GPL software is simply FOSS software that is covered by the GPL. The GPL was developed in the late 1980s by Richard Stallman as a way to convert his concept a software user’s Bill of Rights into a legally meaningful way to share and develop software. Since all FOSS originates directly or indirectly from Stallman’s original set of software user rights, the GPL tends to be the most accurate representation of the underlying principles of FOSS development.

The implications of this close link between the GPL and the underlying principles of FOSS can be seen in its overwhelming dominance among FOSS products. For example, over half of the software in the popular Red Hat Linux operating system is licensed under the GPL, and sites that support FOSS projects typically report that over 70% of their projects use the GPL. The results of the survey done for this report also support the dominance of the GPL, with 52% of the 115 identified applications being licensed wholly or predominantly under the GPL, and the next most popular type of license (BSD ) comprising a mere 6% of the total.

The most distinctive aspect of the GPL is its focus on the right of the software user to make autonomous decisions about how to use the software. GPL clauses ensure that individual users always retain the right to decide if, when, and how to use the software. For example, users always have the right to choose where and how to install GPL software, to analyze how it works, to change it, to decide if and when to release such changes, and even whether to sell original or modified GPL software at whatever price the market will bear. (Without the addition of distinguishing features or services, however, that market price will generally very low, since others can also sell or make copies of the same GPL software.) At no point in this process are GPL users required to ask for permission or guidance from outside entities or authorities, or to pay them additional fees, since the GPL itself provides all of the authorization required.

Another important and controversial Stallman innovation in the GPL was his use of transitive user rights to help ensure the rapid expansion of both the GPL user community and of the overall collection of GPL software. Transitive user rights mean that if anyone creates a new product that is based on the detailed design (source code) of an earlier GPL product, then they must provide any subsequent users of the new product with the same user rights that they had. In other words, the new work must also be placed under the GPL. Stallman realized that without this constraint the set of user rights provided by the GPL would evaporate over time as intermediate developers either neglected or explicitly chose not to convey the same level of autonomy to subsequent generations of users. Insisting on transitive user rights prevents this from happening, and ensures continued propagation of user rights. To balance the inclusive effect, however, Stallman made sure that it applied only when extensive, detailed use of the earlier GPL software was going on. It does not apply, for example, to those who are simply using (executing) GPL software, or to software that simply happens to exist on the same system as GPL software.

Stallman in effect postulated that if individual programmers were given the autonomy to use GPL fully, and that if such rights were always conveyed to all subsequent developers, the result would be explosive growth in both the number of participants and the capabilities of the resulting set of software. Stallman’s implicit postulate was largely validated over the course of the 1990s by the subsequent emergence of the World Wide Web, whose software components used and depended more upon GPL than on any other type of license. The full implications of Stallman’s work are yet to be seen, but via the Internet his principles have already had global consequences.

3. What is Open Source Software?

Open source software is FOSS that uses any license approved by the Open Source Initiative (OSI) in their convenient list of open source licenses . The OSI list is based on the open source definition , which in turn is heavily based on Stallman’s list of software user rights , but with the addition of several additional criteria intended to ensure fairness of the licenses. Both sets of criteria result in the selection of nearly identical sets of licenses, despite such differences.

4. Can FOSS Be Mixed with Proprietary Software?

A common assumption about FOSS licenses such as GPL is that their transitive user rights means they cannot be used with non-FOSS (e.g., government or proprietary) software. However, this is generally not the case; such mixing can generally be done in various ways. For example, even GPL with its strong protection of transitive user rights provides a number of mechanisms to allow such mixing (Figure 1). Microsoft provides a good example of an innovative use of one such mixing strategy in their Windows Services for Unix (SFU) product. This product uses proprietary software to build an initial bridge between Windows and UNIX operating systems, and then adds in GPL tools and utilities to extend greatly its overall emulation of UNIX. Users benefit from the extended functionality provided by the GPL components, while Microsoft benefits by avoiding the cost and time of re-developing the tools as proprietary software.

Figure 1 . Strategies for Mixing GPL and Proprietary Software

(a) Distribution Mixing – GPL and other software can be stored and transmitted together. Example: GPL software can be stored on the same computer disk as (most kinds of) proprietary software.

(b) Execution Mixing – GPL and other software can run at the same time on the same computer or network. Example: GPL and (unrelated) proprietary applications can be running at the same time on a desktop PC.

(c) Application Mixing – GPL can rely on other software to provide it with services, provided either that those services are either generic (e.g., operating system services) or have been explicitly exempted by the GPL software designer as non-GPL components. Examples include GPL applications running on proprietary operating systems or wrappers, and GPL applications that use proprietary components explicitly marked as non-GPL. Windows Services for UNIX 3.0 is a good example of commercial use of GPL application mixing.

(d) Service Mixing – GPL can provide generic services to other software. These services must be genuinely generic in the sense that the applications that use them must not depend on the detailed design of the GPL software to work. An example is linking a GPL utility to a proprietary software component by using the Unix "pipe" mechanism, which allows one-way flow of data to move between software components. This is the tightest form of mixing possible with GPL and other types of software, but it must be used with care to ensure that the GPL software remains generic and is not tightly bound to any one proprietary software component.

Note: GPL does not permit mixing of licenses when new software is directly derived from GPL source code;
such derived products must be licensed under GPL.

Since most FOSS licenses are similar in concept to the GPL, the mixing strategies listed in Figure 1 generally apply to other FOSS licenses as well. However, novel licenses should always be checked for unusual qualifiers or constraints. A number of FOSS licenses such as BSD provide additional ways to mix software types, such as through constrained direct integration of binary software into proprietary software.

5. Can FOSS Be Sold Commercially?

All of the major FOSS licenses, including GPL, permit commercial sale of FOSS software and products. The catch, however, is that since anyone can sell or copy the same software as you, the prices for FOSS products tend to be very low in the absence of other distinguishing features or services. In the late 1990s companies such as Red Hat and VA Software began to develop ways to provide commercial services in support of FOSS software products such as the Linux operating system. In the FOSS business model, such companies benefit from reduced long-term costs of supporting a large, complex code base, but they must also compensate for their loss of product uniqueness by stressing customer services and various forms of innovation in terms of new products and services. From a business support perspective the availability of companies that directly support FOSS products provides much the same kind of product and support continuity that organizations expect from proprietary software products.

6. How do FOSS Licenses Compare to Each Other?

As of mid 2002, nearly three dozen software licenses qualified as being open source , and thus FOSS, according to the defining criteria of the Open Source Initiative . In practice, however, only a small number of these licenses are widely used. Furthermore, less frequently used licenses are often based on or closely similar to more commonly used licenses. Table 1 summarizes a number of differences between four of the most important FOSS licenses. Additionally, the table includes the related concept of public domain software and an example of a proprietary software license that is notable for precluding the use of FOSS software.

Table 1 . A Comparison of FOSS and Related Licenses

License: Property			GPL	LGPL		BSD & MIT	Apache	Public Domain	Microsoft MIT4 EULA
a. Can be stored on disk with other license types			ü	ü		ü	ü	ü	(bans FOSS)5
b. Can be executed in parallel with other license types			ü	ü		ü	ü	ü	(bans FOSS)5
c. Can be executed on top of other license types			ü	ü		ü	ü	ü	(bans FOSS)5
d. Can be executed underneath other license types			ü 1	ü		ü	ü	ü	(bans FOSS)5
e. Source can be integrated with other license types				ü		ü	ü	ü	(bans FOSS)5
f. User decides if and when to publish derived code			ü 2	ü		ü	ü	ü	ü
g. Software can be sold for a profit			ü	ü		ü	ü	ü	ü
h. Binary code can be replicated by users as desired			ü	ü		ü	ü	ü
i. Binary code can be redistributed as desired			ü 3	ü		ü	ü	ü
j. Binary code can be used as desired by users			ü	ü		ü	ü	ü
k. New users always receive source code of derived works			ü	ü 6
l. New users receive full source modification rights for derived works			ü	ü 6
m. New users receive full redistribution rights for derived works			ü	ü 6
n. Binary code can be released without source code						ü	ü	ü	ü
o. Derived code can have a different type of license				7				ü
p. Original source can be incorporated into closed source products								ü
1 Provided that both programs are fully and independently usable in other unrelated contexts. 2 Provided that the binary code has not been previously released to the public. 3 Provided that source code is always redistributed along with the binary code. 4 The proprietary Microsoft MIT EULA is not related to the similarly named MIT (X/MIT) license. 5 Specifically bans use of: GPL, LGPL, Artistic, Perl, Mozilla, Netscape, Sun Community, and Sun Industry Standards. 6 The rights granted by LGPL do not necessarily extend to the applications linked into an LGPL library. 7 The LGPL does permit re-licensing under GPL as a special case, but not re-licensing under any other license type.
License Acronyms:
GPL –	GNU General Public License	(Microsoft) MIT –			Mobile Internet Toolkit
LGPL –	GNU Lesser General Public License	(X/MIT) MIT –			Massachusetts Institute of Technology
BSD –	Berkeley Software Distribution	EULA –			End-User License Agreement
MPL –	Mozilla Public License	FOSS –			Free and Open-Source Software

Properties (a) through (e) in the table examine the ability of a license to co-exist with other types of software, e.g., the ability of FOSS licenses to co-exist with proprietary software. In this category, the most exclusive license is easily the Microsoft MIT EULA license , which prohibits a number of FOSS licenses from co-existing on the same platform as the EULA software. No other FOSS or proprietary license encountered during the survey came close to this level of exclusivity. The GPL takes a very distant second place for exclusivity, since it forbids design-time incorporation of GPL source code into non-GPL source code. However, unlike the Microsoft MIT EULA, the GPL places no constraints on software simply running on the same system, and actually goes out of its way not to intrude on other licenses outside of that context. The GPL even allows non-GPL software to use GPL software as long as the two programs are not inextricably linked to each other (that is, they can both be used independently in other contexts). The GNU Lesser GPL (LGPL) is even more accommodating, allowing software to be directly incorporated into non-free software. The BSD and Apache license are still more accommodating by allowing distribution in binary form only. Finally, and not surprisingly, the most permissive category of all is public domain software, which allows essentially any use.

Properties (k) through (m) point out the flip side of the somewhat restrictive nature of the GPL: Its ability to ensure that later generations of users will inherit exactly the same rights to use, change, and redistribute GPL software as the first generation of users.

4. Overview of the DoD FOSS Survey

The data for the DoD FOSS survey was collected by email. The goal of the survey was to identify as complete a listing of the FOSS applications in use within the DoD as possible, and to document a diverse and representative set of examples of how these FOSS applications are being used. Over a two-week period the survey identified a total of 115 FOSS applications and 251 documented examples of how these applications are being used in the DoD. For purposes of completeness and comparison, a small number of cases were included in which the applications clearly do not meet FOSS criteria, but are related to FOSS in terms of availability of source code or use of FOSS-like processes for sharing work within limited communities. All such examples are noted as such, and should not be confused with applications that are unambiguously FOSS.

The set of 115 applications should include the majority of FOSS applications currently in use within the DoD, as judged by the increasing rate towards the end of the study at which new data points matched previously identified applications. The 251 examples of FOSS use are highly diverse both in terms of the DoD organizations represented and the types of applications. The set of examples likely includes most "big program" uses of FOSS, since explicit decisions to use FOSS in large programs generally led to multiple identifications of such programs in the survey responses. However, the examples clearly represent only the tip of an iceberg in terms the total number of facilities, operators, developers, researchers, and contractors using FOSS applications to support DoD work. For example, the GPL GCC compiler dominates C-language software development globally, and it has few competitors. This dominance makes it likely that the total instances of use of GCC by DoD software developers is hundreds or more likely thousands of times larger than the nine examples identified over the course of this short survey. The categories of FOSS applications that are most likely to have such large amplification factors are software development, web support, and network administration, which are all areas where FOSS applications are traditionally strong.

5. Survey Details

The detailed results of the survey are available in the form of a Sensitive But Unclassified (SBU) Appendix F. By placing this document and Appendix F in the same folder with the original filenames, Appendix F recipients can use hyperlinks from this document to access relevant data.

6. Analysis Approach

To help analyze the resulting data, the hypothetical question was posed of what would happen if FOSS software were banned in the DoD. Surprisingly, over the course of the analysis it was discovered that this hypothetical question has a real world analog in the form of proprietary licenses that if widely used would effectively ban most forms of FOSS . A corollary question is what the impact of banning the GPL alone would be, although many FOSS licenses are too much like GPL to make this distinction easy. The survey found that the GPL sufficiently dominates in DoD applications (Table 9) for a ban on GPL to closely approximate a full ban of all FOSS.

7. Summary of Results

The main conclusion of the analysis was that FOSS software plays a far more critical role in the DoD than has been generally recognized. The value of FOSS to the DoD appears to be greatest in four broad categories: Infrastructure Support , Software Development ,Security , and Research .

1. Infrastructure Support

While commercial equivalents Infrastructure FOSS applications are generally available, banning FOSS products would nonetheless result in a significant short-term cost spike as low-cost FOSS networking and web applications are replaced purchased proprietary equivalents. Ironically, there is no evidence that such a conversion would result in performance benefits. Since much of the infrastructure of the Internet was created under the FOSS model, its infrastructure applications such as Apache are generally older, more functionally mature, and less likely to fail than much more recent proprietary equivalents.

2. Software Development

A FOSS ban would have an especially negative impact on DoD software development. Development projects that use FOSS versions of the C and Ada programming languages would face costly translations to proprietary compilers and run time support packages. For the latter case of Internet-based languages such as Perl , recovery would be especially difficult since there are no immediately available commercial equivalents.

3. Security

One of the more unexpected results of the survey was the degree to which DoD security depends on FOSS applications and strategies. Banning FOSS in this area would have immediate, broad, and in some cases strongly negative impacts on the ability of the DoD to analyze and protect its own networks against hostile intrusion. This is in part because such a ban would prevent DoD groups from using the same analysis and network intrusion applications that hostile groups could use to stage cyberattacks. It would also remove the uniquely FOSS ability to change infrastructure source code rapidly in response to new modes of cyberattack. More interestingly, the GPL turns out to be surprisingly well suited to use in security environments because such environments include existing well-defined abilities to protect and control release of confidential information. This existing awareness largely removes the risk of premature release of GPL source code by developers, while maximizing the ability of those same developers to make effective use of the autonomy of decision provided by the GPL.

4. Research

DoD research would also be seriously damaged by a ban on FOSS. In this case, both cost and capabilities are important factors. Research efforts often use FOSS to extend limited budgets and allow them to focus more quickly on their research agendas. In terms of capabilities, FOSS provides resources such as mathematical software and the ability to link PCs into supercomputers for which there are no equivalent commercial alternatives. Finally, the FOSS method itself provides a form of "active publishing" that researchers use to share not just printed results, but software that can be immediately used to support further work.

2. Analysis of FOSS Survey Results
1. Types of DoD FOSS Users

The survey showed that the majority of DoD FOSS users are simply using the software without modifying the source, and in most cases without even looking at it. Such users are unaffected by the FOSS licenses of those applications. However, there are also cases where a project may choose to use FOSS licenses, or where the implications of the licenses need to be understood. The main categories of DoD FOSS users identified in the survey are described below.

1. Operational Users

As anticipated, the majority of the users in the survey only used their applications operationally – that is, without looking at or using the source code for them. Examples include using Linux, Apache, OpenBSD, and a variety of security applications.

2. Scripting and Basic Code Development Users

This category was also large. It includes using language and scripting applications such as Perl, GCC, bash, and JBoss to write simple scripts and code packages. Perl in particular was the single most widely used FOSS application in the survey. In terms of licensing, this category is similar to operational except for one difference: any libraries of parts that are used should be checked to make sure that they do not use licenses (e.g., the GPL) that would inadvertently require the new software to be FOSS also.

3. Advanced Code Development Users

This is a much smaller category that mostly includes cases where large, complex library routines (e.g., scientific and parallel processing routines) need to be incorporated into new software. While it may be worth doing this kind of work under a FOSS model, such decisions should not be made accidentally, but should be decided ahead of time.

4. FOSS Sponsors

Finally, the smallest group of DoD projects consisted of those that had explicitly decided to use a FOSS model to promote non-DoD development work on their project. The two main examples of this in the survey are SELinux (Secure Linux), which is a FOSS effort sponsored by the NSA, and CVW (Collaborative Virtual Workspace), which was initially developed by The MITRE Corporation for DoD use. While small numerically, this category is interesting because it demonstrates examples of the DoD and its associates using a FOSS model to help promote software advances in a larger overall community.

2. Observations

Some of the more surprising results of the data are given below.

1. FOSS Software is Vital to DoD Information Security

The survey identified 44 examples where organizations involved in DoD Security use FOSS software. The FOSS communities contribute to DoD security in two ways. Firstly, it has produced infrastructure software such as OpenBSD with low rates of software failure combined with early and rapid closure of security holes, which makes such systems useful as the security linchpins in broader security strategies. Secondly, the FOSS communities have had a long-term fascination with developing more and more sophisticated applications for identifying and analyzing security holes in networks and computers, resulting in FOSS products such as SARA and Snort that are invaluable to in-depth analyses of security risks.

The incentive for creating network analysis applications is different, but still deeply embedded in the psychology of FOSS development. In this case there is a strong competitive thread to FOSS developers that encourages them both to demonstrate flaws in the systems of others, while proving the reliability of their own systems. This gaming psychology tends to produce an "arms race" mentality in which both the strategies for analyzing weaknesses and the ability to defend against attacks are constantly improving.

Yet another important way in which FOSS contributes to security is by making it possible to change and fix security holes quickly in the face of new modes of cyberattack. This ability, which allows rapid response to new or innovative forms of cyberattack, is intrinsic to the FOSS approach and generally impractical in closed source products.

2. DoD Web Infrastructures Would Be Hit Hard

Infrastructure was the single largest category of DoD use of FOSS applications (see Table 3). This is in part because the Internet itself developed around a largely FOSS approach, with many of its most mature and widely used components (e.g., Apache ,Sendmail , or Qmail ) being FOSS. Consequently, it is difficult to construct an effective web or Intranet without relying on at least some minimal level of FOSS applications, as reflected by the large number of examples of FOSS infrastructure reliance identified by the survey. If rigorously enforced, a full ban on the use of FOSS web components within the DoD would result in at least a temporary shutdown of many or most of its web-based network and services. Even when commercial equivalents to FOSS web products are available, the relative immaturity of the commercial equivalents could increase risks for DoD infrastructures.

3. DoD Research Relies Heavily on FOSS for Synergy

For some components of the DoD research community, FOSS software acts as a sort of "active publication" medium in which important results are posted in the form of software and collectively improved by the entire community. This effect is especially strong in numeric processing and simulation, where FOSS products provides some of the best processing methods and software available anywhere. A ban on FOSS software here would both slow the exchange of ideas and make certain types of research (e.g., research based on supercomputer networks of low-cost PCs) impractical.

4. Cost Is Seldom the Only Reason for Choosing FOSS

More often than not, the strongest deciding factors for choosing FOSS products were capability and reliability, with cost being an important but secondary factor. In the small number of cases where groups chose to use FOSS software purely for cost reduction reasons, they were more likely to be disappointed by issues such as incompatibility with closed source systems that they were attempting to replace or complement.

5. Software Development Would Be Hit Hard

FOSS languages and applications such as GCC for the C language and GNAT for Ada have become so endemic in software development that a full, rigorously enforced ban on using FOSS could bring affected DoD software development projects to a halt. Such a ban would also remove a number of widely used program development applications such as CVS and GDB . The impact of a ban would be even more severe for development in languages such as Perl , which is a relatively recent language that has become an integral part of the Internet, and which is also widely to build "glue code" for integrating software applications. While commercial alternatives exist for older languages such as C and Ada, they are generally neither as mature or as portable across platforms as the FOSS equivalents. In the case of languages such as Perl that originated as FOSS, commercial alternatives do not exist, and applications would need to be translated into other languages.

3. An Analysis of Approaches to DoD FOSS Policy

In this section, a number of possible approaches to DoD FOSS policy are described and briefly analyzed for their likely consequences.

1. Approach #1: Ban All DoD Use of FOSS

The implementation of a DoD policy that bans any use of FOSS products would likely have interesting (and largely negative) short-term and long-term impacts on DoD cost, reliability, and capability. Figure 2 shows a notional estimate of such impacts on DoD FOSS users.

Figure 2 . Likely Impacts on Users of Banning FOSS



The short-term impacts would be the most serious. These impacts reflect both that the DoD already makes significant use of FOSS applications, and that a number of FOSS capabilities (particularly in the areas of high-end computing, security, and Internet-oriented software development) and security) are not readily available from closed-source COTS products. Short-term impacts on security would be especially bad due to the need to replace reliability- and security-focused systems such as OpenBSD with COTS systems that often have notable security and reliability issues . Over the long term, however, security would probably gradually improve as the closed-source COTS vendors continue to fix bugs and security flaws that were already absent from the FOSS products that they replaced.

Costs would also take a significant short-term hit as the low-cost and no-cost FOSS components are replaced with purchased proprietary products. Overall costs would then likely come down during an interim period. However, in the long term removing FOSS would remove an important source of price and quality competition. Without the constant pressure of low-cost, high-quality FOSS product competing with the closed-source products, the closed-source vendors could more easily fall into a cycle in which their support costs balloon and costs are passed on to their locked-in customers.

Capability would be negatively affected in both the short and long term, especially for high-end scientific and research computing that would lose resources such as libraries of high-quality mathematical software and support for high-end computing . Software development could become a difficult process, since the GCC family of compilers for C, C++, and other languages has become so prevalent that few similarly platform-independent alternatives exist. Development and support of Ada programs would be similarly affected, since the FOSS GNAT compiler dominates the Ada language in much the same way that GCC dominates C.

Ironically, a thoroughly rigorous and systematic ban on DoD use of FOSS could also affect a number of proprietary product that rely on FOSS products that permit incorporation of FOSS into their closed-source products. For example, Microsoft Office uses the FOSS zlib collection of data compression software, and thus could technically be banned as a product that incorporates FOSS software.

Finally, it should be noted simply using GPL software in combination with proprietary or closed-source government software does not have any affect the licensing of the non-GPL software. The GPL only requires that new source code that directly incorporates GPL software be made GPL, which is not the case for operational (e.g., infrastructure and security) use of GPL applications.

2. Approach #2: Limbo Status

At present, FOSS is neither approved nor disapproved in most parts of the DoD. This limbo status makes program, project, and developer decisions regarding FOSS difficult. Developers are often aware of the benefits of FOSS products for certain types of applications, but are unwilling to share that knowledge with their supervisors or commanding officers for fear that they will be told that they are using "unapproved" applications.

This de facto limbo-status policy of the DoD towards FOSS is unfortunate, since based on the way in which FOSS are being used, it is likely that the DoD would benefit from more use of FOSS rather than less. For example, although the FOSS Apache web server is mature, capable, and has an superior track record as measured the number of security holes on public tracking sites such as CERT , it is sometimes avoided on DoD sites simply because site administrators are unsure of its status. In such cases, a policy that explicitly permits the use of Apache would likely result in both improved overall reliability and lower costs for the DoD.

3. Approach #3: Selective FOSS Approvals

In this scenario, selected well-known and well-established FOSS products such as Apache, OpenBSD, GCC, GNAT, and Red Hat Linux would be selectively approved for DoD-wide use.

This approach would have immediate and largely beneficial effects, since many of these programs are already heavily in use in the DoD and have many users and supporters already in place. Approval would allow immediate broader use of such applications by users who for the most part will already be familiar with how to install and use them. Costs would drop in both the short and long term as more costly applications are replace by FOSS products such as Apache that are almost universally considered to be higher quality. Reliability and security would also improve, given that several of these well-known products already have established track records in these areas. Finally, capabilities would improve as the capabilities of these systems are distributed to more and more sites, and in some cases used to upgrade older systems. For example, Linux can often be used to increase the reliability and performance of older systems that are not capable of upgrading to new, much heavier-weight versions of Windows.

The main disadvantage of this approach would be that the selective approval process would likely overlook many of the smaller but highly important niche uses of FOSS, such as some of the security and numeric processing applications.

4. Approach #4: Security, Infrastructure, Research, and Development

This approach would provide DoD approval for using FOSS products in four general areas: Infrastructure Support, Software Development, Security, and Research. Rather than providing a fixed list, this approach would provide broad guidelines for selecting FOSS products in each of the areas, as well as specific lists of pre-approved products.

For Infrastructure Support , users would be able to select widely used and commercially supported FOSS applications such as Linux , Apache , OpenBSD , and other applications related to supporting the information infrastructure of an enterprise. A list of recommendations would be provided, but would not be exclusive. Groups would be able to choose other Infrastructure FOSS products if they meet the overall criteria for acceptable Infrastructure FOSS products. This category would never involve any kind of software development, and so would be unaffected by the special licenses of FOSS.

For Software Development , relevant FOSS applications such as Perl ,CVS , GCC , GNAT ,JBoss , Emacs , and others would be listed explicitly, and others allowed if they meet overall criteria for such applications. In contrast to Infrastructure and Security, users would be required to know and understand the particulars of the FOSS licenses of their applications, so that they are away of areas that could invoke FOSS licenses. For example, the LGPL license used with the C libraries of the GCC compiler does not involve FOSS licenses for any software developed, but there are other examples of C libraries that use GPL licenses that would affect software that uses them. Users of Development FOSS products should be aware in particular of the status of any library software that they use. Invoking a FOSS license could be done intentionally, such as to make better use of a community of like-minded developers outside of a government organization, but it should never be invoked accidentally (e.g., by not checking to see whether a library of components is under the LGPL or GPL).

An example of an area where explicit FOSS development policies would be useful is in the selection and use of FOSS software libraries. This need to be selected with some care, since for example libraries that use the GPL may require that software developed using those routines be GPL also. The GNU Scientific Library (GSL) , for example, contains many useful scientific routines, but was not used by any of the respondents. One respondent indicated that he had specifically avoided the GSL because of its use of GPL. While choosing to use GPL libraries may be appropriate if the goal is to contribute new features to a broader community, such libraries may be conversely be inappropriate when such release is not the desired goal.

For Security , users would similarly have a list of known, recognized products to use for non-development applications, plus guidelines for selecting other products. Guidelines for selecting Security FOSS products would be more stringent than for Infrastructure, since many security-related FOSS products could damage a system or network if used improperly.

Approval for Research use of FOSS would be similar to that for Development, but with more emphasis and leeway for sharing results and contributing to a community of developers. As with Development, though, software should not be made FOSS accidentally, but only by an explicit (and approved) decision to do so.

5. Approach #5: Advocating FOSS Products

There is a point of diminishing returns in all things, and in the case of FOSS, trying to force people to use FOSS products when it is not their own choice is likely well past that point. This is especially true since many of the highest quality FOSS products seem to show up in areas such as infrastructure, security, development, and research. All of these areas share the feature that they include people who are interested in pushing the limits of what they can do with a system or software, rather than simply using the software operationally. In contrast, desktop applications have tended to stay more stubbornly in the realm of closed-source COTS, at least for now.

In short, FOSS seems to work best when people come to it, and not vice-versa. In the study, one of the small number of negative reactions to using a FOSS product (GCC) came as a result of force-fitting it into a situation where compatibility with a closed source compiler was more important than the low cost of the GCC compiler. Anecdotal evidence tends to confirm the idea that using FOSS products only to "save money" is not necessarily a good idea , especially if the fit to the problem is not that good. Such products are best chosen because they have features that are desirable for how they will be used.

4. Conclusions

Based on the above analysis, the FOSS policy approach that appears most likely to benefit the DoD would be a combination of the third (selective approvals) and fourth (security, infrastructure, research, and development based) approaches. The resulting recommendation is summarized in the next and final section of this report.

3. Recommendations

Neither the survey nor the analysis supports the premise that banning or seriously restricting FOSS would benefit DoD security or defensive capabilities. To the contrary, the combination of an ambiguous status and largely ungrounded fears that it cannot be used with other types of software are keeping FOSS from reaching optimal levels of use. MITRE therefore recommends that the DoD take three policy-level actions to help promote optimum DoD use of FOSS:

1. Create a "Generally Recognized As Safe" FOSS list. This list would provide quick official recognition of FOSS applications that are (a) commercially supported, (b) widely used, and (c) have proven track records of security and reliability—e.g., as measured by speed of closures of CERT reports in comparison to closed-source alternatives. Initial applications for consideration would include, but not be limited to, the set of 115 already-used applications identified by the survey in Table 2, plus other widely used tools such as Python (http://www.python.org/ ) that did not appear in this first set of results. In formulating the list, quick consideration should be given in particular to high value, heavily used infrastructure and development tools such as Linux ,OpenBSD , NetBSD , FreeBSD , Samba , Apache , Perl , GCC ,GNAT , XFree86 , OpenSSH , bind , and sendmail .
2. Develop Generic, Infrastructure, Development, Security, & Research Policies. The DoD should develop generic policies both to promote broader and more effective use of FOSS, and to encourage the use of commercial products that work well with FOSS. A good example of the latter is the Microsoft Windows Services for UNIX product, which relies on FOSS (GPL ) software to reduce development costs and dramatically increase its power. A second layer of customized policies should be created to deal with major use areas. For Infrastructure and Development, these policies should focus on enabling easier use of GRAS products such as Apache, Linux, and GCC that are already in wide use, but which often suffer from an ambiguous approval status. For Security, use of GPL within groups with well-defined security boundaries should be encouraged to promote faster, more locally autonomous responses to cyber threats. Finally, for Research the policies should encourage appropriate use of FOSS both to share and publish basic research, and to encourage faster commercial innovation.
3. Encourage use of FOSS to promote product diversity. FOSS applications tend to be much lower in cost than their proprietary equivalents, yet they often provide high levels of functionality with good user acceptance. This makes them good candidates to provide product diversity in both the acquisition and architecture of DoD systems. Acquisition diversity reduces the cost and security risks of being fully dependent on a single software product, while architectural diversity lowers the risk of catastrophic cyber attacks based on automated exploitation of specific features or flaws of very widely deployed products.

1. Lists of Applications
1. Full List of FOSS Applications Used in the U.S. DoD

Table 2 lists the 115 FOSS applications identified by the survey. Note if you are looking at the electronic version of this document, you can use Table 2 as a quick index into the list of application descriptions (Table 7) by clicking on the name of an application.

Table 2 . Quick List of FOSS Software Used in the U.S. DoD

A	ACE	ACE ORB (TAO)	ACID	AMANDA	Apache	Autoconf	Automake
B	bash	Bastille	BIND
C	C++ Boost	CIS Benchmarks	Colt	Condor	COPS	Crack	CVS
	CVW	Cygwin
D	DDD	DjVuLibre
E	EADSIM	Emacs	eTrust	Expect
F	FreeBSD
G	GateD	gawk (awk)	GCC	GDB	Ghostscript	GNAT	GnuPG
	gnuplot	grep
H	h2n	HOSTS
I	ImageMagick
J	JADE	Jakarta	Jaxen	JBoss	JDOM	Jikes	jSIP
K	Kaffe
L	LaTeX	Linux	Linux (Red Hat)	Linux firewalls	Lsof
M	m4	Majordomo	make	Maxima	MIMEsweeper	MRTG	MTR
	MySQL
N	Nessus	NetBSD	NetSaint	nload	Nmap	ntop	NTP
O	Octave	OpenBSD	OpenMap	OpenOffice	OpenSSH	OpenSSL
P	Perl	Perl CGI scripts	PerLDAP	PHP	PingScan	Procmail
Q	Qmail
R	R	RealSecure	RRDtool	RTLinux	RWhois	RXVT
S	Samba	SARA	SATAN	Saxon	SCA	sed	SELinux
	Sendmail	SNARE	Snort	Squid
T	Tcl/Tk	TCP Wrappers	Tomcat	Top	Tripwire
U
V	VisAD	VOCAL	VTK
W	Webmin	WebTAS	Weka	WU-FTPD
X	Xalan	Xerces	XFree86	XGobi	Xpatch
Y
Z	zlib	Zope

2. 
   
3. Breakdown by Use

In this section, the 115 applications of the survey results were regrouped based on the (often multiple) ways in which they are being used. The result was four overlapping sets: Infrastructure Support (65 applications), Software Development (53 applications), Security (44 applications), and Research (21 applications).

1. Infrastructure Support Applications

Table 3 lists the 65 FOSS applications used in DoD infrastructure support. For online users of this document, this table is linked into the application description table (Table 7) and can be used as an index for perusing security-related FOSS applications. To return to this table instead of the main index after reading about an application, hold down Alt and press the left arrow key.

Note that although Security can be viewed as an aspect of Infrastructure Support, applications that were used only for security are listed separately in Table 5, rather than in this table. Some applications (e.g., NetSaint) are listed in both tables since they can support both ordinary network administration and security-oriented activities.

Table 3 . Infrastructure Support Applications

A	ACE	ACE ORB (TAO)	AMANDA	Apache
B	BIND
C	Condor	CVW	Cygwin
E	EADSIM	Emacs
F	FreeBSD
G	GateD	gawk (awk)	Ghostscript	GnuPG	grep
H	h2n
I	ImageMagick
J	Jaxen	JBoss	JDOM
L	LaTeX	Linux	Linux (Red Hat)	Linux firewalls	Lsof
M	Majordomo	MRTG	MTR	MySQL
N	NetSaint	nload	Nmap	ntop	NTP
O	OpenBSD	OpenMap	OpenOffice	OpenSSH	OpenSSL
P	Perl	Perl CGI scripts	PerLDAP	PHP	PingScan	Procmail
Q	Qmail
R	RRDtool	RTLinux	RWhois
S	Samba	SCA	sed	SELinux	Sendmail	Squid
T	Tomcat	Top
W	Webmin	WU-FTPD
X	Xalan	Xerces	XFree86
Z	zlib	Zope

 

2. Software Development Applications

Table 4 lists the 53 FOSS applications used in DoD software development. For online users of this document, this table is linked into the application description table (Table 7) and can be used as an index for perusing security-related FOSS applications. To return to this table instead of the main index after reading about an application, hold down Alt and press the left arrow key.

Table 4 . Software Development Applications

A	ACE	ACE ORB (TAO)	Autoconf	Automake
B	bash
C	C++ Boost	CVS	Cygwin
D	DDD	DjVuLibre
E	Emacs	Expect
F	FreeBSD
G	GateD	GCC	GDB	GNAT	GnuPG
H	h2n
I	ImageMagick
J	JADE	Jakarta	Jaxen	JBoss	JDOM	Jikes	jSIP
K	Kaffe
L	LaTeX	Linux
M	m4	make	MySQL
N	NetBSD
O	OpenMap	OpenSSH
P	Perl	PHP
R	RTLinux	RXVT
S	Saxon	SCA
T	Tcl/Tk	Tomcat
V	VOCAL	VTK
W	WU-FTPD
X	Xalan	Xerces	XFree86
Z	zlib	Zope

 

3. Security Applications

Table 5 lists the 44 FOSS applications used in DoD security applications. For online users of this document, this table is linked into the application description table (Table 7) and can be used as an index for perusing security-related FOSS applications. To return to this table instead of the main index after reading about an application, hold down Alt and press the left arrow key.

Table 5 . Security Applications

A	ACID
B	Bastille
C	CIS Benchmarks	COPS	Crack
E	eTrust	Expect
F	FreeBSD
G	GCC	GnuPG
H	HOSTS
L	Linux	Linux (Red Hat)	Linux firewalls	Lsof
M	MIMEsweeper	MRTG	MTR	MySQL
N	Nessus	NetSaint	nload	Nmap	ntop
O	OpenBSD	OpenSSH	OpenSSL
P	Perl	Perl CGI scripts	PerLDAP	PHP
Q	Qmail
R	RealSecure	RRDtool
S	SARA	SATAN	SELinux	SNARE	Snort	Squid
T	Tcl/Tk	TCP Wrappers	Tripwire
W	Webmin

 

4. Research Applications

Table 6 lists the 21 FOSS applications used in DoD research. For online users of this document, this table is linked into the application description table (Table 7) and can be used as an index for perusing security-related FOSS applications. To return to this table instead of the main index after reading about an application, hold down Alt and press the left arrow key.

Table 6 . Research Applications

A	ACE ORB (TAO)
C	Colt		Condor	CVW
E	EADSIM
G	GateD		gnuplot
J	JADE		Jikes	jSIP
L	Linux
M	Maxima
O	Octave
R	R
S	SCA
V	VisAD		VOCAL	VTK
W	Weka
X	XGobi		Xpatch

2. Application Descriptions
1. Application Descriptions

Table 7 describes the applications, provides references for finding them on the Internet, and lists the 251 identified instances of DoD use of the applications, including email contact points for each instance. The applications are organized alphabetically by FOSS application. The application descriptions include links back to the main index table (Table 2) to make rapid browsing easier. The information in this table was last updated on August 7, 2002.

Table 7 . FOSS Software Used in the U.S. DoD

Application	Description	License	References
ACE (1 example)	ACE = ADAPTIVE Communication Environment. ACE is a toolkit for creating software to perform common cross-platform network communication tasks. ACE helps create software for demultiplexing, event handler dispatching, signal handling, service initialization, interprocess communication, message routing, dynamic reconfiguration of distributed services, shared memory management, concurrent execution, and process synchronization. The TAO real-time CORBA ORB is a major component of ACE.	ACE/TAO	http://www.cs.wustl.edu/~schmidt/ACE-overview.html http://www.riverace.com/ http://www.theaceorb.com/product/aboutace.html
ACE ORB (TAO) (3 examples)	TAO is a standards-based (CORBA) "Object Request Broker" (ORB) that allows programs located on many networked computers to work together securely and in real-time.	ACE/TAO	http://www.cs.wustl.edu/~schmidt/TAO.html http://www.theaceorb.com/
ACID (1 example)	ACID = Analysis Console for Intrusion Databases. ACID is a PHP-based analysis engine used to search and process databases of security events generated by various intrusion detection systems, firewalls, and network monitoring tools.	GPL	http://www.cert.org/kb/acid/
AMANDA (1 example)	AMANDA = Advanced Maryland Automatic Network Disk Archiver. AMANDA allows a single master backup server to back up large sets of workstations running multiple versions of Unix. AMANDA can also use SAMBA to back up Microsoft Windows 95/NT systems.	BSD	http://www.amanda.org/
Apache (22 examples)	A web server is the software that presents web pages to Internet users. Apache is easily the most popular and widely used web server (open or closed source) on the Internet. It is popular for its reliability, security, range of features, and low cost.	Apache	http://www.apache.org/
Autoconf (1 example)	Autoconf adapts software source code to many kinds of Unix-like systems without manual user intervention.	GPL	http://www.gnu.org/software/autoconf/
Automake (1 example)	For software development, Automake generates Makefiles that are compliant with GNU coding standards.	GPL	http://sources.redhat.com/automake/
bash (2 examples)	The default command line interface for Linux. It is used both to create scripts (high level programs), and to interact directly with the operating system.	GPL	http://www.gnu.org/software/bash/bash.html
Bastille (1 example)	The Bastille Hardening System is a package of adjunct software that can be used to "harden" the Linux operating system. The goal of Bastille is to provide the greatest possible security while keeping the system easy to use. Bastille currently supports the Red Hat and Mandrake Linux distributions, and in late 2002 to early 2003 is also expected to support the Debian, SuSE, and TurboLinux distributions of Linux. Support for the proprietary HP-UX operating system is also planned.	GPL	http://www.bastille-linux.org/ http://sourceforge.net/projects/bastille-linux/
BIND (3 examples)	BIND = Berkeley Internet Name Domain. It is BIND that allows easy-to-use URL text names (e.g., place.com) to be used to identify web sites, instead of the long numeric addresses that the Internet itself uses. Nearly all systems and commercial software that connect to the Internet use BIND.	ISC	http://www.isc.org/products/BIND/
C++ Boost (1 example)	C++ Boost is a web site that provides a broad range of free, portable, high-quality, peer-reviewed C++ source libraries. The site emphasizes compatibility with the C++ Standard Library, and holds many candidates for eventual inclusion in than library.	C++ Boost	http://www.boost.org/
CIS Benchmarks (1 example)	CIS = Center for Internet Security. The CIS Benchmarks are a set of documents that specify in detail how to configure common operating systems for maximum security. An associated collection of freeware Scoring Tools provide automated checks of how closely a given system comes to meeting the Benchmark specifications. The Benchmarks documents are developed and maintained using an easily-to-join community-style (limited FOSS) development process. However, the associated scoring tools are zero-cost freeware, not FOSS, and are provided in binary form only (no source code). (See the HOSTS tool for a FOSS analog to the CIS Scoring Tools.)	Community (CIS)	http://www.cisecurity.org/
Colt (1 example)	Colt is a free collection of high-quality scientific and mathematical software written in Java. It includes software for efficient data structures, data analysis, linear algebra, multi-dimensional arrays, histoprogramming, Monte Carlo simulation, and parallel and concurrent programming. Colt serves as a constantly evolving repository for some of the best concepts and designs for such software.	Colt	http://tilde-hoschek.home.cern.ch/~hoschek/colt/
Condor (1 example)	Condor is a computing environment that allows scientists and engineers to harness the capacity of large collections of distributed Unix systems (workstations and PCs running Linux or BSD) to solve processing-intensive problems. Future versions may also work with Windows.	GPL	http://www.cs.wisc.edu/condor/
COPS (1 example)	COPS = Computer Oracle and Password System. COPS analyzes Unix-like systems for weaknesses.	GPL	http://www.tripwire.org/qanda/faq.php
Crack (3 examples)	Crack is used by network admins to verify the quality of user passwords by attempting to break or "crack" those passwords.	Artistic	http://www.uazone.org/demch/analysis/sec-inchtools.html#5.2
CVS (3 examples)	CVS = Concurrent Versions System. CVS is a popular system for helping software development projects keep track of the history and any multiple versions of the source code they develop. CVS can be used in a wide range of project sizes.	GPL	http://www.cvshome.org/
CVW (3 examples)	Originally developed by MITRE and later released as FOSS. Used by over 5000 people for collaboration. Currently being phased out at NSA in favor of the commercial InfoWorkSpace product from ezenia!, as per directions by Congress and the DoD. The InfoWorkSpace product includes elements of the CVW design.	MITRE	http://cvw.sourceforge.net/
Cygwin (2 examples)	A surprisingly complete Linux-like emulation of Unix and the Unix tool set for use on Windows systems. Cygwin provides access to useful Unix tools and capabilities without requiring users to restart their systems or go to another computer.	GPL	http://www.cygwin.com/
DDD (1 example)	GNU DDD is a graphical front-end for debugging tools. It is noted for its ability to display debugging data in a convenient chart format.	GPL	http://www.gnu.org/software/ddd/
DjVuLibre (1 example)	DjVuLibre provides efficient distribution and display of images in a variety of compressed formats.	GPL	http://djvu.sourceforge.net/
EADSIM (1 example)	EADSIM = Extended Air Defense Simulation. Combat developers, materiel developers, and operational commanders use EADSIM simulations to assess the effectiveness of Theater Missile Defense (TMD) and air defense systems against a full spectrum of extended air defense threats. It is provided without charge under a restricted community (versus FOSS) license.	Community (EADSIM)	http://www.eadsim.com/EADSIMBrochure.html
Emacs (6 examples)	A full-functioned and popular editing tool that is especially useful for creating software. There are multiple "families" of Emacs, such as GNU Emacs and X-Emacs, for use in different environments. Emacs also supports language-specific extensions that are widely used for development in languages such as Java and C.	GPL	http://www.gnu.org/software/emacs/emacs.html
eTrust (1 example)	eTrust is a closed source network security evaluation and monitoring tool with FOSS (OpenSSL toolkit) origins.	Closed from open (eTrust)	http://www3.ca.com/Solutions/Solution.asp?ID=271
Expect (1 example)	Expect is a system admin and user tool for automating and testing interactive Unix applications such as telnet, ftp, passwd, fsck, and rlogin. It can be used to greatly simplify and automate tasks that would be prohibitively time consuming and costly if done interactively by people.	Public Domain (Expect)	http://expect.nist.gov/
FreeBSD (3 examples)	The Unix-like operating BSD operating systems are FOSS competitors to Linux, and are notable for having generally higher levels of reliability and security. OpenBSD, NetBSD, and FreeBSD are best known. FreeBSD is notable for being highly efficient when used on PC (Pentium) computers.	BSD	http://www.freebsd.org/ http://www.daemonnews.org/199904/editorial.html http://www.openbsd.org/ http://www.netbsd.org/
GateD (1 example)	GateD provides network routing services, a routing database, and support for a variety of routing protocols.	Closed from open (GateD)	http://www.nexthop.com/products/gated.shtml (current closed version) http://www.merit.edu/internet/net-research/idrp/mitre/doc/gated_doc/main.html (earlier FOSS version)
gawk (awk) (2 examples)	gawk = GNU awk (Aho, Weinberger, Kernighan - the authors of awk). Gawk is the GNU version of the awk file transformation language. Awk is an interpreted C-like language with strong pattern matching and capabilities, making it useful for writing quick programs to make minor transformations on files. For larger or more frequently used file transformations, Perl is usually a better choice than gawk, since the more recent Perl provides similar capabilities plus a number of advanced features.	GPL	http://www.gnu.org/software/gawk/gawk.html
GCC (9 examples)	GCC = GNU Compiler Collection (formerly GNU C Compiler). GCC is a suite of compilers that includes C, C++, Objective C, Chill, Fortran, Java, and (in the next release) GNAT Ada. The original GNU C compiler dominates the C software development market.	GPL	http://gcc.gnu.org/
GDB (1 example)	GDB = GNU Project Debugger. GDB, the GNU Project debugger, allows you to see what is going on inside another program while it executes, or what another program was doing at the moment it crashed. GDB can be used to start your program with any options you want, stop your program when specified conditions occur, examine the state of your program after stopping it, and change your program temporarily to examine the effects of possible fixes.	GPL	http://sources.redhat.com/gdb/
Ghostscript (2 examples)	Ghostscript, along with its associated graphical interface tools Ghostview and GSview, provides viewing of postscript and PDF documents.	AFPL	http://www.cs.wisc.edu/~ghost/
GNAT (9 examples)	GNAT is a FOSS implementation of Ada 95. Commercial versions of GNAT (GNAT Pro Ada 95) and support are provided by Ada Core Technologies, and fully FOSS (GPL) versions are also available. A GNAT Ada front-end will also be added to GCC in GCC 3.1.	GPL	http://www.gnat.com/ ftp://cs.nyu.edu/pub/gnat/ http://gcc.gnu.org/
GnuPG (1 example)	GnuPG stands for GNU Privacy Guard and is GNU's tool for secure communication and data storage. GnuPG is a complete and free replacement for PGP. It can be used to encrypt data and to create digital signatures, and it includes an advanced key management facility. Because it does not use the patented IDEA algorithm, it can be used without any restrictions. GnuPG is a RFC2440 (OpenPGP) compliant application, providing compatibility with PGP from NAI Inc.	GPL	http://www.gnupg.org/
gnuplot (3 examples)	gnuplot is a command-driven interactive function plotting program that can be used to plot functions and data points in two or three dimensions and many different formats. It is free, but not GPL, despite its name.	Gnuplot	http://www.gnuplot.info/
grep (1 example)	GNU grep can be used to search text files or text streams for lines that match simple or complex patterns.	GPL	http://www.gnu.org/software/grep/grep.html
h2n (1 example)	h2n converts a table of host computers into a form usable as Internet (DNS) names.	GPL	http://www.crihan.fr/system/linux/maint/bind/old/h2n-man.html
HOSTS (1 example)	HOSTS = Host-Oriented Security Test Suite. Provides greater consistency and repeatability in security testing of Unix and Unix-like operating systems by automating many aspects of the testing process.	GPL	http://www.openchannelfoundation.org/projects/HOSTS
ImageMagick (1 example)	ImageMagick provides display and conversion of images in about 70 major formats.	ImageMagick	http://www.imagemagick.org/
JADE (1 example)	JADE = Java Agent DEvelopment framework. JADE provides Java middleware for creating "multi-agent" software that on multiple networked machines. JADE implements FIPA agent communication standards.	LGPL	http://sharon.cselt.it/projects/jade/
Jakarta (1 example)	Jakarta is a web site that provides FOSS Java solutions for a wide range of applications and problems.	Apache	http://jakarta.apache.org/
Jaxen (1 example)	Jaxen = Java XPath Engine. Jaxen is a Java and XML development tool that interprets XPath expressions for multiple XML models, including DOM, dom4j, EXML, and JDOM.	Apache	http://jaxen.org/
JBoss (1 example)	JBoss is a J2EE-compliant web application server that provides middleware capabilities (EJB and JMS), database connectivity (JDBC), transactions (JTA/JTS), presentation (servlets and Java Server Pages), and directory services (JNDI). In March 2002, Sun Microsystems expressed stronger support for getting the popular JBoss package Java certified.	LGPL	http://jboss.org/
JDOM (1 example)	JDOM provides a fast, easy-to-read way to represent XML documents in Java. (JDOM is a name, not an acronym.)	GPL	http://www.jdom.org/
Jikes (1 example)	Jikes is a FOSS compiler for Java.	IPL	http://oss.software.ibm.com/developerworks/opensource/jikes/
jSIP (1 example)	jSIP = Java Session Initiation Protocol. The jSIP library provides text-based collaboration by users, including Instant Messaging.	GPL	http://jsip.sourceforge.net/
Kaffe (1 example)	Kaffe is a FOSS implementation of the Java Virtual Machine (JVM), which is the software that interprets Java software. (Sun JVMs are free but not FOSS.)	GPL	http://www.kaffe.org/
LaTeX (2 examples)	LaTeX (pronounced "lay-tek") is a high-quality typesetting system, with features designed for the production of technical and scientific documentation. It is the de facto standard for writing and publishing scientific documents.	LaTeX	http://www.latex-project.org/
Linux (19 examples)	Linux is a popular Unix-like FOSS operating system. It contains hundreds of individual tools, and has more commercial and applications support than any other FOSS operating system.	GPL	http://www.linux.org/
Linux (Red Hat) (3 examples)	Red Hat is the most popular commercial source for the Linux operating system.	GPL	http://www.redhat.com/
Linux firewalls (1 example)	Linux provides a variety of tools for creating firewalls.	GPL	http://www.linuxjournal.com/article.php?sid=1212 http://www.linuxdoc.org/HOWTO/Firewall-HOWTO.html
Lsof (1 example)	Lsof = List Open Files. Lsof lists any currently open files or process communications.	Lsof	http://freshmeat.net/projects/lsof/
m4 (1 example)	GNU m4 is a "macro expander" that can be used to create large sets of source code (such as web pages) with a shared format or visual look and feel.	GPL	http://www.gnu.org/software/m4/
Majordomo (1 example)	Majordomo automates management of Internet mailing lists. Once a list is set up, nearly all operations can be performed remotely by email. A graphical user interface called MajorCool is also available.	GPL	http://www.greatcircle.com/majordomo/
make (2 examples)	The GNU make utility automatically determines which pieces of a large program need to be recompiled, and issues the commands to recompile them.	GPL	http://www.gnu.org/manual/make-3.79.1/html_node/make_toc.html
Maxima (1 example)	Maxima is a Common Lisp implementation of MIT's Macsyma system for computer based algebra.	GPL	http://www.ma.utexas.edu/users/wfs/maxima.html
MIMEsweeper (1 example)	MIMEsweeper is a closed source product with FOSS origins. It looks for suspicious patterns in the actual content of emails and communications to help identify suspicious activities.	Closed from open (MIMEsweeper)	http://www.mimesweeper.com/default.asp
MRTG (3 examples)	MRTG = Multi Router Traffic Grapher. MRTG provides monitoring of traffic load on network links, and shows the live status graphically using HTML images that can be viewed over the Internet.	GPL	http://people.ee.ethz.ch/~oetiker/webtools/mrtg/mrtg.html
MTR (1 example)	MTR determines whether a network computer is available, and the overall quality of the link to it.	GPL	http://www.bitwizard.nl/mtr/
MySQL (4 example)	MySQL is the world's most popular FOSS database. It is fast, full-functioned, and precise enough to be used in both heavy load and mission critical applications.	GPL	http://www.mysql.com/
Nessus (3 examples)	An easy-to-use, full-functioned, and up-to-date remote security scanner.	GPL	http://www.nessus.org/
NetBSD (1 example)	The Unix-like operating BSD operating systems are FOSS competitors to Linux, and are notable for having generally higher levels of reliability and security. OpenBSD, NetBSD, and FreeBSD are best known. NetBSD is notable for being highly portable across a wide range of computer platforms.	BSD	http://www.netbsd.org/ http://www.daemonnews.org/199904/editorial.html http://www.openbsd.org/ http://www.freebsd.org/
NetSaint (1 example)	NetSaint monitors network Linux hosts services and can alert administrators of problems via email when a problem arises.	GPL	http://www.netsaint.org/
nload (1 example)	nload monitors and graphically displays real-time network traffic and usage.	GPL	http://www.roland-riegel.de/nload/index_en.html
Nmap (2 examples)	Nmap scans networks and maps out their configurations.	GPL	http://www.insecure.org/nmap/
ntop (2 examples)	ntop is a Unix tool that shows the heaviest users of network resources in ranked order, making it easy to see hot spots or anomalous usage.	GPL	http://www.ntop.org/ntop.html
NTP (1 example)	NTP = Network Time Protocol. NTP software provides the ability to synchronize in network computer clocks precisely.	GPL	http://www.eecis.udel.edu/~ntp/ http://www.eecis.udel.edu/~mills/ntp.htm http://www.eecis.udel.edu/~ntp/ntp_spool/html/ntpd.htm
Octave (1 example)	GNU Octave is a high-level language, primarily intended for numerical computations. It provides a convenient command line interface for solving linear and nonlinear problems numerically, and for performing other numerical experiments using a language that is mostly compatible with MATLAB. It may also be used as a batch-oriented language.	GPL	http://www.octave.org/
OpenBSD (1 example)	The Unix-like operating BSD operating systems are FOSS competitors to Linux, and are notable for having generally higher levels of reliability and security. OpenBSD, NetBSD, and FreeBSD are best known. OpenBSD is notable for its high security, support for encryption, and an exceptionally rigorous self-auditing process. OpenBSD has been particularly successful at avoiding the kinds of default security holes commonly encountered when installing most operating systems.	BSD	http://www.openbsd.org/ http://www.daemonnews.org/199904/editorial.html http://www.freebsd.org/ http://www.netbsd.org/
OpenMap (2 examples)	OpenMap is JavaBeans-based programmer's toolkit that allows Java application to access map data from older databases and formats.	OpenMAP	http://openmap.bbn.com/
OpenOffice (1 example)	OpenOffice is a suite of business office support programs comparable to Microsoft Office, but based on the open and easily exchanged XML format. OpenOffice began as a free but closed-source system called StarOffice, which was bought by Sun Microsystems, who eventually made it fully FOSS. As of early 2002, OpenOffice was still undergoing the transition from closed to FOSS.	GPL	http://www.openoffice.org/
OpenSSH (1 example)	OpenSSH = Open Secured Shell. OpenSSH provides secure (encrypted) access to remote network computers.	BSD	http://www.openssh.com/
OpenSSL (1 example)	OpenSSL is a FOSS implementation of the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols for secure communications over the Internet. It includes a full-strength, general-purpose library of cryptography software.	OpenSSL	http://www.openssl.org/
Perl (25 examples)	Perl = Practical Extraction and Reporting Language. A popular, functionally rich Internet language that is used in a wide range of applications that include extracting data from text, reformatting documents, and integrating software components.	GPL	http://www.perl.org/
Perl CGI scripts (1 example)	Perl scripts provide numerous functions to support web sites, including various types of search.	GPL	http://www.scriptsearch.com/Perl/Scripts_and_Programs/ http://awsd.com/scripts/
PerLDAP (2 examples)	The Lightweight Directory Access Protocol (LDAP) is a protocol for accessing online directory services. PerLDAP is a Perl implementation of it.	GPL	http://www.perldap.org/
PHP (4 examples)	PHP = PHP Hypertext Preprocessor. PHP allows web pages to interact with users (e.g., to accept and display form data).	PHP	http://www.php.net/
PingScan (1 example)	PingScan scans networks to find all accessible systems.	GPL	http://www.linux.org/apps/AppId_1996.html
Procmail (1 example)	Procmail supports lists and automated pre-processing of email, such as sorting, selecting, and re-routing emails based on various criteria and conditions.	GPL	http://www.procmail.org/
Qmail (1 example)	Qmail is a FOSS replacement for Sendmail, the program that transfers emails between computers on the Internet. Qmail has improved security, reliability, and performance features.	Qmail	http://qmail.goof.com/top.html
R (1 example)	R is a language and environment for statistical computing and graphics. It provides a wide variety of statistical and graphical techniques such as linear and nonlinear modeling, statistical tests, time series analysis, classification, and clustering. It is also known as GNU S, a reference both to its use of the GPL and its similarity to the S statistical language.	GPL	http://www.r-project.org/
RealSecure (1 example)	RealSecure is a closed source intrusion detection product with FOSS origins.	Closed from open (RealSecure)	http://www.iss.net/products_services/enterprise_protection/rsnetwork/index.php
RRDtool (2 examples)	RRDtool = Round Robin Database tool. RRDtool provides efficient collection of network usage data over extended periods of time.	GPL	http://people.ee.ethz.ch/~oetiker/webtools/rrdtool/
RTLinux (1 example)	RTLinux allows Linux and BSD operating systems to respond reliably to time-critical applications such as embedded device control, instrumentation, and certain types of communications.	RTLinux	http://www.fsmlabs.com/community/
RWhois (1 example)	RWhois provides improved administrative identification of users on a network.	GPL	http://www.rwhois.net/
RXVT (1 example)	A smaller, more compact way to interact via command lines with programs.	GPL	http://www.rxvt.org/ http://www.math.fu-berlin.de/~guckes/rxvt/#intro
Samba (3 examples)	Samba is a popular tool that allows Linux and BSD (OpenBSD, NetBSD, and FreeBSD) operating systems to provide invisibly the same file and printer services as Windows servers. Since the Linux and BSD operating systems were generally more stable than early Windows NT servers, administrators often invisibly converted Windows servers to Linux-plus-Samba to improve network reliability.	GPL	http://us1.samba.org/samba/samba.html
SARA (1 example)	SARA = Security Auditor's Research Assistant. SARA is a third generation Unix security analysis tool that is based on the SATAN model.	SATAN	http://www-arc.com/sara/
SATAN (2 examples)	SATAN = Security Administrator Tool for Analyzing Networks. It is a first generation Unix security analysis tool that collects data on networked hosts.	SATAN	http://www.uazone.org/demch/analysis/sec-inchtools.html#5.1
Saxon (1 example)	SAXON provides tools for processing XML. (XML is the successor to the HTML used in most Internet web pages.) It includes an XML standards-compliant XSLT processor, plus and a number of useful extensions, such as a Java library that provides XSL-like processing.	MPL	http://saxon.sourceforge.net/
SCA (1 example)	SCA = Software Communications Architecture. This web site provides standards for writing code for software-defined radio applications. This is an early effort to promote sharing by providing an overall standards framework through which contributed software can work and interoperate.	Community (SCA)	http://www.jtrs.saalt.army.mil/docs/documents/sca.html
sed (2 examples)	sed = Stream Editor. GNU sed can be used to extract or transform text in very large files, or in incoming or outgoing streams of text data of indefinite length. Perl and awk (gawk) both provide more functionality, but for simple filtering and conversions, sed is both fast and easy to use.	GPL	http://www.gnu.org/software/sed/sed.html http://www.dreamwvr.com/sed-info/sed-faq.html
SELinux (2 examples)	SELinux = Security Enhanced Linux, a set of Linux enhancements developed specifically by NSA to make Linux usable in a broader range of government and industry applications. (Note: In contrast, NSA Signal Intelligence prohibits use of Linux.)	GPL	http://www.nsa.gov/selinux/
Sendmail (1 example)	Sendmail takes care of the actual transfer of email messages between Internet computers. Sendmail is the most widely used such program on the Internet. Qmail provides a more security-focused FOSS alternative.	Sendmail	http://www.sendmail.org/
SNARE (1 example)	SNARE = System iNtrusion Analysis and Reporting Environment). An auditing and intrusion detection module that can be attached directly to the Linux kernel.	GPL	http://www.intersectalliance.com/projects/Snare/
Snort (3 examples)	Snort is a multi-platform, lightweight, rule-based tool for detecting hostile intrusions into a network. It works well on small networks, and can be deployed quickly to help fill in network security holes when new attacks emerge.	GPL	http://www.snort.org/ http://www.snort.org/docs/lisapaper.txt
Squid (1 example)	Squid improves web performance for Unix and Unix-like systems by invisibly providing local copies (caching) of frequently used files and information from remote parts of the web. It supports full-featured proxying (that is, invisible replacement of requests for files from remote sites with copies of the same information previously stored locally) and caching for most of the major web protocols and formats, including HTTP, FTP, and web site names (URLs), and also proxying for SSL.	GPL	http://www.squid-cache.org/
Tcl/Tk (1 example)	Tcl is a scripting language for controlling computer devices, and Tk is a library for creating graphical interfaces to those parts.	BSD	http://www.tcl.tk/
TCP Wrappers (2 examples)	Provides monitoring and filtering of incoming requests for network services, including sysstat, finger, ftp, telnet, rlogin, rsh, exec, tftp, and talk.	TCP Wrappers	ftp://ftp.porcupine.org/pub/security/tcp_wrappers_7.6.BLURB ftp://ftp.porcupine.org/pub/security/index.html
Tomcat (1 example)	Tomcat is a FOSS implementation of the official "servlet container" for Java Servlets and JavaServer Pages.	Apache	http://jakarta.apache.org/tomcat/index.html
Top (1 example)	Top is a standard Unix (Linux and BSD) tool for determining which processes are consuming the most processing resources.	GPL	http://www.tac.eu.org/cgi-bin/man-cgi?top+1
Tripwire (2 examples)	Tripwire monitors key attributes of files that should not change and provides alerts when they do change.	GPL	http://www.tripwire.org/qanda/faq.php
VisAD (1 example)	VisAD = Visualization for Algorithm Development. VisAD is a Java library for interactive and collaborative visualization and analysis of numerical data.	LGPL	http://www.ssec.wisc.edu/~billh/visad.html
VOCAL (1 example)	VOCAL = Vovida Open Communication Application Library. VOCAL provides tools and software for building advanced Internet telephony (VoIP) applications.	Vovida	http://www.vovida.org/applications/downloads/vocal/home.html
VTK (1 example)	VTK = Visualization Toolkit. VTK provides 3D computer graphics, image processing, and visualization. It has interfaces to most of the major Internet computer languages, and is used by thousands of researchers and developers around the world.	VTK	http://public.kitware.com/VTK/
Webmin (1 example)	Webmin makes it possible to do web-based remote or local system administration of Unix and Unix-like systems. Using any browser that supports tables and forms (and Java for the File Manager module), you can setup user accounts, Apache, DNS, file sharing, and other common system admin tasks. The web server part of Webmin is written in Perl, using only standard Perl modules.	BSD	http://www.webmin.com/
WebTAS (1 example)	WebTAS = Web-enabled Timeline Analysis System. WebTAS provides tools for analyzing data and looking for suspicious patterns in the data of both large and small organizations, particularly law enforcement and security agencies. It is free under a limited access (community) license.	Community (WebTAS)	http://www.webtas.com/ http://iswsolutions.com/webtas.shtml
Weka (1 example)	Weka is a collection of machine learning algorithms for solving real-world data mining problems. It is written in Java and runs on almost any platform.	GPL	http://www.cs.waikato.ac.nz/~ml/weka/
WU-FTPD (1 example)	WU-FTPD provides the ability to transfer files easily ("FTP") between computers on the Internet. It is the most widely used program for providing FTP capabilities.	WU-FTPD	http://www.wu-ftpd.org/
Xalan (1 example)	Xalan-Java and Xalan-C++ are XSLT-based tools for converting XML documents into HTML, text, or other XML document types.	Apache	http://xml.apache.org/xalan-j/ http://www.garshol.priv.no/download/xmltools/prod/Xalan-C.html
Xerces (3 examples)	Xerces interprets (parses) XML, which is the successor to HTML. Xerces is available for Java, C++, and Windows.	Apache	http://xml.apache.org/
XFree86 (1 example)	XFree86 is a FOSS version of the X windowing system used in most Unix-like systems, including Linux and the BSD operating systems. It provides easy-to-use, PC-like graphical displays and controls for computer users.	Xfree86	http://www.xfree86.org/
XGobi (1 example)	XGobi is a data visualization system for viewing high-dimensional data. The most recent version is called GGobi. GGobi components include four FOSS licenses: AT&T Open Source License , GPL , BSD , and LGPL .	AT&T Open Source License	http://www.ggobi.org/ ; http://www.research.att.com/areas/stat/xgobi/
Xpatch (1 example)	Xpatch provides tools for predicting the likely radar signatures of both nearby and distant objects.	Community (Xpatch)	http://www.saic.com/products/software/xpatch/
zlib (6 examples)	A library of FOSS compression software with a license that permits use in closed source products.	zlib	http://www.gzip.org/zlib/
Zope (1 example)	Zope is a web application server used to create web-based applications such as intranets and portals.	ZPL	http://www.zope.org/

3. Use of Licenses in DoD Applications
1. List of FOSS Licenses

Table 8 lists the FOSS licenses used in the identified DoD applications, with links to the full texts of the licenses (in Appendix D) provided in the last column of the table.

Table 8 . Index and Notes for FOSS Licenses

License Name	Notes	Text
ACE/TAO Copyright	BSD-like (Douglas Schmidt)	D.1
AFPL (Aladdin Free Public License)	Unusual for its prohibition of for-profit sale of the software	D.2
Apache License	Used in the widely deployed Apache web server.	D.3
Artistic License	Used in the widely deployed Perl web language.	D.4
AT&T Open Source License		D.5
BSD License	The most common FOSS license, after GPL. Allows easy inclusion in non-BSD software, but does not ensure code rights to later software recipients	D.6
C++ Boost License Selection Spec.	BSD-like	D.7
Closed from open (eTrust)	Closed application with FOSS (OpenSSL License and toolkit) origins	D.8
Closed from open (GateD)	The original Cornell GateD Copyright made the source available, but placed restrictions on redistribution	D.9
Closed from open (MIMEsweeper)	Closed source tools with FOSS (SATAN License) origins	D.10
Closed from open (RealSecure)	RealSecure is a closed source tools with FOSS (SATAN License) origins	D.11
Colt License and Copyrights	A diverse mix of licenses including LGPL, public domain, and community	D.12
Community License (EADSIM)	Community license for U.S. Government users	D.13
Community License (WebTAS)	Community license for U.S. Government users	D.14
Community License (Xpatch)	Community license for U.S. Government users	D.15
Community Specification (CIS)	A community specification. Associated Scoring Tools that implement the specification are provided as freeware	D.16
Community Specification (SCA)	A community specification for developing proprietary software products.	D.17
Gnuplot Copyright	Forbids redistribution of full source code	D.18
GPL (General Public License)	The dominant FOSS license. GPL requires that code that directly incorporates GPL source also be licensed as GPL. This makes GPL more complicated to use (see in contrast BSD), but has the benefit of ensuring that all subsequent recipients of the original GPL software receive full software modification and redistribution rights (see in contrast BSD).	D.19
ImageMagick Copyright	BSD-like	D.20
IPL (IBM Public License)		D.21
ISC License	BSD-like	D.22
LaTeXProject Public License	One of the earliest open-source-like licenses	D.23
LGPL (Lesser General Public License)	BSD-like	D.24
Lsof Copyright	BSD-like (Victor Abell)	D.25
MITRE License	Allows selection of either GPL or MPL	D.26
MPL (Mozilla Public License)	Used to make public the formerly proprietary source of the Netscape browser	D.27
OpenMAP License	Retains BBN ownership of original source code, but allows developers to retain rights to any source code they may add	D.28
OpenSSL License	Apache-like	D.29
PHP License	Apache-like; replaces GPL of earlier PHP releases	D.30
Public Domain (Expect)	Expect is U.S. government public domain software whose original source code cannot be license or copyrighted, but can be incorporated freely under other more restrictive licenses.	D.31
Qmail License	Easy source distribution, but very tight control of changes	D.32
RTLinux Open Patent License	GPL-like and fully GPL compliant	D.33
SATAN License	BSD-like, but does not allow profits from redistributed copies	D.34
Sendmail License	GPL-like	D.35
TCP Wrappers License	BSD-like	D.36
Vovida Software License	BSD-like	D.37
VTK Copyright	BSD-like	D.38
WU-FTPD Software License	GPL-like	D.39
XFree86	BSD-like; very similar to the X/MIT License	D.40
X/MIT License	BSD-like; the basis of for the XFree86 License	D.41
zlib License	BSD-like	D.42
ZPL (Zope Public License)	GPL compatible	D.43

Applications Grouped By License

Table 9 provides a breakdown of DoD FOSS applications by the type of FOSS license used in each application. The GPL dominates, followed distantly by BSD and Apache.

Table 9 . Use of Licenses In All Applications

License	DoD Applications Using License
GPL (59) [52%]	ACID	Autoconf	Automake	bash	Bastille
	Condor	COPS	CVS	Cygwin	DDD
	DjVuLibre	Emacs	gawk (awk)	GCC	GDB
	GNAT	GnuPG	grep	h2n	HOSTS
	JDOM	jSIP	Kaffe	Linux	Linux (Red Hat)
	Linux firewalls	m4	Majordomo	make	Maxima
	MRTG	MTR	MySQL	Nessus	NetSaint
	nload	Nmap	ntop	NTP	Octave
	OpenOffice	Perl	Perl CGI scripts	PerLDAP	PingScan
	Procmail	R	RRDtool	RWhois	RXVT
	Samba	sed	SELinux	SNARE	Snort
	Squid	Top	Tripwire	Weka
BSD (7) [6%]	AMANDA	FreeBSD	NetBSD	OpenBSD
	OpenSSH	Tcl/Tk	Webmin
Apache (6) [5%]	Apache	Jakarta	Jaxen
	Tomcat	Xalan	Xerces
Community: CIS , EADSIM , SCA , WebTAS , Xpatch (5) [4%]	CIS Benchmarks	EADSIM	SCA
	WebTAS	Xpatch
Closed from open: eTrust , GateD , MIMEsweeper , RealSecure (4) [3%]	eTrust	GateD
	MIMEsweeper	RealSecure
LGPL (3) [3%]	JADE	JBoss
	VisAD
ACE/TAO (2) [2%]	ACE	ACE ORB (TAO)
SATAN (2) [2%]	SARA	SATAN
AFPL (1) [1%]	Ghostscript
Artistic (1) [1%]	Crack
AT&T Open Source (1) [1%]	XGobi
C++ Boost (1) [1%]	C++ Boost
Colt (1) [1%]	Colt
Gnuplot (1) [1%]	gnuplot
ImageMagick (1) [1%]	ImageMagick
IPL (1) [1%]	Jikes
ISC (1) [1%]	BIND
LaTeX (1) [1%]	LaTeX
Lsof (1) [1%]	Lsof
MITRE (1) [1%]	CVW
MPL (1) [1%]	Saxon
OpenMAP (1) [1%]	OpenMap
PHP (1) [1%]	PHP
OpenSSL (1) [1%]	OpenSSL
Public Domain (Expect) (1) [1%]	Expect
Qmail (1) [1%]	Qmail
RTLinux (1) [1%]	RTLinux
Sendmail (1) [1%]	Sendmail
TCP Wrappers (1) [1%]	TCP Wrappers
Vovida (1) [1%]	VOCAL
VTK (1) [1%]	VTK
WU-FTPD (1) [1%]	WU-FTPD
XFree86 (1) [1%]	XFree86
zlib (1) [1%]	zlib
ZPL (1) [1%]	Zope
(Total of 115 applications)

3. Breakdown of Licenses By Application Use

The tables in this section show the relative levels of use of the various types of FOSS licenses within the four major application areas of Infrastructure Support, Software Development, Security, and Research.

1. Use of Licenses in Infrastructure Support

Table 10 provides a breakout of how the licenses are used for Infrastructure Support.

Table 10 . Use of Licenses In Infrastructure Support Applications

License	DoD Infrastructure Support Applications Using License
GPL (32) [49%]	Condor	Cygwin	Emacs	gawk (awk)	GnuPG
	grep	h2n	JDOM	Linux (Red Hat)	Linux firewalls
	Majordomo	MRTG	MTR	MySQL	NetSaint
	nload	Nmap	ntop	NTP	OpenOffice
	Perl	Perl CGI scripts	PerLDAP	PingScan	Procmail
	RRDtool	RWhois	Samba	sed	SELinux
	Squid	Top
Apache (5) [8%]	Apache	Jaxen	Tomcat
	Xalan	Xerces
BSD (4) [6%]	AMANDA	FreeBSD
	OpenSSH	Webmin
ACE/TAO (2) [3%]	ACE	ACE ORB (TAO)
Community: EADSIM , SCA (2) [3%]	EADSIM	SCA
SATAN (2) [3%]	SARA	SATAN
AFPL (1) [1.5%]	Ghostscript
Closed from open: GateD (1) [1.5%]	GateD
ImageMagick (1) [1.5%]	ImageMagick
ISC (1) [1.5%]	BIND
LaTeX (1) [1.5%]	LaTeX
LGPL (1) [1.5%]	JBoss
Lsof (1) [1.5%]	Lsof
MITRE (1) [1.5%]	CVW
OpenMAP (1) [1.5%]	OpenMap
OpenSSL (1) [1.5%]	OpenSSL
PHP (1) [1.5%]	PHP
Qmail (1) [1.5%]	Qmail
RTLinux (1) [1.5%]	RTLinux
Sendmail (1) [1.5%]	Sendmail
WU-FTPD (1) [1.5%]	WU-FTPD
XFree86 (1) [1.5%]	XFree86
zlib (1) [1.5%]	zlib
ZPL (1) [1.5%]	Zope
(Total of 65 applications)

2. Use of Licenses in Software Development

Table 11 provides the same breakout for Software Development.

Table 11 . Use of Licenses In Software Development Applications

License	DoD Software Development Applications Using License
GPL (22) [42%]	Autoconf	Automake	bash	CVS	Cygwin
	DDD	DjVuLibre	Emacs	GCC	GDB
	GNAT	GnuPG	h2n	JDOM	jSIP
	Kaffe	Linux	m4	make	MySQL
	Perl	RXVT
Apache (5) [10%]	Jakarta	Jaxen	Tomcat
	Xalan	Xerces
BSD (4) [8%]	FreeBSD	NetBSD
	OpenSSH	Tcl/Tk
ACE/TAO (2) [4%]	ACE	ACE ORB (TAO)
LGPL (2) [4%]	JADE	JBoss
C++ Boost (1) [2%]	C++ Boost
Closed from open: GateD (1) [2%]	GateD
Community: SCA (1) [2%]	SCA
ImageMagick (1) [2%]	ImageMagick
IPL (1) [2%]	Jikes
LaTeX (1) [2%]	LaTeX
MPL (1) [2%]	Saxon
OpenMAP (1) [2%]	OpenMap
PHP (1) [2%]	PHP
Public Domain (Expect) (1) [2%]	Expect
RTLinux (1) [2%]	RTLinux
Vovida (1) [2%]	VOCAL
VTK (1) [2%]	VTK
WU-FTPD (1) [2%]	WU-FTPD
XFree86 (1) [2%]	XFree86
zlib (1) [2%]	zlib
ZPL (1) [2%]	Zope
(Total of 52 applications)

3. Use of Licenses in Security

Table 12 provides the breakout for Security.

Table 12 . Use of Licenses In Security Applications

License	DoD Security Applications Using License
GPL (26) [59%]	ACID	Bastille	COPS	GCC	GnuPG
	HOSTS	Linux	Linux (Red Hat)	Linux firewalls	MRTG
	MTR	MySQL	Nessus	NetSaint	nload
	Nmap	ntop	Perl	Perl CGI scripts	PerLDAP
	RRDtool	SELinux	SNARE	Snort	Squid
	Tripwire
BSD (5) [11%]	FreeBSD	OpenBSD	OpenSSH
	Tcl/Tk	Webmin
Closed from open: eTrust , MIMEsweeper , RealSecure (3) [7%]	eTrust	MIMEsweeper
	RealSecure
SATAN (2) [4.5%]	SARA	SATAN
Artistic (1) [2%]	Crack
Community: CIS (1) [2%]	CIS Benchmarks
Lsof (1) [2%]	Lsof
OpenSSL (1) [2%]	OpenSSL
PHP (1) [2%]	PHP
Public Domain (Expect) (1) [2%]	Expect
Qmail (1) [2%]	Qmail
TCP Wrappers (1) [2%]	TCP Wrappers
(Total of 44 applications)

4. Use of Licenses in Research

Finally, Table 13 provides the license breakout for Research.

Table 13 . Use of Licenses In Research Applications

License	DoD Research Applications Using License
GPL (7) [33%]	Condor	jSIP	Linux	Maxima
	Octave	R	Weka
Community: EADSIM , SCA , Xpatch (3) [14%]	EADSIM	SCA
	Xpatch
LGPL (2) [10%]	JADE	VisAD
ACE/TAO (1) [5%]	ACE ORB (TAO)
AT&T Open Source (1) [5%]	XGobi
Closed from open: GateD (1) [5%]	GateD
Colt (1) [5%]	Colt
Gnuplot (1) [5%]	gnuplot
IPL (1) [5%]	Jikes
MITRE (1) [5%]	CVW
Vovida (1) [5%]	VOCAL
VTK (1) [5%]	VTK
(Total of 21 applications)

4. FOSS Licenses

This appendix provides the complete text of the licenses used in the DoD FOSS applications that were identified by the survey. The online Internet source of each license is also given.

1. ACE-TAO License

Source: http://www.cs.wustl.edu/~schmidt/ACE-copying.html

Note: The license shown below is for reference purposes and does not apply to this document.

Copyright and Licensing Information for ACE(TM) and TAO(TM)

ACE ^(TM) and TAO ^(TM) are copyrighted by Douglas C. Schmidt and his research group at Washington University and University of California, Irvine , Copyright (c) 1993-2002, all rights reserved. Since ACE+TAO are open-source, free software, you are free to use, modify, copy, and distribute--perpetually and irrevocably--the ACE+TAO source code and object code produced from the source, as well as copy and distribute modified versions of this software. You must, however, include this copyright statement along with code built using ACE+TAO.

You can use ACE+TAO in proprietary software and are under no obligation to redistribute any of your source code that is built using ACE+TAO. Note, however, that you may not do anything to the ACE+TAO code, such as copyrighting it yourself or claiming authorship of the ACE+TAO code, that will prevent ACE+TAO from being distributed freely using an open-source development model. You needn’t inform anyone that you’re using ACE+TAO in your software, though we encourage you to let us know so we can promote your project in the ACE+TAO success stories.

ACE+TAO are provided as is with no warranties of any kind, including the warranties of design, merchantability, and fitness for a particular purpose, noninfringement, or arising from a course of dealing, usage or trade practice. Moreover, ACE+TAO are provided with no support and without any obligation on the part of Washington University, UC Irvine, their employees, or students to assist in its use, correction, modification, or enhancement. However, commercial support for ACE is available from Riverace and commercial support for TAO is available from OCI and PrismTech . Both ACE and TAO are Y2K-compliant, as long as the underlying OS platform is Y2K-compliant.

Washington University, UC Irvine, their employees, and students shall have no liability with respect to the infringement of copyrights, trade secrets or any patents by ACE+TAO or any part thereof. Moreover, in no event will Washington University or UC Irvine, their employees, or students be liable for any lost revenue or profits or other special, indirect and consequential damages.

The ACE and TAO web sites are maintained by the Center for Distributed Object Computing of Washington University for the development of open-source software as part of the open-source software community . By submitting comments, suggestions, code, code snippets, techniques (including that of usage), and algorithms, submitters acknowledge that they have the right to do so, that any such submissions are given freely and unreservedly, and that they waive any claims to copyright or ownership. In addition, submitters acknowledge that any such submission might become part of the copyright maintained on the overall body of code, which comprises the ACE and TAO software. By making a submission, submitter agree to these terms. Furthermore, submitters acknowledge that the incorporation or modification of such submissions is entirely at the discretion of the moderators of the open-source ACE+TAO projects or their designees.

The names ACE^(TM), TAO^(TM), Washington University, and UC Irvine, may not be used to endorse or promote products or services derived from this source without express written permission from Washington University or UC Irvine. Further, products or services derived from this source may not be called ACE^(TM) or TAO^(TM), nor may the name Washington University or UC Irvine appear in their names, without express written permission from Washington University or UC Irvine.

If you have any suggestions, additions, comments, or questions, please let me know.

Douglas C. Schmidt

2. AFPL

Source: http://www.cs.wisc.edu/~ghost/doc/AFPL/7.04/Public.htm

Note: The license shown below is for reference purposes and does not apply to this document.

Aladdin Free Public License (Version 9, September 18, 2000)

Copyright (C) 1994, 1995, 1997, 1998, 1999, 2000 Aladdin Enterprises, Menlo Park, California, U.S.A. All rights reserved.

NOTE: This License is not the same as any of the GNU Licenses published by the Free Software Foundation . Its terms are substantially different from those of the GNU Licenses. If you are familiar with the GNU Licenses, please read this license with extra care.

Aladdin Enterprises hereby grants to anyone the permission to apply this License to their own work, as long as the entire License (including the above notices and this paragraph) is copied with no changes, additions, or deletions except for changing the first paragraph of Section 0 to include a suitable description of the work to which the license is being applied and of the person or entity that holds the copyright in the work, and, if the License is being applied to a work created in a country other than the United States, replacing the first paragraph of Section 6 with an appropriate reference to the laws of the appropriate country.

This License is not an Open Source license: among other things, it places restrictions on distribution of the Program, specifically including sale of the Program. While Aladdin Enterprises respects and supports the philosophy of the Open Source Definition, and shares the desire of the GNU project to keep licensed software freely redistributable in both source and object form, we feel that Open Source licenses unfairly prevent developers of useful software from being compensated proportionately when others profit financially from their work. This License attempts to ensure that those who receive, redistribute, and contribute to the licensed Program according to the Open Source and Free Software philosophies have the right to do so, while retaining for the developer(s) of the Program the power to make those who use the Program to enhance the value of commercial products pay for the privilege of doing so.

0. Subject Matter

This License applies to the computer program known as "AFPL Ghostscript." The "Program", below, refers to such program. The Program is a copyrighted work whose copyright is held by artofcode LLC, located in Benicia, California (the "Licensor"). Please note that AFPL Ghostscript is neither the program known as "GNU Ghostscript" nor the version of Ghostscript available for commercial licensing from Artifex Software Inc.

A "work based on the Program" means either the Program or any derivative work of the Program, as defined in the United States Copyright Act of 1976, such as a translation or a modification.

BY MODIFYING OR DISTRIBUTING THE PROGRAM (OR ANY WORK BASED ON THE PROGRAM), YOU INDICATE YOUR ACCEPTANCE OF THIS LICENSE TO DO SO, AND ALL ITS TERMS AND CONDITIONS FOR COPYING, DISTRIBUTING OR MODIFYING THE PROGRAM OR WORKS BASED ON IT. NOTHING OTHER THAN THIS LICENSE GRANTS YOU PERMISSION TO MODIFY OR DISTRIBUTE THE PROGRAM OR ITS DERIVATIVE WORKS. THESE ACTIONS ARE PROHIBITED BY LAW. IF YOU DO NOT ACCEPT THESE TERMS AND CONDITIONS, DO NOT MODIFY OR DISTRIBUTE THE PROGRAM.

1. Licenses.

Licensor hereby grants you the following rights, provided that you comply with all of the restrictions set forth in this License and provided, further, that you distribute an unmodified copy of this License with the Program:

(a) You may copy and distribute literal (i.e., verbatim) copies of the Program’s source code as you receive it throughout the world, in any medium.

(b) You may modify the Program, create works based on the Program and distribute copies of such throughout the world, in any medium.

2. Restrictions.

This license is subject to the following restrictions:

(a) Distribution of the Program or any work based on the Program by a commercial organization to any third party is prohibited if any payment is made in connection with such distribution, whether directly (as in payment for a copy of the Program) or indirectly (as in payment for some service related to the Program, or payment for some product or service that includes a copy of the Program "without charge"; these are only examples, and not an exhaustive enumeration of prohibited activities). The following methods of distribution involving payment shall not in and of themselves be a violation of this restriction:

(i) Posting the Program on a public access information storage and retrieval service for which a fee is received for retrieving information (such as an on-line service), provided that the fee is not content-dependent (i.e., the fee would be the same for retrieving the same volume of information consisting of random data) and that access to the service and to the Program is available independent of any other product or service. An example of a service that does not fall under this section is an on-line service that is operated by a company and that is only available to customers of that company. (This is not an exhaustive enumeration.)

(ii) Distributing the Program on removable computer-readable media, provided that the files containing the Program are reproduced entirely and verbatim on such media, that all information on such media be redistributable for non-commercial purposes without charge, and that such media are distributed by themselves (except for accompanying documentation) independent of any other product or service. Examples of such media include CD-ROM, magnetic tape, and optical storage media. (This is not intended to be an exhaustive list.) An example of a distribution that does not fall under this section is a CD-ROM included in a book or magazine. (This is not an exhaustive enumeration.)

(b) Activities other than copying, distribution and modification of the Program are not subject to this License and they are outside its scope. Functional use (running) of the Program is not restricted, and any output produced through the use of the Program is subject to this license only if its contents constitute a work based on the Program (independent of having been made by running the Program).

(c) You must meet all of the following conditions with respect to any work that you distribute or publish that in whole or in part contains or is derived from the Program or any part thereof ("the Work"):

(i) If you have modified the Program, you must cause the Work to carry prominent notices stating that you have modified the Program’s files and the date of any change. In each source file that you have modified, you must include a prominent notice that you have modified the file, including your name, your e-mail address (if any), and the date and purpose of the change;

(ii) You must cause the Work to be licensed as a whole and at no charge to all third parties under the terms of this License;

(iii) If the Work normally reads commands interactively when run, you must cause it, at each time the Work commences operation, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty). Such notice must also state that users may redistribute the Work only under the conditions of this License and tell the user how to view the copy of this License included with the Work. (Exceptions: if the Program is interactive but normally prints or displays such an announcement only at the request of a user, such as in an "About box", the Work is required to print or display the notice only under the same circumstances; if the Program itself is interactive but does not normally print such an announcement, the Work is not required to print an announcement.);

(iv) You must accompany the Work with the complete corresponding machine-readable source code, delivered on a medium customarily used for software interchange. The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable code. If you distribute with the Work any component that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, you must also distribute the source code of that component if you have it and are allowed to do so;

(v) If you distribute any written or printed material at all with the Work, such material must include either a written copy of this License, or a prominent written indication that the Work is covered by this License and written instructions for printing and/or displaying the copy of the License on the distribution medium;

(vi) You may not impose any further restrictions on the recipient’s exercise of the rights granted herein.

If distribution of executable or object code is made by offering the equivalent ability to copy from a designated place, then offering equivalent ability to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source code along with the object code.

3. Reservation of Rights.

No rights are granted to the Program except as expressly set forth herein. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

4. Other Restrictions.

If the distribution and/or use of the Program is restricted in certain countries for any reason, Licensor may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

5. Limitations.

THE PROGRAM IS PROVIDED TO YOU "AS IS," WITHOUT WARRANTY. THERE IS NO WARRANTY FOR THE PROGRAM, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL LICENSOR, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

6. General.

This License is governed by the laws of the State of California, U.S.A., excluding choice of law rules.

If any part of this License is found to be in conflict with the law, that part shall be interpreted in its broadest meaning consistent with the law, and no other parts of the License shall be affected.

For United States Government users, the Program is provided with RESTRICTED RIGHTS. If you are a unit or agency of the United States Government or are acquiring the Program for any such unit or agency, the following apply:

If the unit or agency is the Department of Defense ("DOD"), the Program and its documentation are classified as "commercial computer software" and "commercial computer software documentation" respectively and, pursuant to DFAR Section 227.7202, the Government is acquiring the Program and its documentation in accordance with the terms of this License. If the unit or agency is other than DOD, the Program and its documentation are classified as "commercial computer software" and "commercial computer software documentation" respectively and, pursuant to FAR Section 12.212, the Government is acquiring the Program and its documentation in accordance with the terms of this License.

3. Apache License

Source: http://www.apache.org/LICENSE.txt

Note: The license shown below is for reference purposes and does not apply to this document.

The Apache Software License, Version 1.1

Copyright (c) 2000 The Apache Software Foundation. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/ )." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

4. The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected] .

5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

4. Artistic License

Source: http://www.perl.com/language/misc/Artistic.html

Note: The license shown below is for reference purposes and does not apply to this document.

Preamble

The intent of this document is to state the conditions under which a Package may be copied, such that the Copyright Holder maintains some semblance of artistic control over the development of the package, while giving the users of the package the right to use and distribute the Package in a more-or-less customary fashion, plus the right to make reasonable modifications.

Definitions

"Package" refers to the collection of files distributed by the Copyright Holder, and derivatives of that collection of files created through textual modification.

"Standard Version" refers to such a Package if it has not been modified, or has been modified in accordance with the wishes of the Copyright Holder as specified below.

"Copyright Holder" is whoever is named in the copyright or copyrights for the package.

"You" is you, if you’re thinking about copying or distributing this Package.

"Reasonable copying fee" is whatever you can justify on the basis of media cost, duplication charges, time of people involved, and so on. (You will not be required to justify it to the Copyright Holder, but only to the computing community at large as a market that must bear the fee.)

"Freely Available" means that no fee is charged for the item itself, though there may be fees involved in handling the item. It also means that recipients of the item may redistribute it under the same conditions they received it.

1. You may make and give away verbatim copies of the source form of the Standard Version of this Package without restriction, provided that you duplicate all of the original copyright notices and associated disclaimers.

2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domain or from the Copyright Holder. A Package modified in such a way shall still be considered the Standard Version.

3. You may otherwise modify your copy of this Package in any way, provided that you insert a prominent notice in each changed file stating how and when you changed that file, and provided that you do at least ONE of the following:

a. place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or placing the modifications on a major archive site such as uunet.uu.net, or by allowing the Copyright Holder to include your modifications in the Standard Version of the Package.

b. use the modified Package only within your corporation or organization.

c. rename any non-standard executables so the names do not conflict with standard executables, which must also be provided, and provide a separate manual page for each non-standard executable that clearly documents how it differs from the Standard Version.

d. make other distribution arrangements with the Copyright Holder.

4. You may distribute the programs of this Package in object code or executable form, provided that you do at least ONE of the following:

a. distribute a Standard Version of the executables and library files, together with instructions (in the manual page or equivalent) on where to get the Standard Version.

b. accompany the distribution with the machine-readable source of the Package with your modifications.

c. give non-standard executables non-standard names, and clearly document the differences in manual pages (or equivalent), together with instructions on where to get the Standard Version.

d. make other distribution arrangements with the Copyright Holder.

5. You may charge a reasonable copying fee for any distribution of this Package. You may charge any fee you choose for support of this Package. You may not charge a fee for this Package itself. However, you may distribute this Package in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this Package as a product of your own. You may embed this Package’s interpreter within an executable of yours (by linking); this shall be construed as a mere form of aggregation, provided that the complete Standard Version of the interpreter is so embedded.

6. The scripts and library files supplied as input to or produced as output from the programs of this Package do not automatically fall under the copyright of this Package, but belong to whomever generated them, and may be sold commercially, and may be aggregated with this Package. If such scripts or library files are aggregated with this Package via the so-called "undump" or "unexec" methods of producing a binary executable image, then distribution of such an image shall neither be construed as a distribution of this Package nor shall it fall under the restrictions of Paragraphs 3 and 4, provided that you do not represent such an executable image as a Standard Version of this Package.

7. C subroutines (or comparably compiled subroutines in other languages) supplied by you and linked into this Package in order to emulate subroutines and variables of the language defined by this Package shall not be considered part of this Package, but are the equivalent of input as in Paragraph 6, provided these subroutines do not change the language in any way that would cause it to fail the regression tests for the language.

8. Aggregation of this Package with a commercial distribution is always permitted provided that the use of this Package is embedded; that is, when no overt attempt is made to make this Package’s interfaces visible to the end user of the commercial distribution. Such use shall not be construed as a distribution of this Package.

9. The name of the Copyright Holder may not be used to endorse or promote products derived from this software without specific prior written permission.

10. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF merchantability AND FITNESS FOR A PARTICULAR PURPOSE.

The End

5. AT&T Open Source License

Source: http://www.ggobi.org/license.html

Note: The license shown below is for reference purposes and does not apply to this document.

SOURCE CODE AGREEMENT

Version 1.1

PLEASE READ THIS AGREEMENT CAREFULLY. By accessing and using the Source Code, you accept this Agreement in its entirety and agree to only use the Source Code in accordance with the following terms and conditions. If you do not wish to be bound by these terms and conditions, do not access or use the Source Code.

1. YOUR REPRESENTATIONS

1. You represent and warrant that:

a. If you are an entity, or an individual other than the person accepting this Agreement, the person accepting this Agreement on your behalf is your legally authorized representative, duly authorized to accept agreements of this type on your behalf and obligate you to comply with its provisions;

b. You have read and fully understand this Agreement in its entirety;

c. Your Build Materials are either original or do not include any Software obtained under a license that conflicts with the obligations contained in this Agreement;

d. To the best of your knowledge, your Build Materials do not infringe or misappropriate the rights of any person or entity; and,

e. You will regularly monitor the Website for any notices.

2. DEFINITIONS AND INTERPRETATION

1. For purposes of this Agreement, certain terms have been defined below and elsewhere in this Agreement to encompass meanings that may differ from, or be in addition to, the normal connotation of the defined word.

a. "Additional Code" means Software in source code form which does not contain any

i. of the Source Code, or

ii. derivative work (such term having the same meaning in this Agreement as under U.S. Copyright Law) of the Source Code.

b. "AT&T Patent Claims" means those claims of patents (i) owned by AT&T and (ii) licensable without restriction or obligation, which, absent a license, are necessarily and unavoidably infringed by the use of the functionality of the Source Code.

c. "Build Materials" means, with reference to a Derived Product, the Patch and Additional Code, if any, used in the preparation of such Derived Product, together with written instructions that describe, in reasonable detail, such preparation.

d. "Capsule" means a computer file containing the exact same contents as the computer file having the name ggobi.tgz, ggobi.tar.gz or ggobi.zip, which will be downloaded after accepting, or was opened to access, this Agreement.

e. "Derived Product" means a Software Product which is a derivative work of the Source Code.

f. "IPR" means all rights protectable under intellectual property law anywhere throughout the world, including rights protectable under patent, copyright and trade secret laws, but not trademark rights.

g. "Patch" means Software for changing all or any portion of the Source Code.

h. "Proprietary Notice" means the following statement:

"This product contains certain software code or other information ("AT&T Software") proprietary to AT&T Corp. ("AT&T"). The AT&T Software is provided to you "AS IS". YOU ASSUME TOTAL RESPONSIBILITY AND RISK FOR USE OF THE AT&T SOFTWARE. AT&T DOES NOT MAKE, AND EXPRESSLY DISCLAIMS, ANY EXPRESS OR IMPLIED WARRANTIES OF ANY KIND WHATSOEVER, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, WARRANTIES OF TITLE OR NON-INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHTS, ANY WARRANTIES ARISING BY USAGE OF TRADE, COURSE OF DEALING OR COURSE OF PERFORMANCE, OR ANY WARRANTY THAT THE AT&T SOFTWARE IS "ERROR FREE" OR WILL MEET YOUR REQUIREMENTS.

You have the right to obtain from the person or entity who furnished this product to you support and maintenance for the AT&T Software substantially similar to the support and maintenance offered by such person or entity with respect to the rest of this product and/or any other reasonably comparable products the person or entity distributes. Unless you accept a license to use the AT&T Software, you shall not reverse compile, disassemble or otherwise reverse engineer this product to ascertain the source code for any AT&T Software.

© AT&T Corp. All rights reserved. AT&T is a registered trademark of AT&T Corp."

i. "Software" means, as the context may require, source or object code instructions for controlling the operation of a central processing unit or computer, and computer files containing data or text.

j. "Software Product" means a collection of computer files containing Software in object code form only, which, taken together, reasonably comprise a product, regardless of whether such product is intended for internal use or commercial exploitation. A single computer file can comprise a Software Product.

k. "Source Code" means the Software contained in compressed form in the Capsule.

l. "Website" means the Internet website having the URL http://www.research.att.com/areas/stat/ggobi . AT&T may change the content or URL of the Website, or remove it from the Internet altogether.

2. By way of clarification only, the terms Capsule, Proprietary Notice and Source Code when used in this Agreement shall mean the materials and information defined by such terms without any change, enhancement, amendment, alteration or modification (collectively, "change").

3. GRANT OF RIGHTS

1. Subject to third party intellectual property claims, if any, and the terms and conditions of this Agreement, AT&T grants to you under:

a. the AT&T Patent Claims and AT&T’s copyright rights in the Source Code, a non-exclusive, fully paid-up license to:

i. Reproduce and distribute the Capsule;

ii. Compile the Source Code and execute the resultant binary Software on a computer;

iii. Prepare a Derived Product solely by compiling Additional Code, if any, together with the code resulting from operating a Patch on the Source Code; and,

iv. Execute on a computer and distribute to others Derived Products,

except that, with respect to the AT&T Patent Claims, the license rights granted in clauses (iii) and (iv) above shall only extend, and be limited, to that portion of a Derived Product which is Software compiled from some portion, without change, of the Source Code; and,

b. AT&T’s copyright rights in the Source Code, a non-exclusive, fully paid-up license to prepare and distribute Patches for the Source Code.

2. Subject to the terms and conditions of this Agreement, you may create a hyperlink between an Internet website owned and controlled by you and the Website, which hyperlink describes in a fair and good faith manner where the Capsule and Source Code may be obtained, provided that, you do not frame the Website or otherwise give the false impression that AT&T is somehow associated with, or otherwise endorses or sponsors your website. Any goodwill associated with such hyperlink shall inure to the sole benefit of AT&T. Other than the creation of such hyperlink, nothing in this Agreement shall be construed as conferring upon you any right to use any reference to AT&T, its trade names, trademarks, service marks or any other indicia of origin owned by AT&T, or to indicate that your products or services are in any way sponsored, approved or endorsed by, or affiliated with, AT&T.

3. Except as expressly set forth in Section 3.1 above, no other rights or licenses under any of AT&T’s IPR are granted or, by implication, estoppel or otherwise, conferred. By way of example only, no rights or licenses under any of AT&T’s patents are granted or, by implication, estoppel or otherwise, conferred with respect to any portion of a Derived Product which is not Software compiled from some portion, without change, of the Source Code.

4. YOUR OBLIGATIONS

1. You shall only distribute the Capsule and Build Materials free of charge, without any form of compensation. However, you may charge for bona fide maintenance and support of the Software resulting from the Build Materials and, if you furnish the Capsule or Build Materials on any physical media, you may charge for your out-of-pocket expense for both the media and shipping. You may distribute Derived Products for a fair and reasonable fee.

2. If you distribute Build Materials (including if you are required to do so pursuant to this Agreement), you shall ensure that the recipient enters into and duly accepts a written agreement with you which includes the minimum terms set forth in Appendix A (completed to indicate you as the LICENSOR) and no other provisions which, in AT&T’s opinion, conflict with your obligations under, or the intent of, this Agreement. The agreement required under this Section 4.2 may be in electronic form.

3. If you prepare a Derived Product that you distribute to a third party, or if you distribute to a third party any Build Materials for a Derived Product, you shall make available to such third party support and maintenance for at least that portion of such Derived Product or Build Materials which is, or is a derivative work of, the Source Code. Such support and maintenance shall be substantially similar to the support and maintenance offered by you with respect to any other reasonably comparable products that you distribute. In no event shall you or anyone acting for you, in any way, indicate to any person or entity that AT&T will support or maintain any Software and you shall indemnify AT&T for any expenses, including legal fees, incurred by AT&T as a result of a breach of this Section 4.3.

4. If you prepare a Patch which you distribute to anyone else you shall:

a. Contact AT&T, as may be provided on the Website or in a text file included with the Source Code, and describe for AT&T such Patch; and,

b. Provide AT&T with a copy of such Patch as directed by AT&T, unless you make it generally available on your Internet website, in which case, you shall provide AT&T with the URL of your website and hereby grant to AT&T a non-exclusive, fully-paid up right to create a hyperlink between your website and a page associated with the Website.

5. If you prepare a Derived Product, such product shall conspicuously display to users, and any corresponding documentation and license agreement shall include as a provision, the Proprietary Notice.

5. YOUR GRANT OF RIGHTS TO AT&T

1. You grant to AT&T under any IPR owned or licensable by you which in any way relates to your Patches, a non-exclusive, perpetual, worldwide, fully paid-up, unrestricted, irrevocable license, along with the right to sublicense others, to (a) make, have made, use, offer to sell, sell and import any products, services or any combination of products or services, and (b) reproduce, distribute, prepare derivative works based on, perform, display and transmit your Patches in any media whether now known or in the future developed.

6. AS IS CLAUSE / LIMITATION OF LIABILITY

1. The Source Code and Capsule are provided to you "AS IS". YOU ASSUME TOTAL RESPONSIBILITY AND RISK FOR YOUR USE OF THEM INCLUDING THE RISK OF ANY DEFECTS OR INACCURACIES THEREIN. AT&T DOES NOT MAKE, AND EXPRESSLY DISCLAIMS, ANY EXPRESS OR IMPLIED WARRANTIES OF ANY KIND WHATSOEVER, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, WARRANTIES OF TITLE OR NON-INFRINGEMENT OF ANY IPR OR TRADEMARK RIGHTS, ANY WARRANTIES ARISING BY USAGE OF TRADE, COURSE OF DEALING OR COURSE OF PERFORMANCE, OR ANY WARRANTY THAT THE SOURCE CODE OR CAPSULE ARE "ERROR FREE" OR WILL MEET YOUR REQUIREMENTS.

2. IN NO EVENT SHALL AT&T BE LIABLE FOR (a) ANY INCIDENTAL, CONSEQUENTIAL, OR INDIRECT DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION, LOSS OF PROGRAMS OR INFORMATION, AND THE LIKE) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOURCE CODE OR CAPSULE, EVEN IF AT&T OR ANY OF ITS AUTHORIZED REPRESENTATIVES HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, (b) ANY CLAIM ATTRIBUTABLE TO ERRORS, OMISSIONS, OR OTHER INACCURACIES IN THE SOURCE CODE OR CAPSULE, OR (c) ANY CLAIM BY ANY THIRD PARTY.

3. BECAUSE SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. IN THE EVENT THAT APPLICABLE LAW DOES NOT ALLOW THE COMPLETE EXCLUSION OR LIMITATION OF LIABILITY OF CLAIMS AND DAMAGES AS SET FORTH IN THIS AGREEMENT, AT&T’S LIABILITY IS LIMITED TO THE GREATEST EXTENT PERMITTED BY LAW.

7. INDEMNIFICATION

1. You shall indemnify and hold harmless AT&T, its affiliates and authorized representatives against any claims, suits or proceedings asserted or commenced by any third party and arising out of, or relating to, your use of the Source Code. This obligation shall include indemnifying against all damages, losses, costs and expenses (including attorneys’ fees) incurred by AT&T, its affiliates and authorized representatives as a result of any such claims, suits or proceedings, including any costs or expenses incurred in defending against any such claims, suits, or proceedings.

8. GENERAL

1. You shall not assert against AT&T, its affiliates or authorized representatives any claim for infringement or misappropriation of any IPR or trademark rights in any way relating to the Source Code, including any such claims relating to any Patches.

2. In the event that any provision of this Agreement is deemed illegal or unenforceable, AT&T may, but is not obligated to, post on the Website a new version of this Agreement which, in AT&T’s opinion, reasonably preserves the intent of this Agreement.

3. Your rights and license (but not any of your obligations) under this Agreement shall terminate automatically in the event that (a) notice of a non-frivolous claim by a third party relating to the Source Code or Capsule is posted on the Website, (b) you have knowledge of any such claim, (c) any of your representations or warranties in Article 1.0 or Section 8.4 are false or inaccurate, (d) you exceed the rights and license granted to you or (e) you fail to fully comply with any provision of this Agreement. Nothing in this provision shall be construed to restrict you, at your option and subject to applicable law, from replacing the portion of the Source Code that is the subject of a claim by a third party with non-infringing code or from independently negotiating for necessary rights from the third party.

4. You acknowledge that the Source Code and Capsule are subject to U.S. export laws and regulations and that any use thereof must be authorized under those laws and regulations. You hereby assure AT&T that you will not, directly or indirectly, "export" or "reexport" the Source Code or Capsule to any country, or national of any country, to which, or to whom, "export" or "reexport" is prohibited under U.S. export laws and regulations. For purposes of this Section 8.4, "export" and "reexport" mean transferring or releasing to another country or to a national of another country (wherever that person is located) by any means, including physical, electronic, or otherwise. You represent and warrant that you are not located in or a national of any such country.

5. Without limiting any of AT&T’s rights under this Agreement or at law or in equity, or otherwise expanding the scope of the license and rights granted hereunder, if you fail to perform any of your obligations under this Agreement with respect to any of your Patches or Derived Products, or if you do any act which exceeds the scope of the license and rights granted herein, then such Patches,Derived Products and acts are not licensed or otherwise authorized under this Agreement and such failure shall also be deemed a breach of this Agreement. In addition to all other relief available to it for any breach of your obligations under this Agreement, AT&T shall be entitled to an injunction requiring you to perform such obligations.

6. This Agreement shall be governed by and construed in accordance with the laws of the State of New York, USA, without regard to its conflicts of law rules. This Agreement shall be fairly interpreted in accordance with its terms and without any strict construction in favor of or against either AT&T or you. Any suit or proceeding you bring relating to this Agreement shall be brought and prosecuted only in New York, New York, USA.

Appendix A - Minimum Terms

The minimum terms are available at the Internet website having the URL http://www.research.att.com/areas/stat/ggobi or accessed by opening the computer file having the name MINTERMS.txt.

6. BSD License

Source: http://www.opensource.org/licenses/bsd-license.php

Note: The license shown below is for reference purposes and does not apply to this document.

The BSD License

The following is a BSD license template. To generate your own license, change the values of OWNER, ORGANIZATION and YEAR from their original values as given here, and substitute your own.

Note: The advertising clause in the license appearing on BSD Unix files was officially rescinded by the Director of the Office of Technology Licensing of the University of California on July 22 1999. He states that clause 3 is "hereby deleted in its entirety."

Note the new BSD license is thus equivalent to the MIT License, except for the no-endorsement final clause.

<OWNER> = Regents of the University of California <ORGANIZATION> = University of California, Berkeley <YEAR> = 1998

In the original BSD license, both occurrences of the phrase "COPYRIGHT HOLDERS AND CONTRIBUTORS" in the disclaimer read "REGENTS AND CONTRIBUTORS".

Here is the license template:

Copyright (c) <YEAR>, <OWNER> All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the <ORGANIZATION> nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

7. C++ Boost License Selection Specification

Source: http://www.boost.org/more/lib_guide.htm#License

Note: The license shown below is for reference purposes and does not apply to this document.

Boost Library Requirements and Guidelines

…

Requirements

…

* The license must meet the license requirements below. Restricted licenses like the GPL and LGPL are not acceptable.

* The copyright ownership must be clear.

License requirements

* Must be simple to read and understand.

* Must grant permission to copy, use and modify the software for any use (commercial and non-commercial) for no fee.

* Must require that the license appear on all copies of the software source code.

* Must not require that the license appear with executables or other binary uses of the library.

* Must not require that the source code be available for execution or other binary uses of the library.

* May restrict the use of the name and description of the library to the standard version found on the Boost web site.

…

Ownership

Are you sure you own the library you are thinking of submitting? "How to Copyright Software" by MJ Salone, Nolo Press, 1990 says:

Doing work on your own time that is very similar to programming you do for your employer on company time can raise nasty legal problems.  In this situation, it’s best to get a written release from your employer in advance.

Place a copyright notice in all the important files you submit. Boost.org won’t accept libraries without clear copyright information.

…

8. Closed from open (eTrust)

Source: http://www3.ca.com/Solutions/Solution.asp?ID=271

Note: The proprietary license for this closed software product is not available online.

[Proprietary license not available online]

9. Closed from open (GateD)

Source: http://www.merit.edu/internet/net-research/idrp/mitre/doc/gated_doc/copyright.html

Note 1: The license shown below is for the earlier open version of this now-closed product.

Note 2: The license shown below is for reference purposes and does not apply to this document.

GateD, Release 3.5

Copyright (c) 1990,1991,1992,1993,1994 by Cornell University All rights reserved.

THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Royalty-free licenses to redistribute GateD Release 3 in whole or in part may be obtained by writing to:

GateDaemon Project Information Technologies/Network Resources 200 CCC Cornell University Ithaca, NY 14853-2601 USA

GateD is based on Kirton’s EGP, UC Berkeley’s routing daemon (routed), and DCN’s HELLO routing Protocol. Development of GateD has been supported in part by the National Science Foundation.

Please forward bug fixes, enhancements and questions to the gated mailing list: [email protected].

------------------------------------------------------------------------

Portions of this software may fall under the following copyrights:

Copyright (c) 1988 Regents of the University of California. All rights reserved.

Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

10. Closed from open (MIMEsweeper)

Source: http://www.mimesweeper.com/default.asp

Note: The proprietary license for this closed software product is not available online.

[Proprietary license not available online]

11. Closed from open (RealSecure)

Source: http://www.iss.net/products_services/enterprise_protection/rsnetwork/index.php

Note: The proprietary license for this closed software product is not available online.

[Proprietary license not available online]

12. Colt License and Copyrights

Source: http://tilde-hoschek.home.cern.ch/~hoschek/colt/V1.0.2/doc/cern/colt/doc-files/license.html

Note: The license shown below is for reference purposes and does not apply to this document.

License and Copyrights

These are the copyright and license statements for the Colt Distribution, Version 1.0.2. Do not use this software if you do not accept the terms of the licenses described below. In alphabetic order:

packages cern.colt* , cern.jet*, cern.clhep

Written by Wolfgang Hoschek (http://www.cern.ch/CERN/Divisions/EP/HL/index.html ). Check the Colt home page (http://nicewww.cern.ch/~hoschek/colt/index.htm ) for more info.

Copyright © 1999 CERN - European Organization for Nuclear Research.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. CERN makes no representations about the suitability of this software for any purpose. It is provided "as is" without expressed or implied warranty.

package corejava

Written by Cay S. Horstmann (http://www.horstmann.com/ )& Gary Cornell.

Copyright © 1997 Sun Microsystems Inc. All Rights Reserved.

Cay S. Horstmann & Gary Cornell, Core Java Published By Sun Microsystems Press/Prentice-Hall Copyright (C) 1997 Sun Microsystems Inc. All Rights Reserved. Permission to use, copy, modify, and distribute this software and its documentation for NON-COMMERCIAL purposes and without fee is hereby granted provided that this copyright notice appears in all copies. THE AUTHORS AND PUBLISHER MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY OF THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THE AUTHORS AND PUBLISHER SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES.

package com.imsl.math

Written by Visual Numerics, Inc. Check the Visual Numerics home page (http://www.vni.com/ ) for more info.

Copyright (c) 1997 - 1998 by Visual Numerics, Inc. All rights reserved.

Permission to use, copy, modify, and distribute this software is freely granted by Visual Numerics, Inc., provided that the copyright notice above and the following warranty disclaimer are preserved in human readable form. Because this software is licenses free of charge, it is provided "AS IS", with NO WARRANTY. TO THE EXTENT PERMITTED BY LAW, VNI DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ITS PERFORMANCE, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. VNI WILL NOT BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF THE USE OF OR INABILITY TO USE THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, PUNITIVE, AND EXEMPLARY DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

package edu.cornell.lassp.houle.RngPack

Written by Paul Houle (http://www.msc.cornell.edu/~houle ). Check the RngPack home page (http://www.honeylocust.com/RngPack/ ) for more info.

Copyright © 1997, 1998 honeylocust media systems.

This package is released free under the GNU General Public License (http://www.gnu.ai.mit.edu/copyleft/gpl.html ).

package edu.oswego.cs.dl.util.concurrent

Written by Doug Lea (http://gee.cs.oswego.edu/dl ). Check the util.concurrent home page (http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html ) for more info.

Originally written by Doug Lea and released into the public domain. He says about this package: All classes are released to the public domain and may be used for any purpose whatsoever without permission or acknowledgment.

packages hep.aida.*

Written by Pavel Binko, Dino Ferrero Merlino, Wolfgang Hoschek, Tony Johnson, Andreas Pfeiffer, and others. Check the FreeHEP home page (http://java.freehep.org/ ) for more info.

Permission to use and/or redistribute this work is granted under the terms of the LGPL License (http://www.gnu.org/copyleft/lgpl.html ), with the exception that any usage related to military applications is expressly forbidden. The software and documentation made available under the terms of this license are provided with no warranty.

packages jal*

Written by Matthew Austern (http://reality.sgi.com/austern/index.html ) and Alexander Stepanov (mailto:[email protected] ). Check the JAL home page (http://reality.sgi.com/austern_mti/java/ ) for more info.

Copyright © 1996 Silicon Graphics, Inc.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided "as is" without expressed or implied warranty.

package ViolinStrings

Written by Michael Schmeling (mailto:[email protected] ). Check the ViolinStrings home page (http://users.aol.com/MSchmelng/Home.html )for more info.

(C) 1998 Michael Schmeling.

This software is provided ‘as-is’, without any express or implied warranty. In no event will the author be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. Altered version of the source code or the class files must be stored with a different Java package name, so that users can clearly distinguish those altered versions from the original software and can use them safely together with the original software.

4. This notice may not be removed or altered from any source distribution.

13. Community License (EADSIM)

Source: https://www.eadsim.com/RequestName/EADSIMPassword.asp

Note: The license shown below is for reference purposes and does not apply to this document.

Request An EADSIM Homepage Password

(* Denotes a required field.)

* Name:

* Requested Username:

Rank/Title:

* Company/Organization:

* Are you the Registered POC?:

If No, Registered POC:

* Street Address:

* City:

* Phone:

* E-Mail:

* U. S. Citizen:

14. Community License (WebTAS)

Source: http://www.iswsolutions.com/webtas/download.shtml

Note: The license shown below is for reference purposes and does not apply to this document.

Please fill out the following form to request an evaluation WebTAS download. We will contact you shortly.

You must have a Government sponsor to get a free evaluation. WebTAS is freely distributed to Federal Government customers. Distribution must be approved by the WebTAS Air Force program Office. Contact John Mucks for details. Email: [email protected]

Questions may be directed to the following

Air Force Program Manager
Mr. John Mucks
[email protected]
315-330-7950

WebTAS Program Manager
Mr. Jay Jesse
[email protected]
719-457-0690 x2601
Intelligent Software Solutions, Inc.

Name:
Organization:
E-Mail:
Phone #:

How did you hear about WebTAS?

Government Sponsor

Purpose of Evaluation

Any comments and/or questions?

15. Community License (Xpatch)

Source: http://www.saic.com/products/software/xpatch/faq.html

Note: The license shown below is for reference purposes and does not apply to this document.

Platform/License Questions

Q. My organization is located outside of the US. Can I order Xpatch?

A. Xpatch is export-controlled software and is only available to U.S. government agencies and government contractors.

16. Community Specification (CIS)

Source: http://www.cisecurity.org/membership.html

Note: The license shown below is for reference purposes and does not apply to this document.

…

… We invite you to join us - more than 170 member companies, educational organizations, government and law enforcement agencies plus individuals from around the world - in our quest to raise the level of security for everyone’s information assets that are connected to the Internet.

…

Benefits of Membership

#1... An active voice in the development of Benchmarks that are quickly becoming widely accepted as a prudent due care security standard for organizations of all types.

#2... The right to distribute the benchmarks and tools within your organization. (User Members and Consulting Members only are entitled to this benefit)

#3... Timely electronic notification of updates to the Benchmarks and Scoring Tools.

#4... The right to claim compliance with the CIS Benchmarks with auditors and business partners.

#5... Visibility for your organization’s tangible commitment to Internet security through its inclusion in the Roster of Members on the CIS website and promotional materials.

#6... The right to use the Center’s logo on your organization’s website and documents, establishing its status as a leader in working with others to formulate better security standards for systems connected to the Internet.

#7... Working and networking with other highly skilled people from organizations around the world, both virtually and in person during periodic CIS meetings.

Who Should Be a CIS Member

The Center represents the shared interests of:

* Users-Organizations that depend on secure and reliable cyber systems;

* Auditors who strive to verify the security of clients’ automated information systems in a way that is consistent with their audit of other standards-based business processes;

* IT Consultants who help clients improve their system security configurations to levels that are widely accepted as prudent due care or best practice;

* Security Software Vendors who market commercially available tools that assess and report the conformity of system security configurations with the settings and actions defined in CIS benchmarks;

* ISPs, Web Hosting Companies, Business-to-Business e-Commerce Exchanges, and others who have a direct stake in minimizing their customers’ risk of business disruptions and cyber crime;

* Insurance Companies that strive to minimize the underwriting risk associated with the information assets of the businesses which they insure;

* Network security specialists, firewall administrators, and others whose job it is to ensure the security, privacy, integrity, and availability of information assets under their custodial care;

CIS is a not-for-profit consortium not tied to any proprietary product or service.

Categories of Membership

Category 1 - Consultants, Auditors, and Commercial Software Companies ($11,000 annual membership fee) for organizations that market security software and/or provide information security consulting or auditing services

Category 2A - Large User-Organizations ($7,000 annual membership fee) for end-user organizations that have 100 or more employees

Category 2B - Small User-Organizations ($2,000 annual membership fee) for end-user organizations that have fewer than 100 employees

Category 3 - Individuals ($250 annual membership fee) for an individual who is not affiliated with an organization, or whose organization does not reimburse him/her for the membership fee -- Individual Members are not permitted, by the Benchmark Terms of Use Agreement, to distribute the benchmarks and scoring tools within their organizations.

All membership fees are for a one-year period beginning upon receipt of the member’s application.

To become a Member

Please print and complete this form, then fax it to 301-951-0140, or mail it with a check to:

The Center for Internet Security
5401 Westbard Ave.
Suite 1501
Bethesda, MD 20816

Make your check payable to "The Center for Internet Security"

17. Community Specification (SCA)

Source: http://www.jtrs.saalt.army.mil/SCA/scachange.html

Note: The license shown below is for reference purposes and does not apply to this document.

JTRS SCA Change Proposal

This form is provided as a template for you to propose changes to the Software Communications Architecture (SCA) Specification, and other controlled documents, found on this website. The form is produced in MS Word 97 using the "table" format. It should be electronically downloaded, completed following the detailed instructions on the form, and submitted as an e-mail attachment to the JTRS Program Office at [email protected] .

The JPO will conduct a quick-look review of the proposed changes within two working days of receipt and, if acceptable, forward them to the CCB for consideration.

Questions or comments about the SCA or the other controlled documents may be submitted to the JTRS Program Office at the same e-mail address, [email protected] . These questions and comments will be addressed as expeditiously as possible.

18. Gnuplot Copyright

Source: http://www.brics.dk/~engberg/usr_local_doc/gnuplot-shr-3.7/Copyright

Note: The license shown below is for reference purposes and does not apply to this document.

Copyright 1986 - 1993, 1998 Thomas Williams, Colin Kelley

Permission to use, copy, and distribute this software and its documentation for any purpose with or without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation.

Permission to modify the software is granted, but not the right to distribute the complete modified source code. Modifications are to be distributed as patches to the released version. Permission to distribute binaries produced by compiling modified sources is granted, provided you

1. distribute the corresponding source modifications from the released version in the form of a patch file along with the binaries,

2. add special version identification to distinguish your version in addition to the base release version number,

3. provide your name and address as the primary contact for the support of your modified version, and

4. retain our contact information in regard to use of the base software.

Permission to distribute the released version of the source code along with corresponding source modifications in the form of a patch file is granted with same provisions 2 through 4 for binary distributions.

This software is provided "as is" without express or implied warranty to the extent permitted by applicable law.

19. GPL

Source: http://www.gnu.org/licenses/gpl.html

Note: The license shown below is for reference purposes and does not apply to this document.

GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation’s software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author’s protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors’ reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone’s free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients’ exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.

<one line to give the program’s name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w’.
This is free software, and you are welcome to redistribute it under certain conditions; type `show c’ for details.

The hypothetical commands `show w’ and `show c’ should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w’ and `show c’; they could even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision’ (which makes passes at compilers) written by James Hacker.

<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.

20. ImageMagick Copyright

Source: http://www.imagemagick.org/www/Copyright.html

Note: The license shown below is for reference purposes and does not apply to this document.

Copyright (C) 2002 ImageMagick Studio, a non-profit organization dedicated to making software imaging solutions freely available.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files ("ImageMagick"), to deal in ImageMagick without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of ImageMagick, and to permit persons to whom the ImageMagick is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of ImageMagick.

The software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall ImageMagick Studio be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with ImageMagick or the use or other dealings in ImageMagick.

Except as contained in this notice, the name of the ImageMagick Studio shall not be used in advertising or otherwise to promote the sale, use or other dealings in ImageMagick without prior written authorization from the ImageMagick Studio.

ImageMagick is available as

ftp://ftp.imagemagick.org/pub/ImageMagick/

The official ImageMagick WWW page is

http://www.imagemagick.org/

21. IPL

Source: http://oss.software.ibm.com/developerworks/oss/license10.html

Note: The license shown below is for reference purposes and does not apply to this document.

IBM Public License Version 1.0

THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT’S ACCEPTANCE OF THIS AGREEMENT.

1. DEFINITIONS

"Contribution" means:

a) in the case of International Business Machines Corporation ("IBM"), the Original Program, and

b) in the case of each Contributor,

i) changes to the Program, and

ii) additions to the Program;

where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution ‘originates’ from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor’s behalf. Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program.

"Contributor" means IBM and any other entity that distributes the Program.

"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program.

"Original Program" means the original version of the software accompanying this Agreement as released by IBM, including source code, object code and documentation, if any.

"Program" means the Original Program and Contributions.

"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.

2. GRANT OF RIGHTS

a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.

b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder.

c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient’s responsibility to acquire that license before distributing the Program.

d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement.

3. REQUIREMENTS

A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:

a) it complies with the terms and conditions of this Agreement; and

b) its license agreement:

i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;

ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;

iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and

iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.

When the Program is made available in source code form:

a) it must be made available under this Agreement; and

b) a copy of this Agreement must be included with each copy of the Program.

Each Contributor must include the following in a conspicuous location in the Program:

Copyright (c) {date here}, International Business Machines Corporation and others. All Rights Reserved.

In addition, each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.

4. COMMERCIAL DISTRIBUTION

Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.

For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor’s responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.

5. NO WARRANTY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.

6. DISCLAIMER OF LIABILITY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7. GENERAL

If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.

If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient’s patent(s), then such Recipient’s rights granted under Section 2(b) shall terminate as of the date such litigation is filed.

All Recipient’s rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient’s rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient’s obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.

IBM may publish new versions (including revisions) of this Agreement from time to time. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. No one other than IBM has the right to modify this Agreement. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.

This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.

22. ISC License

Source: http://old.lwn.net/1999/0909/a/bind-license.html

Note: The license shown below is for reference purposes and does not apply to this document.

Copyright (c) 1993-1999 by Internet Software Consortium.

Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Internet Software Consortium
950 Charter Street
Redwood City, CA 94063
Tel: 1-888-868-1001
Fax: 1-650-779-7055
Email: [email protected]

------

The RSA license is:

------

DNSSAFE LICENSE TERMS

This BIND software includes the DNSsafe software from RSA Data Security, Inc., which is copyrighted software that can only be distributed under the terms of this license agreement.

The DNSsafe software cannot be used or distributed separately from the BIND software. You only have the right to use it or distribute it as a bundled, integrated product.

The DNSsafe software can ONLY be used to provide authentication for resource records in the Domain Name System, as specified in RFC 2065 and successors. You cannot modify the BIND software to use the DNSsafe software for other purposes, or to make its cryptographic functions available to end-users for other uses.

If you modify the DNSsafe software itself, you cannot modify its documented API, and you must grant RSA Data Security the right to use, modify, and distribute your modifications, including the right to use any patents or other intellectual property that your modifications depend upon.

You must not remove, alter, or destroy any of RSA’s copyright notices or license information. When distributing the software to the Federal Government, it must be licensed to them as "commercial computer software" protected under 48 CFR 12.212 of the FAR, or 48 CFR 227.7202.1 of the DFARS.

You must not violate United States export control laws by distributing the DNSsafe software or information about it, when such distribution is prohibited by law.

THE DNSSAFE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY WARRANTY WHATSOEVER. RSA HAS NO OBLIGATION TO SUPPORT, CORRECT, UPDATE OR MAINTAIN THE RSA SOFTWARE. RSA DISCLAIMS ALL WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO ANY MATTER WHATSOEVER, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT OF THIRD PARTY RIGHTS.

If you desire to use DNSsafe in ways that these terms do not permit, please contact RSA Data Security, Inc., 100 Marine Parkway, Redwood City, California 94065, USA, to discuss alternate licensing arrangements.

23. LaTeXProject Public License

Source: http://www.latex-project.org/lppl.html

Note: The license shown below is for reference purposes and does not apply to this document.

LaTeXProject Public License

LPPL Version 1.2 1999-09-03

Copyright 1999 LaTeX3 Project

Everyone is allowed to distribute verbatim copies of this license document, but modification of it is not allowed.

PREAMBLE

The LaTeX Project Public License (LPPL, http://www.latex-project.org/lppl.txt ) is the license under which the base LaTeX distribution is distributed.

You may use this license for any program that you have written and wish to distribute. This license may be particularly suitable if your program is TeX-related (such as a LaTeX package), but you may use it even if your program is unrelated to TeX. The section ‘WHETHER AND HOW TO DISTRIBUTE PROGRAMS UNDER THIS LICENSE’, below, gives instructions, examples, and recommendations for authors who are considering distributing their programs under this license.

In this license document, ‘The Program’ refers to any program distributed under this license.

This license gives conditions under which The Program may be distributed and conditions under which modified versions of The Program may be distributed. Individual files of The Program may bear supplementary and/or superseding conditions on modification of themselves and on the distribution of modified versions of themselves, but *no* file of The Program may bear supplementary or superseding conditions on the distribution of an unmodified copy of the file. A distributor wishing to distribute a complete, unmodified copy of The Program therefore needs to check the conditions only in this license and nowhere else.

Activities other than distribution and/or modification of The Program are not covered by this license; they are outside its scope. In particular, the act of running The Program is not restricted.

We, the LaTeX3 Project, believe that the conditions below give you the freedom to make and distribute modified versions of The Program that conform with whatever technical specifications you wish while maintaining the availability, integrity, and reliability of The Program. If you do not see how to achieve your goal while meeting these conditions, then read the document ‘cfgguide.tex’ in the base LaTeX distribution for suggestions.

CONDITIONS ON DISTRIBUTION AND MODIFICATION

You may distribute a complete, unmodified copy of The Program. Distribution of only part of The Program is not allowed.

You may not modify in any way a file of The Program that bears a legal notice forbidding modification of that file.

You may distribute a modified file of The Program if, and only if, the following eight conditions are met:

1. You must meet any additional conditions borne by the file on the distribution of a modified version of the file as described below in the subsection ‘Additional Conditions on Individual Files of The Program’.

2. If the file is a LaTeX software file, then you must meet any applicable additional conditions on the distribution of a modified version of the file that are described below in the subsection ‘Additional Conditions on LaTeX Software Files’.

3. You must not distribute the modified file with the filename of the original file.

4. In the modified file, you must acknowledge the authorship and name of the original file, and the name (if any) of the program which contains it.

5. You must change any identification string in the file to indicate clearly that the modified file is not part of The Program.

6. You must change any addresses in the modified file for the reporting of errors in the file or in The Program generally to ensure that reports for files no longer maintained by the original maintainers will be directed to the maintainers of the modified files.

7. You must distribute the modified file under a license that forbids distribution both of the modified file and of any files derived from the modified file with the filename of the original file.

8. You must do either (A) or (B):

(A) distribute a copy of The Program (that is, a complete, unmodified copy of The Program) together with the modified file; if your distribution of the modified file is made by offering access to copy the modified file from a designated place, then offering equivalent access to copy The Program from the same place meets this condition, even though third parties are not compelled to copy The Program along with the modified file;

(B) provide to those who receive the modified file information that is sufficient for them to obtain a copy of The Program; for example, you may provide a Uniform Resource Locator (URL) for a site that you expect will provide them with a copy of The Program free of charge (either the version from which your modification is derived, or perhaps a later version).

Note that in the above, ‘distribution’ of a file means making the file available to others by any means. This includes, for instance, installing the file on any machine in such a way that the file is accessible by users other than yourself. ‘Modification’ of a file means any procedure that produces a derivative file under any applicable law - that is, a file containing the original file or a significant portion of it, either verbatim or with modifications and/or translated into another language.

Changing the name of a file (other than as necessitated by the file conventions of the target file systems) is considered to be a modification of the file.

The distribution conditions in this license do not have to be applied to files that have been modified in accordance with the above conditions. Note, however, that Condition 7. does apply to any such modified file.

The conditions above are not intended to prohibit, and hence do not apply to, the updating, by any method, of a file so that it becomes identical to the latest version of that file of The Program.

A Recommendation on Modification Without Distribution

It is wise never to modify a file of The Program, even for your own personal use, without also meeting the above eight conditions for distributing the modified file. While you might intend that such modified files will never be distributed, often this will happen by accident - you may forget that you have modified the file; or it may not occur to you when allowing others to access the modified file that you are thus distributing it and violating the conditions of this license. It is usually in your best interest to keep your copy of The Program identical with the public one. Many programs provide ways to control the behavior of that program without altering its licensed files.

Additional Conditions on Individual Files of The Program

An individual file of The Program may bear additional conditions that supplement and/or supersede the conditions in this license if, and only if, such additional conditions exclusively concern modification of the file or distribution of a modified version of the file. The conditions on individual files of The Program therefore may differ only with respect to the kind and extent of modification of those files that is allowed, and with respect to the distribution of modified versions of those files.

Additional Conditions on LaTeX Software Files

If a file of The Program is intended to be used with LaTeX (that is, if it is a LaTeX software file), then the following additional conditions, which supplement and/or supersede the conditions above, apply to the file according to its filename extension:

* You may not modify any file with filename extension ‘.ins’ since these are installation files containing the legal notices that are placed in the files they generate.

* You may distribute modified versions of files with filename extension ‘.fd’ (LaTeX font definition files) under the standard conditions of the LPPL as described above. You may also distribute such modified LaTeX font definition files with their original names provided that:

(1) the only changes to the original files either enable use of available fonts or prevent attempts to access unavailable fonts;

(2) you also distribute the original, unmodified files (TeX input paths can be used to control which set of LaTeX font definition files is actually used by TeX).

* You may distribute modified versions of files with filename extension ‘.cfg’ (configuration files) with their original names. The Program may (and usually will) specify the range of commands that are allowed in a particular configuration file.

Because of portability and exchangeability issues in LaTeX software, The LaTeX3 Project deprecates the distribution of modified versions of components of LaTeX or of generally available contributed code for them, but such distribution can meet the conditions of this license.

NO WARRANTY

There is no warranty for The Program. Except when otherwise stated in writing, The Copyright Holder provides The Program ‘as is’, without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of The Program is with you. Should The Program prove defective, you assume the cost of all necessary servicing, repair, or correction.

In no event unless agreed to in writing will The Copyright Holder, or any author named in the files of The Program, or any other party who may distribute and/or modify The Program as permitted above, be liable to you for damages, including any general, special, incidental or consequential damages arising out of any use of The Program or out of inability to use The Program (including, but not limited to, loss of data, data being rendered inaccurate, or losses sustained by anyone as a result of any failure of The Program to operate with any other programs), even if The Copyright Holder or said author or said other party has been advised of the possibility of such damages.

WHETHER AND HOW TO DISTRIBUTE PROGRAMS UNDER THIS LICENSE

This section contains important instructions, examples, and recommendations for authors who are considering distributing their programs under this license. These authors are addressed as ‘you’ in this section.

Choosing This License or Another License

If for any part of your program you want or need to use *distribution* conditions that differ from those in this license, then do not refer to this license anywhere in your program but instead distribute your program under a different license. You may use the text of this license as a model for your own license, but your license should not refer to the LPPL or otherwise give the impression that your program is distributed under the LPPL.

The document ‘modguide.tex’ in the base LaTeX distribution explains the motivation behind the conditions of this license. It explains, for example, why distributing LaTeX under the GNU General Public License (GPL) was considered inappropriate. Even if your program is unrelated to LaTeX, the discussion in ‘modguide.tex’ may still be relevant, and authors intending to distribute their programs under any license are encouraged to read it.

How to Use This License

To use this license, place in each of the files of your program both an explicit copyright notice including your name and the year and also a statement that the distribution and/or modification of the file is constrained by the conditions in this license.

Here is an example of such a notice and statement:

%% pig.dtx

%% Copyright 2001 M. Y. Name

%

% This program may be distributed and/or modified under the

% conditions of the LaTeX Project Public License, either version 1.2

% of this license or (at your option) any later version.

% The latest version of this license is in

% http://www.latex-project.org/lppl.txt

% and version 1.2 or later is part of all distributions of LaTeX

% version 1999/12/01 or later.

%

% This program consists of the files pig.dtx and pig.ins

Given such a notice and statement in a file, the conditions given in this license document would apply, with ‘The Program’ referring to the two files ‘pig.dtx’ and ‘pig.ins’, and ‘The Copyright Holder’ referring to the person ‘M. Y. Name’.

Important Recommendations

Defining What Constitutes The Program

The LPPL requires that distributions of The Program contain all the files of The Program. It is therefore important that you provide a way for the licensee to determine which files constitute The Program. This could, for example, be achieved by explicitly listing all the files of The Program near the copyright notice of each file or by using a line like

% This program consists of all files listed in manifest.txt.

in that place. In the absence of an unequivocal list it might be impossible for the licensee to determine what is considered by you to comprise The Program.

Noting Exceptional Files

If The Program contains any files bearing additional conditions on modification, or on distribution of modified versions, of those files (other than those listed in ‘Additional Conditions on LaTeX Software Files’), then it is recommended that The Program contain a prominent file that defines the exceptional conditions, and either lists the exceptional files or defines one or more categories of exceptional files.

Files containing the text of a license (such as this file) are often examples of files bearing more restrictive conditions on modification. LaTeX configuration files (with filename extension ‘.cfg’) are examples of files bearing less restrictive conditions on the distribution of a modified version of the file. The additional conditions on LaTeX software given above are examples of declaring a category of files bearing exceptional additional conditions.

Last revised on August 10, 2000

24. LGPL

Source: http://www.gnu.org/copyleft/lesser.txt

Note: The license shown below is for reference purposes and does not apply to this document.

GNU LESSER GENERAL PUBLIC LICENSE

Version 2.1, February 1999

Copyright (C) 1991, 1999 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.]

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.

To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.

To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author’s reputation will not be affected by problems that might be introduced by others.

Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs.

When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library.

We call this license the "Lesser" General Public License because it does Less to protect the user’s freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.

For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.

In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.

Although the Lesser General Public License is Less protective of the users’ freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run.

GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you".

A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables.

The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".)

"Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does. 1. You may copy and distribute verbatim copies of the Library’s complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) The modified work must itself be a software library.

b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change.

c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License.

d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful.

(For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.

In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.

Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.

This option is useful when you wish to copy part of the code of the Library into a program that is not a library.

4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.

If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.

5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)

Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.

6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer’s own use and reverse engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:

a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.)

b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user’s computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.

c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.

d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place.

e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy.

For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.

7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things:

a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above.

b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.

8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.

10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients’ exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.

11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.

14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Libraries

If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License).

To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.

<one line to give the library’s name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob’ (a library for tweaking knobs) written by James Random Hacker.

<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice

That’s all there is to it!

25. Lsof Copyright

Source: http://search.mfe.govt.nz/doc/lsof-2.2/copyright

Note: The license shown below is for reference purposes and does not apply to this document.

Copyright 1994 Purdue Research Foundation, West Lafayette, Indiana 47907. All rights reserved.

Written by Victor A. Abell

This software is not subject to any license of the American Telephone and Telegraph Company or the Regents of the University of California.

Permission is granted to anyone to use this software for any purpose on any computer system, and to alter it and redistribute it freely, subject to the following restrictions:

1. Neither the authors nor Purdue University are responsible for any consequences of the use of this software.

2. The origin of this software must not be misrepresented, either by explicit claim or by omission. Credit to the authors and Purdue University must appear in documentation and sources.

3. Altered versions must be plainly marked as such, and must not be misrepresented as being the original software.

4. This notice may not be removed or altered.

26. MITRE License

Source: http://www.opensource.org/licenses/mitrepl.php

Note: The license shown below is for reference purposes and does not apply to this document.

MITRE Collaborative Virtual Workspace License (CVW License)

Collaborative Virtual Workspace License (CVW) License Agreement

General

Redistribution of the CVW software or derived works must reproduce MITRE’s copyright designation and this License in the documentation and/or other materials provided with the distribution. Copyright (c) 1994-1999. The MITRE Corporation (http://www.mitre.org/). All Rights Reserved.

The terms "MITRE" and "The MITRE Corporation" are trademarks of The MITRE Corporation and must not be used to endorse or promote products derived from this software or in redistribution of this software in any form.

The terms "CVW" and "Collaborative Virtual Workspace" are trademarks of The MITRE Corporation and must not be used to endorse or promote products derived from this software without the prior written permission of MITRE. For written permission, please contact [email protected].

UNITED STATES GOVERNMENT RIGHTS: This software was produced for the U.S. Government under Contract No. F19628-99-C-0001, and is subject to the Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation Clause (DFARS) 252.227-7014 (JUN 1995). The Licensee agrees that the US Government will not be charged any license fee and/or royalties related to this software.

Downloaders of the CVW software may choose to have their access to and use of the CVW software governed under either the GNU General Public License (Version 2) or the Mozilla License (Version 1.0). In either case, if you transmit source code improvements or modifications to MITRE, you agree to assign to MITRE copyright to such improvements or modifications, which MITRE will then make available from MITRE’s web site.

If you choose to use the Mozilla License (Version 1.0), please note that because the software in this module was developed using, at least in part, Government funds, the Government has certain rights in the module which apply instead of the Government rights in Section 10 of the Mozilla License. These Government rights DO NOT affect your right to use the module on an Open Source basis as set forth in the Mozilla License. The statement of Government rights which replaces Section 10 of the Mozilla License is stated in Section 4 above.

27. MPL

Source: http://www.mozilla.org/MPL/MPL-1.0.html

Note: The license shown below is for reference purposes and does not apply to this document.

MOZILLA PUBLIC LICENSE
Version 1.1

1. Definitions.

1.0.1. "Commercial Use" means distribution or otherwise making the Covered Code available to a third party.

1.1. "Contributor" means each entity that creates or contributes to the creation of Modifications.

1.2. "Contributor Version" means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor.

1.3. "Covered Code" means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof.

1.4. "Electronic Distribution Mechanism" means a mechanism generally accepted in the software development community for the electronic transfer of data.

1.5. "Executable" means Covered Code in any form other than Source Code.

1.6. "Initial Developer" means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A.

1.7. "Larger Work" means a work which combines Covered Code or portions thereof with code not governed by the terms of this License.

1.8. "License" means this document.

1.8.1. "Licensable" means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein.

1.9. "Modifications" means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is:

A. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications.

B. Any new file that contains any part of the Original Code or previous Modifications.

1.10. "Original Code" means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License.

1.10.1. "Patent Claims" means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor.

1.11. "Source Code" means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor’s choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge.

1.12. "You" (or "Your") means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, "You" includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, "control" means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity.

2. Source Code License.

2.1. The Initial Developer Grant.
The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims:

(a) under intellectual property rights (other than patent or trademark) Licensable by Initial Developer to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, and/or as part of a Larger Work; and

(b) under Patents Claims infringed by the making, using or selling of Original Code, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Code (or portions thereof).

(c) the licenses granted in this Section 2.1(a) and (b) are effective on the date Initial Developer first distributes Original Code under the terms of this License.

(d) Notwithstanding Section 2.1(b) above, no patent license is granted: 1) for code that You delete from the Original Code; 2) separate from the Original Code;  or 3) for infringements caused by: i) the modification of the Original Code or ii) the combination of the Original Code with other software or devices.

2.2. Contributor Grant.
Subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license

(a) under intellectual property rights (other than patent or trademark) Licensable by Contributor, to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code and/or as part of a Larger Work; and

(b) under Patent Claims infringed by the making, using, or selling of  Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: 1) Modifications made by that Contributor (or portions thereof); and 2) the combination of  Modifications made by that Contributor with its Contributor Version (or portions of such combination).

(c) the licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributor first makes Commercial Use of the Covered Code.

(d) Notwithstanding Section 2.2(b) above, no patent license is granted: 1) for any code that Contributor has deleted from the Contributor Version; 2) separate from the Contributor Version; 3) for infringements caused by: i) third party modifications of Contributor Version or ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or 4) under Patent Claims infringed by Covered Code in the absence of Modifications made by that Contributor.

3. Distribution Obligations.

3.1. Application of License.
The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients’ rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5.

3.2. Availability of Source Code.
Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party.

3.3. Description of Modifications.
You must cause all Covered Code to which You contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code.

3.4. Intellectual Property Matters

(a) Third Party Claims.
If Contributor has knowledge that a license under a third party’s intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text file with the Source Code distribution titled "LEGAL" which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If Contributor obtains such knowledge after the Modification is made available as described in Section 3.2, Contributor shall promptly modify the LEGAL file in all copies Contributor makes available thereafter and shall take other steps (such as notifying appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained.

(b) Contributor APIs.
If Contributor’s Modifications include an application programming interface and Contributor has knowledge of patent licenses which are reasonably necessary to implement that API, Contributor must also include this information in the LEGAL file.

(c) Representations.
Contributor represents that, except as disclosed pursuant to Section 3.4(a) above, Contributor believes that Contributor’s Modifications are Contributor’s original creation(s) and/or Contributor has sufficient rights to grant the rights conveyed by this License.

3.5. Required Notices.
You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be likely to look for such a notice. If You created one or more Modification(s) You may add your name as a Contributor to the notice described in Exhibit A. You must also duplicate this License in any documentation for the Source Code where You describe recipients’ rights or ownership rights relating to Covered Code. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer.

3.6. Distribution of Executable Versions.
You may distribute Covered Code in Executable form only if the requirements of Section 3.1-3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients’ rights relating to the Covered Code. You may distribute the Executable version of Covered Code or ownership rights under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient’s rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer.

3.7. Larger Works.
You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code.

4. Inability to Comply Due to Statute or Regulation.

If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it.

5. Application of this License.

This License applies to code to which the Initial Developer has attached the notice in Exhibit A and to related Covered Code.

6. Versions of the License.

6.1. New Versions.
Netscape Communications Corporation ("Netscape") may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number.

6.2. Effect of New Versions.
Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by Netscape. No one other than Netscape has the right to modify the terms applicable to Covered Code created under this License.

6.3. Derivative Works.
If You create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), You must (a) rename Your license so that the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape", "MPL", "NPL" or any confusingly similar phrase do not appear in your license (except to note that your license differs from this License) and (b) otherwise make it clear that Your version of the license contains terms which differ from the Mozilla Public License and Netscape Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.)

7. DISCLAIMER OF WARRANTY.

COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

8. TERMINATION.

8.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive.

8.2. If You initiate litigation by asserting a patent infringement claim (excluding declatory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You file such action is referred to as "Participant") alleging that:

(a) such Participant’s Contributor Version directly or indirectly infringes any patent, then any and all rights granted by such Participant to You under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively, unless if within 60 days after receipt of notice You either: (i) agree in writing to pay Participant a mutually agreeable reasonable royalty for Your past and future use of Modifications made by such Participant, or (ii) withdraw Your litigation claim with respect to the Contributor Version against such Participant. If within 60 days of notice, a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is not withdrawn, the rights granted by Participant to You under Sections 2.1 and/or 2.2 automatically terminate at the expiration of the 60 day notice period specified above.

(b) any software, hardware, or device, other than such Participant’s Contributor Version, directly or indirectly infringes any patent, then any rights granted to You by such Participant under Sections 2.1(b) and 2.2(b) are revoked effective as of the date You first made, used, sold, distributed, or had made, Modifications made by that Participant.

8.3. If You assert a patent infringement claim against Participant alleging that such Participant’s Contributor Version directly or indirectly infringes any patent where such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the reasonable value of the licenses granted by such Participant under Sections 2.1 or 2.2 shall be taken into account in determining the amount or value of any payment or license.

8.4. In the event of termination under Sections 8.1 or 8.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or any distributor hereunder prior to termination shall survive termination.

9. LIMITATION OF LIABILITY.

UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

10. U.S. GOVERNMENT END USERS.

The Covered Code is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documentation," as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with only those rights set forth herein.

11. MISCELLANEOUS.

This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in the United States of America, any litigation relating to this License shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys’ fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License.

12. RESPONSIBILITY FOR CLAIMS.

As between Initial Developer and the Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability.

13. MULTIPLE-LICENSED CODE.

Initial Developer may designate portions of the Covered Code as "Multiple-Licensed". "Multiple-Licensed" means that the Initial Developer permits you to utilize portions of the Covered Code under Your choice of the MPL or the alternative licenses, if any, specified by the Initial Developer in the file described in Exhibit A.

EXHIBIT A - Mozilla Public License.

The contents of this file are subject to the Mozilla Public License Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.mozilla.org/MPL/

Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License.

The Original Code is ____________.

The Initial Developer of the Original Code is ____________ Portions created by __________ are Copyright (C) ____________ ____________. All Rights Reserved.

Contributor(s): ____________.

Alternatively, the contents of this file may be used under the terms of the ____ license (the "[____] License"), in which case the provisions of [____] License are applicable instead of those above. If you wish to allow use of your version of this file only under the terms of the [____] License and not to allow others to use your version of this file under the MPL, indicate your decision by deleting the provisions above and replace them with the notice and other provisions required by the [____] License. If you do not delete the provisions above, a recipient may use your version of this file under either the MPL or the [____] License.

[NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the Source Code files of the Original Code. You should use the text of this Exhibit A rather than the text found in the Original Code Source Code for Your Modifications.]

28. OpenMap License

Source: http://openmap.bbn.com/license.html

Note: The license shown below is for reference purposes and does not apply to this document.

OpenMap Software License Agreement

This Agreement sets forth the terms and conditions under which the software known as OpenMap(tm) will be licensed by BBN Technologies ("BBN") to you ("Licensee"), and by which Derivative Works (as hereafter defined) of OpenMap will be licensed by you to BBN.

Definitions:

"Derivative Work(s)" shall mean any revision, enhancement, modification, translation, abridgement, condensation or expansion created by Licensee or BBN that is based upon the Software or a portion thereof that would be a copyright infringement if prepared without the authorization of the copyright owners of the Software or portion thereof.

"OpenMap" shall mean a programmer’s toolkit for building map based applications as originally created by BBN, and any Derivative Works thereof as created by either BBN or Licensee, but shall include only those Derivative Works BBN has approved for inclusion into, and BBN has integrated into OpenMap.

"Standard Version" shall mean OpenMap, as originally created by BBN.

"Software" shall mean OpenMap and the Derivative Works created by Licensee and the collection of files distributed by the Licensee with OpenMap, and the collection of files created through textual modifications.

"Copyright Holder" is whoever is named in the copyright or copyrights for the Derivative Works.

"Licensee" is you, only if you agree to be bound by the terms and conditions set forth in this Agreement.

"Reasonable copying fee" is whatever you can justify on the basis of media cost, duplication charges, time of people involved.

"Freely Available" means that no fee is charged for the item itself, though there may be fees involved in handling the item. It also means that recipients of the item may redistribute it under the same conditions that they received it.

1. BBN maintains all rights, title and interest in and to OpenMap, including all applicable copyrights, trade secrets, patents and other intellectual rights therein. Licensee hereby grants to BBN all right, title and interest into the compilation of OpenMap. Licensee shall own all rights, title and interest into the Derivative Works created by Licensee (subject to the compilation ownership by BBN).

2. BBN hereby grants to Licensee a royalty free, worldwide right and license to use, copy, distribute and make Derivative Works of OpenMap, and sublicensing rights of any of the foregoing in accordance with the terms and conditions of this Agreement, provided that you duplicate all of the original copyright notices and associated disclaimers.

3. Licensee hereby grants to BBN a royalty free, worldwide right and license to use, copy, distribute and make Derivative Works of Derivative Works created by Licensee and sublicensing rights of any of the foregoing.

4. Licensee’s right to create Derivative Works in the Software is subject to Licensee agreement to insert a prominent notice in each changed file stating how and when you changed that file, and provided that you do at least ONE of the following:

a) place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or placing the modifications on a major archive site and by providing your modifications to the Copyright Holder.

b) use the modified Package only within your corporation or organization.

c) rename any non-standard executables so the names do not conflict with standard executables, which must also be provided, and provide a separate manual page for each non-standard executable that clearly documents how it differs from OpenMap.

d) make other distribution arrangements with the Copyright Holder.

5. Licensee may distribute the programs of this Software in object code or executable form, provided that you do at least ONE of the following:

a) distribute an OpenMap version of the executables and library files, together with instructions (in the manual page or equivalent) on where to get OpenMap.

b) accompany the distribution with the machine-readable source code with your modifications.

c) accompany any non-standard executables with their corresponding OpenMap executables, giving the non-standard executables non-standard names, and clearly documenting the differences in manual pages (or equivalent), together with instructions on where to get OpenMap.

d) make other distribution arrangements with the Copyright Holder.

6. You may charge a reasonable copying fee for any distribution of this Software. You may charge any fee you choose for support of this Software. You may not charge a fee for this Software itself. However, you may distribute this Software in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this Software as a product of your own.

7. The data and images supplied as input to or produced as output from the Software do not automatically fall under the copyright of this Software, but belong to whomever generated them, and may be sold commercially, and may be aggregated with this Software.

8. BBN makes no representation about the suitability of OpenMap for any purposes. BBN shall have no duty or requirement to include any Derivative Works into OpenMap.

9. Each party hereto represents and warrants that they have the full unrestricted right to grant all rights and licenses granted to the other party herein.

10. THIS PACKAGE IS PROVIDED "AS IS" WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING (BUT NOT LIMITED TO) ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, AND WITHOUT ANY WARRANTIES AS TO NONINFRINGEMENT.

11. IN NO EVENT SHALL COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE OF DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS CONDUCT, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS PACKAGE.

12. Without limitation of the foregoing, You agree to commit no act which, directly or indirectly, would violate any U.S. law, regulation, or treaty, or any other international treaty or agreement to which the United States adheres or with which the United States complies, relating to the export or re-export of any commodities, software, or technical data.

29. OpenSSL License

Source: http://www.telnetsoftware.com/openssl.htm

Note: The license shown below is for reference purposes and does not apply to this document.

OpenSSL License

Copyright (c) 1998-2000 The OpenSSL Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org)

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected]

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This product includes cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim Hudson ([email protected]).

 

SSLeay license

Copyright (C) 1995-1998 Eric Young ([email protected]) All rights reserved. This package is an SSL implementation written by Eric Young ([email protected]). The implementation was written so as to conform with Netscape’s SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson ([email protected]).

Copyright remains Eric Young’s, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young ([email protected])". The word ‘cryptographic’ can be left out if the routines from the library being used are not cryptographic related :-).

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson ([email protected])"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU General Public License].

30. PHP License

Source: http://www.php.net/license/3_0.txt

Note: The license shown below is for reference purposes and does not apply to this document.

The PHP License, version 3.0

Copyright (c) 1999 - 2002 The PHP Group. All rights reserved.

---------------------------------------------------------------------------------------------------------------------

Redistribution and use in source and binary forms, with or without modification, is permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. The name "PHP" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

4. Products derived from this software may not be called "PHP", nor may "PHP" appear in their name, without prior written permission from [email protected] . You may indicate that your software works in conjunction with PHP by saying "Foo for PHP" instead of calling it "PHP Foo" or "phpfoo"

5. The PHP Group may publish revised and/or new versions of the license from time to time. Each version will be given a distinguishing version number. Once covered code has been published under a particular version of the license, you may always continue to use it under the terms of that version. You may also choose to use such covered code under the terms of any subsequent version of the license published by the PHP Group. No one other than the PHP Group has the right to modify the terms applicable to covered code created under this License.

6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes PHP, freely available from http://www.php.net/ ".

THIS SOFTWARE IS PROVIDED BY THE PHP DEVELOPMENT TEAM ``AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PHP DEVELOPMENT TEAM OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---------------------------------------------------------------------------------------------------------------------

This software consists of voluntary contributions made by many individuals on behalf of the PHP Group.

The PHP Group can be contacted via Email at [email protected] .

For more information on the PHP Group and the PHP project, please see http://www.php.net .

This product includes the Zend Engine, freely available at http://www.zend.com .

31. Public Domain (Expect)

Source: http://expect.nist.gov/FAQ.html#q5

Note: The license shown below is for reference purposes and does not apply to this document.

Expect FAQ (Frequently Asked Questions)

…

I keep hearing about Expect. So what is it?

…

Expect is free and in the public domain…

…

Do we need to pay or ask for permission to distribute Expect?

It is my understanding that you are allowed to do just about anything with Expect. You can even sell it. You need not ask our permission. You need not pay for it. (Your tax dollars, in effect, already have paid for it.)

You should not claim that you wrote it (since this would be a lie), nor should you attempt to copyright it (this would be fruitless as it is a work of the US government and therefore not subject to copyright).

NIST lawyers declined to supply a formal response but verbally told me that there is a law stating that NIST’s name may not be used to imply (however indirectly) that NIST’s association with Expect somehow makes your software product better. For simplicity, just leave NIST’s name off. You may, of course, credit me personally and I certainly encourage that. One line suffices (as far as I’m concerned) although there should be something to the effect that no warrantee, guarantee, or liability is implied. If you have further legal questions, please contact Melissa Lieberman (http://www.nist.gov/cgi-bin/wwwph?melissa+lieberman ).

32. Qmail License

Source: http://cr.yp.to/qmail/dist.html

Note: The license shown below is for reference purposes and does not apply to this document.

Information for distributors

If you’re a distributor, you should join the qmaildist mailing list .

You may distribute copies of

qmail-1.00.tar.gz, with MD5 checksum d3033be700fd6f59ac0548c832652dd3.

You may distribute copies of

qmail-1.01.tar.gz, with MD5 checksum 1f606d6a5d1caaca6da6b6fa5db500bf.

You may distribute copies of

qmail-1.02.tar.gz, with MD5 checksum 01071fe52b5257adb4bb6bcf8149eb16.

You may distribute copies of

qmail-1.03.tar.gz, with MD5 checksum 622f65f982e380dbe86e6574f3abcb7c.

Vendors: I’d be interested in hearing about any CDs that include the package, but you don’t have to check with me if you don’t want to.

If you want to distribute modified versions of qmail (including ports, no matter how minor the changes are) you’ll have to get my approval. This does not mean approval of your distribution method, your intentions, your e-mail address, your haircut, or any other irrelevant information. It means a detailed review of the exact package that you want to distribute.

Exception: You are permitted to distribute a precompiled var-qmail package if

(1) installing the package produces exactly the same /var/qmail hierarchy as a user would obtain by downloading, compiling, and installing qmail-1.03.tar.gz, fastforward-0.51.tar.gz, and dot-forward-0.71.tar.gz;

(2) the package behaves correctly, i.e., the same way as normal qmail+fastforward+dot-forward installations on all other systems; and

(3) the package’s creator warrants that he has made a good-faith attempt to ensure that the package behaves correctly.

It is not acceptable to have qmail working differently on different machines; any variation is a bug. If there’s something about a system (compiler, libraries, kernel, hardware, whatever) that changes qmail’s behavior, then that platform is not supported, and you are not permitted to distribute binaries.

33. RTLinux Open Patent License Version 2

Source: http://www.fsmlabs.com/openpatentlicense.html

Note: The license shown below is for reference purposes and does not apply to this document.

The Open RTLinux Patent License Version 2.0

The Open RTLinux Patent License ("License" or "Agreement") governs the royalty-free use of the process defined by U.S. Patent No. 5,995,745. Anyone can license the use of the Patented Process (as defined below) by agreeing to be bound by the terms of this License. Such person is considered to be the Licensee ("Licensee"). The Patented Process may be used, without any payment of a royalty, with two (2) types of software. The first type is software that operates under the terms of a GPL (as defined below). The second type is software operating under an Open RTLinux Execution Environment (as defined below). As long as the Licensee complies with the terms and conditions of this License and, where applicable, with the terms of the GPL, the Licensee may continue to use the Patented Process without paying a royalty for its use. You may use the Patented Process with software other than the two types mentioned above but you must first obtain a separate license for such use. The first step is to contact Finite State Machine Labs, Inc. (http://www.fsmlabs.com)

Definitions

1. "Patented Process" means the process covered by U.S. Patent No. 5,995,745, issued November 30, 1999 and entitled ADDING REAL-TIME SUPPORT TO GENERAL PURPOSE OPERATING SYSTEMS.

2. "License" means this License in its entirety, also known as the Open RTLinux Patent License Version 2.0.

3. "Licensor" means Victor Yodaiken, the inventor and co-owner of U.S. Patent No. 5,995,745, and Finite State Machine Labs, Inc., the other co-owner of the patent.

4. "You" means any person or entity that makes use of the Patented Process or agrees to be bound by provisions of this License ("Licensee").

5. "GPL" means The Free Software Foundation’s General Public License Version 2.

6. "Open RTLinux Software" means unmodified software labeled "Open RTLinux code" by Finite State Machine Labs, Inc. and:

A. In the case of a binary distribution, the complete set of executable programs, including linked files and any and all other accompanying files, such as documentation;

B. In the case of an installation for use, the complete set of executable programs, any linked files, any attached files and any and all other accompanying files, such as documentation;

C. In the case of a source distribution, the complete set of unmodified source files, and any and all documentation included with the source code.

7. "Open RTLinux Execution Environment" means: A computer hardware system where the interrupt control hardware of processors and system boards is under the direct control of unmodified Open RTLinux Software in binary form. Configuration by a Licensee using the configuration tools provided by Licensor is not considered a modification unless such configuration includes a change to Open RTLinux code that is not provided as an option through the configuration tool.

Approved Use

In addition to the other terms and conditions of this License, use of the Patented Process is permitted, without fee or royalty, when used: A. By software licensed under the GPL; or B. By software that executes within an Open RTLinux Execution Environment - whether that software is licensed under the GPL or not.

Your Obligations

1. Any use of the Patented Process must include labeling the product or service that includes the Patented Process with the following language: "Used, under license, U.S. Patent No. 5,995,745."

2. A copy of these conditions and terms must be attached to or included with any distribution of any product or service that uses the Patented Process. It must be made clear to anyone that uses your product or service that all subsequent uses must also comply with the conditions and terms of this License and (where appropriate) the GPL.

3. If you are using this Patented Process according to the conditions of this License for GPL software and you are distributing or otherwise making your software available outside your company then you must not place any artificial impediments to free access to your software source code. If you distribute your software or market your software through some web site on the World-Wide-Web, you must make source code for the software that makes use of the Patented Process immediately available on the World-Wide-Web for all to access. Any subsequent use must comply strictly with the terms of the GPL and with this License. Failure to comply with the terms of the GPL will result in an automatic termination of this License.

4. Open RTLinux Software is released under the GPL and you must comply with the terms of the GPL where applicable. Any modification of Open RTLinux code outside of the terms of the GPL is considered a material breach of this license. Any modification of Open RTLinux code results in code that is not "Open RTLinux code" in the terms of this license and this code cannot be used under the provisions of the section on Approved Use, subparagraph (B) above.

5. All notices, requests, demands, and other communications shall be in writing and sent by electronic mail and by facsimile, nationally recognized overnight carrier, or certified mail, postage prepaid, to: Victor J. Yodaiken Finite State Machine Labs, Inc. 115-D Abeyta Avenue Socorro, New Mexico 87801 Facsimile: (505) 838-9112 email: [email protected]

6. This Agreement is the entire agreement between the parties with respect to this subject matter.

7. This Agreement shall be governed by the laws of the State of New Mexico, without giving effect to principles of conflicts of law. In addition, any action or proceeding arising from or relating to this Agreement, except for actions solely relating to issues regarding compliance with or interpretation of the GPL, must be brought in a federal court in New Mexico. Each party irrevocably submits to the jurisdiction of venue of any such court.

8. Licensor shall have no liability for any direct, indirect, incidental, special, exemplary, punitive, consequential, or other damages, including without limitation, loss of profit or business opportunities, however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise), whether or not advised of the possibility of such damages. Licensor expressly disclaims any representations or warranties, expressed or implied, regarding the product or services contemplated by this Agreement, including, but not limited to, any implied warranty of merchantability or fitness for a particular purpose. The products and services contemplated by this Agreement are provided "as is" without warranty of any kind, either expressed or implied. The entire risk as to the quality and performance of the products and services contemplated by this Agreement are with the Licensee. Each Licensee under this Agreement assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs, or equipment, and unavailability or interruption of operations.

Termination and Limitations

1. This Agreement shall commence as of the date this Agreement is executed by both parties and shall remain in full force and effect until Three-Hundred-and-Sixty-Five (365) calendar days from the date of execution subject to prior termination as provided below. Execution shall be deemed complete as of the moment the Licensee acknowledges acceptance of all terms of this Agreement by clicking on the "I agree" icon found on Licensor’s web site (http://www.fsmlabs.com) or by sending written confirmation of acceptance by electronic mail to [email protected]. Execution of this license shall also be deemed complete upon your first use of the software licensed under the GPL in accordance with Section 1.A. of this Agreement, without registering acceptance with the Licensor. Unless this Agreement is terminated as provided below, this Agreement shall automatically renew for periods of Three-Hundred-and-Sixty-Five (365) calendar days each until the expiration of the U.S. Patent on the Licensed Process.

2. The Licensor owns all right, title and interest to the patent. The Licensor is not obligated to defend or indemnify any Licensee against any suit, damage, claim or allegation of patent infringement resulting from any use of the Patented Process. In the event of any such occurrence, the Licensor will cooperate with Licensee, at Licensee’s expense.

3. The term of this License will be limited by compliance of the Licensee. If you do not comply with the conditions and terms of this License, the License will be automatically terminated and all use of the Patented Process must stop.

4. Licensee acknowledges that no other representations by Licensor exist and that no other agreements exist between Licensee and Licensor. This Agreement will be construed and interpreted according to the laws of the State of New Mexico.

Dated: October 5 2001.

The end

34. SATAN License

Source: http://www-arc.com/sara/copyright.html

Note: The license shown below is for reference purposes and does not apply to this document.

Copyright

SARA Unique Software

SARA unique software (SUS) copyright by Advanced Research Corporation 1999. All SUS is covered by the SATAN license below.

SATAN Software

Copyright 1995 by Dan Farmer and Wietse Venema. All rights reserved. Some individual files may be covered by other copyrights (this will be noted in the file itself.)

Redistribution and use in source and binary forms are permitted provided that this entire copyright notice is duplicated in all such copies. No charge, other than an "at-cost" distribution fee, may be charged for copies, derivations, or distributions of this material without the express written consent of the copyright holders.

THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR ANY PARTICULAR PURPOSE.

IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, LOSS OF USE, DATA, OR PROFITS OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

35. Sendmail License

Source: ftp://ftp.sendmail.org/pub/sendmail/LICENSE

Note: The license shown below is for reference purposes and does not apply to this document.

SENDMAIL LICENSE

The following license terms and conditions apply, unless a different license is obtained from Sendmail, Inc., 6425 Christie Ave, Fourth Floor, Emeryville, CA 94608, or by electronic mail at [email protected].

License Terms:

Use, Modification and Redistribution (including distribution of any modified or derived work) in source and binary forms is permitted only if each of the following conditions is met:

1. Redistributions qualify as "freeware" or "Open Source Software" under one of the following terms:

(a) Redistributions are made at no charge beyond the reasonable cost of materials and delivery.

(b) Redistributions are accompanied by a copy of the Source Code or by an irrevocable offer to provide a copy of the Source Code for up to three years at the cost of materials and delivery. Such redistributions must allow further use, modification, and redistribution of the Source Code under substantially the same terms as this license. For the purposes of redistribution "Source Code" means the complete compilable and linkable source code of sendmail including all modifications.

2. Redistributions of source code must retain the copyright notices as they appear in each source code file, these license terms, and the disclaimer/limitation of liability set forth as paragraph 6 below.

3. Redistributions in binary form must reproduce the Copyright Notice, these license terms, and the disclaimer/limitation of liability set forth as paragraph 6 below, in the documentation and/or other materials provided with the distribution. For the purposes of binary distribution the "Copyright Notice" refers to the following language: "Copyright (c) 1998-2002 Sendmail, Inc. All rights reserved."

4. Neither the name of Sendmail, Inc. nor the University of California nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission. The name "sendmail" is a trademark of Sendmail, Inc.

5. All redistributions must comply with the conditions imposed by the University of California on certain embedded code, whose copyright notice and conditions for redistribution are as follows:

(a) Copyright (c) 1988, 1993 The Regents of the University of California. All rights reserved.

(b) Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

(i) Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

(ii) Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

(iii) Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

6. Disclaimer/Limitation of Liability: THIS SOFTWARE IS PROVIDED BY SENDMAIL, INC. AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SENDMAIL, INC., THE REGENTS OF THE UNIVERSITY OF CALIFORNIA OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Revision: 8.11, Last updated 2002/04/24 22:26:56

36. TCP Wrappers License

Source: ftp://ftp.porcupine.org/pub/security/tcp_wrappers_license

Note: The license shown below is for reference purposes and does not apply to this document.

Copyright 1995 by Wietse Venema. All rights reserved. Some individual files may be covered by other copyrights.

This material was originally written and compiled by Wietse Venema at Eindhoven University of Technology, The Netherlands, in 1990, 1991, 1992, 1993, 1994 and 1995.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that this entire copyright notice is duplicated in all such copies.

This software is provided "as is" and without any expressed or implied warranties, including, without limitation, the implied warranties of merchantability and fitness for any particular purpose.

37. Vovida Software License

Source: http://www.vovida.org/license.html

Note: The license shown below is for reference purposes and does not apply to this document.

Vovida Software License

The Vovida Software License, Version 1.0
Copyright (c) 2000 Vovida Networks, Inc. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. The names "VOCAL", "Vovida Open Communication Application Library", and "Vovida Open Communication Application Library (VOCAL)" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

4. Products derived from this software may not be called "VOCAL", nor may "VOCAL" appear in their name, without prior written permission.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT ARE DISCLAIMED. IN NO EVENT SHALL VOVIDA NETWORKS, INC. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DAMAGES IN EXCESS OF $1,000, NOR FOR ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

38. VTK Copyright

Source: http://www.vtk.org/copyright.php

Note: The license shown below is for reference purposes and does not apply to this document.

The Visualization Toolkit (VTK) Copyright

This is an open-source copyright as follows:

Copyright (c) 1993-2002 Ken Martin, Will Schroeder, Bill Lorensen. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* Neither name of Ken Martin, Will Schroeder, or Bill Lorensen nor the names of any contributors may be used to endorse or promote products derived from this software without specific prior written permission.

* Modified source versions must be plainly marked as such, and must not be misrepresented as being the original software.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

39. WU-FTPD Software License

Source: http://www.wu-ftpd.org/license.html

Note: The license shown below is for reference purposes and does not apply to this document.

WU-FTPD SOFTWARE LICENSE

Use, modification, or redistribution (including distribution of any modified or derived work) in any form, or on any medium, is permitted only if all the following conditions are met:

1. Redistributions qualify as "freeware" or "Open Source Software" under the following terms:

a. Redistributions are made at no charge beyond the reasonable cost of materials and delivery. Where redistribution of this software is as part of a larger package or combined work, this restriction applies only to the costs of materials and delivery of this software, not to any other costs associated with the larger package or combined work.

b. Redistributions are accompanied by a copy of the Source Code or by an irrevocable offer to provide a copy of the Source Code for up to three years at the cost of materials and delivery. Such redistributions must allow further use, modification, and redistribution of the Source Code under substantially the same terms as this license. For the purposes of redistribution "Source Code" means all files included in the original distribution, including all modifications or additions, on a medium and in a form allowing fully working executable programs to be produced.

2. Redistributions of Source Code must retain the copyright notices as they appear in each Source Code file and the COPYRIGHT file, these license terms, and the disclaimer/limitation of liability set forth as paragraph 6 below.

3. Redistributions in binary form must reproduce the Copyright Notice, these license terms, and the disclaimer/limitation of liability set forth as paragraph 6 below, in the documentation and/or other materials provided with the distribution. For the purposes of binary distribution the "Copyright Notice" refers to the following language:

Copyright (c) 1999,2000,2001 WU-FTPD Development Group.
All rights reserved.

Portions Copyright (c) 1980, 1985, 1988, 1989, 1990, 1991, 1993, 1994 The Regents of the University of California.

Portions Copyright (c) 1993, 1994 Washington University in Saint Louis.

Portions Copyright (c) 1996, 1998 Berkeley Software Design, Inc.

Portions Copyright (c) 1998 Sendmail, Inc.

Portions Copyright (c) 1983, 1995, 1996, 1997 Eric P. Allman.

Portions Copyright (c) 1989 Massachusetts Institute of Technology.

Portions Copyright (c) 1997 Stan Barber.

Portions Copyright (c) 1991, 1992, 1993, 1994, 1995, 1996, 1997 Free Software Foundation, Inc.

Portions Copyright (c) 1997 Kent Landfield.

Use and distribution of this software and its source code are governed by the terms and conditions of the WU-FTPD Software License ("LICENSE").

If you did not receive a copy of the license, it may be obtained online at http://www.wu-ftpd.org/license.html

4. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes software developed by the WU-FTPD Development Group, the Washington University at Saint Louis, Berkeley Software Design, Inc., and their contributors."

5. Neither the name of the WU-FTPD Development Group, nor the names of any copyright holders, nor the names of any contributors may be used to endorse or promote products derived from this software without specific prior written permission. The names "wuftpd" and "wu-ftpd" are trademarks of the WU-FTPD Development Group and the Washington University at Saint Louis.

6. Disclaimer/Limitation of Liability:

THIS SOFTWARE IS PROVIDED BY THE WU-FTPD DEVELOPMENT GROUP, THE COPYRIGHT HOLDERS, AND CONTRIBUTORS, "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE WU-FTPD DEVELOPMENT GROUP, THE COPYRIGHT HOLDERS, OR CONTRIBUTORS, BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7. USE, MODIFICATION, OR REDISTRIBUTION, OF THIS SOFTWARE IMPLIES ACCEPTANCE OF ALL TERMS AND CONDITIONS OF THIS LICENSE.

40. XFree86 License

Source: http://www.xfree86.org/current/LICENSE1.html

Note: The license shown below is for reference purposes and does not apply to this document.

1. XFree86 License

XFree86 code without an explicit copyright is covered by the following copyright/license:

Copyright (C) 1994-2002 The XFree86 Project, Inc. All Rights Reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of the XFree86 Project shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the XFree86 Project.

41. X/MIT License

Source: http://www.xfree86.org/current/LICENSE2.html#3

Note: The license shown below is for reference purposes and does not apply to this document.

Copyright (C) <date> X Consortium

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium.

X Window System is a trademark of X Consortium, Inc.

42. zlib License

Source: http://www.gzip.org/zlib/zlib_license.html

Note: The license shown below is for reference purposes and does not apply to this document.

zlib License

version 1.1.4, March 11th, 2002

Copyright (C) 1995-2002 Jean-loup Gailly and Mark Adler

This software is provided ‘as-is’, without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

Jean-loup Gailly [email protected]

Mark Adler [email protected]

43. ZPL

Source: http://www.zope.org/Resources/ZPL

Note: The license shown below is for reference purposes and does not apply to this document.

Zope Public License (ZPL) Version 2.0

This software is Copyright (c) Zope Corporation (tm) and Contributors. All rights reserved.

This license has been certified as open source. It has also been designated as GPL compatible by the Free Software Foundation (FSF).

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions in source code must retain the above copyright notice, this list of conditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. The name Zope Corporation (tm) must not be used to endorse or promote products derived from this software without prior written permission from Zope Corporation.

4. The right to distribute this software or to use it for any purpose does not give you the right to use Servicemarks (sm) or Trademarks (tm) of Zope Corporation. Use of them is covered in a separate agreement (see http://www.zope.com/Marks).

5. If any files are modified, you must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

Disclaimer

THIS SOFTWARE IS PROVIDED BY ZOPE CORPORATION "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ZOPE CORPORATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of contributions made by Zope Corporation and many individuals on behalf of Zope Corporation. Specific attributions are listed in the accompanying credits file.

44. Other FOSS-Related Licenses
1. Microsoft MIT EULA (Proprietary)

Source: http://msdn.microsoft.com/downloads/eula_mit.htm

This non-open-source proprietary license includes restrictions on FOSS licenses.

Note: The license shown below is for reference purposes and does not apply to this document.

Please read the following license agreement. Use the scroll bar to see the rest of the agreement.

This is a legal agreement ("Agreement") between you (either an individual or an entity), the end user ("Recipient"), and Microsoft Corporation ("Microsoft"). BY INSTALLING, COPYING OR OTHERWISE USING THE SOFTWARE (AS DEFINED BELOW), YOU AGREE TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, DO NOT INSTALL, COPY OR USE THE SOFTWARE.

MICROSOFT CORPORATION LICENSE AGREEMENT FOR PRERELEASE SOFTWARE Microsoft Mobile Internet Toolkit Beta 2

Accompanying this Agreement is a prerelease copy of the Microsoft software identified above, which includes software and related documentation and information (collectively the "Software"). The Software is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The Software is licensed, not sold.

1. GRANT OF LICENSE; RESTRICTIONS; ACKNOWLEDGEMENT. This Agreement grants Recipient the following rights provided that Recipient complies with all terms and conditions of this Agreement:

(a) License Grant for Internal Use; Applications. Microsoft grants to Recipient a limited, non-exclusive, nontransferable, royalty-free license to install and use unlimited copies of the executable code of the Software on any number of CPUs residing on Recipient’s premises running validly licensed copies of both Microsoft Windows 2000 and the Microsoft .Net Framework (each a server), solely

(i) to test the compatibility of Recipient’s application or other product(s) which operate in conjunction with the Software and to evaluate the Software for the purpose of providing feedback thereon to Microsoft, and

(ii) to develop software applications ("Applications") for use in accordance with Section 3 of this Agreement. All other rights are reserved to Microsoft except as expressly provided herein.

(b) License to Device Adapter Code. In addition to the rights granted in Section 1(a), Microsoft grants to Recipient the right to use, copy and modify the source code version of those portions of the Software identified as "Device Adapter Code" ("Device Adapter Code") for the sole purposes of designing, developing, and testing Recipient’s Applications, and to reproduce and distribute the Device Adapter Code, along with any modifications thereof, solely in object code form as a part of Recipient’s Applications in accordance with Section 3 of this Agreement. In addition to the conditions set forth in Section 3 of this Agreement, the foregoing license is subject to the following conditions:

(i) any modifications or derivatives made by Recipient to the Device Adapter Code shall only be used in conjunction with the Software; and

(ii) Recipient shall not distribute the Device Adapter Code, or any portion thereof, on a stand-alone basis or otherwise permit further distribution of the Device Adapter Code and/or derivatives thereof by third parties.

(c) Open Source. Recipient’s license rights to the Software are conditioned upon Recipient

(i) not distributing such Software, in whole or in part, in conjunction with Potentially Viral Software (as defined below); and

(ii) not using Potentially Viral Software (e.g. tools) to develop Recipient software which includes the Software, in whole or in part. For purposes of the foregoing, "Potentially Viral Software" means software which is licensed pursuant to terms that:

(x) create, or purport to create, obligations for Microsoft with respect to the Software or

(y) grant, or purport to grant, to any third party any rights to or immunities under Microsoft’s intellectual property or proprietary rights in the Software. By way of example but not limitation of the foregoing, Recipient shall not distribute the Software, in whole or in part, in conjunction with any Publicly Available Software. "Publicly Available Software" means each of

(i) any software that contains, or is derived in any manner (in whole or in part) from, any software that is distributed as free software, open source software (e.g. Linux) or similar licensing or distribution models; and

(ii) any software that requires as a condition of use, modification and/or distribution of such software that other software distributed with such software

(A) be disclosed or distributed in source code form;

(B) be licensed for the purpose of making derivative works; or

(C) be redistributable at no charge. Publicly Available Software includes, without limitation, software licensed or distributed under any of the following licenses or distribution models, or licenses or distribution models similar to any of the following:

(A) GNU’s General Public License (GPL) or Lesser/Library GPL (LGPL),

(B) The Artistic License (e.g., PERL),

(C) the Mozilla Public License,

(D) the Netscape Public License,

(E) the Sun Community Source License (SCSL), and

(F) the Sun Industry Standards License (SISL).

(d) ACKNOWLEDGEMENT. All other rights are reserved to Microsoft. Recipient shall not rent, lease, sell, sublicense, assign, or otherwise transfer any portion of the Software. Recipient may not reverse engineer, decompile or disassemble any portion of the Software, except and only to the extent that this limitation is expressly prohibited by applicable law notwithstanding this limitation.

2. FEEDBACK. Recipient agrees to provide reasonable feedback to Microsoft, including but not limited to usability, bug reports and test results, with respect to Software testing. All bug reports, test results and other feedback provided to Microsoft by Recipient shall be the property of Microsoft and may be used by Microsoft for any purpose. Due to the nature of the development work, Microsoft provides no assurance that any specific errors or discrepancies in the Software will be corrected. Recipient may not use the Software in a live operating environment with data that has not been sufficiently backed up.

3. APPROVED USES OF APPLICATIONS.

(a) Except as provided in Subsection 3(b), Recipient may only use Applications on an internal basis for non-production purposes only and may not distribute or license the Applications to third parties or make the Applications available for use by any third party.

(b) Recipient may deploy and make Applications available for use by third parties via the Internet provided that for the purposes of such deployment, the Application is hosted by an Approved Hoster. The list of Approved Hosters is available within the Visual Studio.Net software product, on the Visual Studio.NET Start page, in the Web Hosting Section. The Approved Hoster may require a separate hosting agreement with the Recipient and Microsoft disclaims all liability related to any agreements or services provided by the Approved Hoster. In addition, Recipient agrees

(i) to promptly upgrade to and obtain a license for the commercially released version of the Software when it becomes generally available to the public;

(ii) to install all updates as "mandatory updates" by Microsoft within 2 business days of receipt of such updates (all updates delivered to Recipient by Microsoft shall be subject to this Agreement);

(iii) that Recipient is solely responsible for updating its customers with versions of Applications that operate satisfactorily with the final commercially released version of the Software;

(iv) not to use Microsoft’s name, logo, or trademarks to market the Application, provided however, that any Application that includes the Device Adapter Code or any derivatives thereof must include a clear statement indicating that such Application is based upon the Microsoft Mobile Internet Toolkit;

(v) to include a valid copyright notice on the Applications in Recipient’s name;

(vi) to indemnify and hold harmless Microsoft from and against any claims or lawsuits, including attorneys’ fees, that arise from or result from the use or deployment of the Application;

(vii) to otherwise comply with the terms of this EULA; and

(viii) that Microsoft reserves all rights not expressly granted.

4. TERM OF AGREEMENT. The term of this Agreement shall commence on the date accepted by Recipient and shall continue until terminated by Microsoft in writing at any time, with or without cause. This Agreement will terminate without notice upon the earlier of

(i) commercial release of the Software or

(ii) one year after the last date Recipient receives the Software or any Update thereto, unless terminated earlier by Microsoft.

Upon the termination of this Agreement (or upon request by Microsoft), Recipient shall promptly return to Microsoft, or certify destruction of, all full or partial copies of the Software provided by Microsoft. The following Sections shall survive termination or expiration of this Agreement: Sections 2, 7, 8, 9, 10 and 11.

5. COST OF TESTING. There is no charge to Recipient for testing of the Software.

6. MAINTENANCE/UPDATES. Microsoft is not obligated to provide maintenance, technical support or updates to Recipient for the Software provided to Recipient pursuant to this Agreement or to provide any support with respect to the Applications. However, Microsoft may, in its sole discretion, provide further pre-release versions, technical support, updates and/or supplements of the Software and/or related information ("Updates") to Recipient hereunder, in which case such Updates shall also be deemed to be included in the "Software" and therefore governed by this Agreement, unless other terms of use are provided by Microsoft with such Updates. In no event shall Microsoft be obligated to provide Recipient a copy of the commercial release version of the Software in connection with Recipient’s participation in the testing program. Microsoft is not obligated to make the Software commercially available.

7. INTELLECTUAL PROPERTY RIGHTS. All title and intellectual property rights in and to the Software (including but not limited to any images, photographs, animations, video, audio, music, text and "applets" incorporated into the Software), and any copies of the Software that Recipient is expressly permitted to make herein, are owned by Microsoft or its suppliers. All title and intellectual property rights in and to the content that may be accessed through use of the Software are the property of the respective content owner and may be protected by applicable copyright or other intellectual property laws and treaties. This Agreement grants Recipient no rights to use such content. If the Software contains documentation that is provided only in electronic form, Recipient may print one copy of such electronic documentation. Recipient may not copy the printed materials accompanying the Software. Microsoft reserves all rights not expressly granted.

8. DISCLAIMER OF WARRANTIES. THE SOFTWARE IS DEEMED ACCEPTED BY RECIPIENT. THE SOFTWARE CONTAINS PRE-RELEASE SOFTWARE AND MAY BE CHANGED SUBSTANTIALLY BEFORE COMMERCIAL RELEASE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND ITS SUPPLIERS PROVIDE THE SOFTWARE AND ANY (IF ANY) SUPPORT SERVICES RELATED TO THE SOFTWARE ("SUPPORT SERVICES") AS IS AND WITH ALL FAULTS, AND HEREBY DISCLAIM WITH RESPECT TO THE SOFTWARE AND SUPPORT SERVICES ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY (IF ANY) WARRANTIES, DUTIES OR CONDITIONS OF OR RELATED TO: MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, LACK OF VIRUSES, ACCURACY OR COMPLETENESS OF RESPONSES, RESULTS, WORKMANLIKE EFFORT AND LACK OF NEGLIGENCE. ALSO, THERE IS NO WARRANTY, DUTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, AND CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT. THE ENTIRE RISK AS TO THE QUALITY, OR ARISING OUT OF THE USE OR PERFORMANCE OF THE SOFTWARE AND ANY SUPPORT SERVICES, REMAINS WITH RECIPIENT.

9. EXCLUSION OF INCIDENTAL, CONSEQUENTIAL AND CERTAIN OTHER DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, SPECIAL, INCIDENTAL, INDIRECT, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR: LOSS OF PROFITS, LOSS OF CONFIDENTIAL OR OTHER INFORMATION, BUSINESS INTERRUPTION, PERSONAL INJURY, LOSS OF PRIVACY, FAILURE TO MEET ANY DUTY (INCLUDING OF GOOD FAITH OR OF REASONABLE CARE), NEGLIGENCE, AND ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE OR SUPPORT SERVICES, THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT SERVICES, OR OTHERWISE UNDER OR IN CONNECTION WITH ANY PROVISION OF THIS AGREEMENT, EVEN IN THE EVENT OF THE FAULT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, BREACH OF CONTRACT OR BREACH OF WARRANTY OF MICROSOFT OR ANY SUPPLIER, AND EVEN IF MICROSOFT OR ANY SUPPLIER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO RECIPIENT.

10. LIMITATION OF LIABILITY AND REMEDIES. NOTWITHSTANDING ANY DAMAGES THAT RECIPIENT MIGHT INCUR FOR ANY REASON WHATSOEVER (INCLUDING, WITHOUT LIMITATION, ALL DAMAGES REFERENCED ABOVE AND ALL DIRECT OR GENERAL DAMAGES), THE ENTIRE LIABILITY OF MICROSOFT AND ANY OF ITS SUPPLIERS UNDER ANY PROVISION OF THIS AGREEMENT AND RECIPIENT’S EXCLUSIVE REMEDY FOR ALL OF THE FOREGOING SHALL BE LIMITED TO ACTUAL DAMAGES INCURRED BY YOU BASED ON REASONABLE RELIANCE UP TO THE LESSER OF THE AMOUNT ACTUALLY PAID BY RECIPIENT FOR THE SOFTWARE OR FIVE DOLLARS (US$5.00). THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS (INCLUDING SECTIONS 8 AND 9 ABOVE) SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EVEN IF ANY REMEDY FAILS ITS ESSENTIAL PURPOSE.

11. GOVERNING LAW/JURISDICTION/ATTORNEYS’ FEES. This Agreement shall be construed and controlled by the laws of the State of Washington, and Recipient consents to exclusive jurisdiction and venue in the federal courts sitting in King County, Washington, unless no federal jurisdiction exists, in which case Recipient consents to exclusive jurisdiction and venue in the Superior Court of King County, Washington. Recipient waives all defenses of lack of personal jurisdiction and forum non-conveniens. Process may be served on either party in the manner authorized by applicable law or court rule. If either party employs attorneys to enforce any rights arising out of or relating to this Agreement, the prevailing party shall be entitled to recover its reasonable attorneys' fees, costs and other expenses.

12. U.S. GOVERNMENT RIGHTS. All Software provided to the U.S. Government pursuant to solicitations issued on or after December 1, 1995 is provided with the rights and restrictions described elsewhere herein. All Software provided to the U.S. Government pursuant to solicitations issued prior to December 1, 1995 is provided with RESTRICTED RIGHTS as provided for in FAR, 48 CFR 52.227-14 (JUNE 1987) or DFAR, 48 CFR 252.227-7013 (OCT 1988), as applicable.

13. EXPORT RESTRICTIONS. Recipient acknowledges that Software is of U.S. origin. Recipient agrees to comply with all applicable international and national laws that apply to the Software, including the U.S. Export Administration Regulations, as well as end-user, end-use and destination restrictions issued by U.S. and other governments. For additional information, see http://www.microsoft.com/exporting/ .

14. NOTE ON JAVA SUPPORT. THE SOFTWARE MAY CONTAIN SUPPORT FOR PROGRAMS WRITTEN IN JAVA. JAVA TECHNOLOGY IS NOT FAULT TOLERANT AND IS NOT DESIGNED, MANUFACTURED, OR INTENDED FOR USE OR RESALE AS ONLINE CONTROL EQUIPMENT IN HAZARDOUS ENVIRONMENTS REQUIRING FAIL-SAFE PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, DIRECT LIFE SUPPORT MACHINES, OR WEAPONS SYSTEMS, IN WHICH THE FAILURE OF JAVA TECHNOLOGY COULD LEAD DIRECTLY TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE. Sun Microsystems, Inc. has contractually obligated Microsoft to make this disclaimer.

15. ENTIRE AGREEMENT. This Agreement constitutes the complete and exclusive agreement between Microsoft and Recipient with respect to the subject matter hereof, and supersedes all prior or contemporaneous oral or written communications, proposals, representations, understandings, or agreements not specifically incorporated herein. This Agreement may not be amended except in a writing duly signed by an authorized representative of Microsoft and Recipient.

16. PARTIES BOUND. If Recipient is executing this Agreement on behalf of an entity, then Recipient represents he/she has authority to execute this Agreement on behalf of such entity and agrees that the Software (and any copies thereof) shall remain on the company premises, unless otherwise agreed to in writing by Microsoft.

17. Should you have any questions concerning this Agreement, or if you desire to contact Microsoft for any reason, please write Microsoft Corporation, One Microsoft Way, Redmond WA 98052-6399.

Do you accept all of the terms of the preceding License Agreement? If you choose No, Install will close. To install you must accept this agreement.

2. The Open Source Definition

Source: http://www.opensource.org/docs/definition.php

This is not a license, but rather a set of criteria for deciding whether a license is "open source."

Note: The license shown below is for reference purposes and does not apply to this document.

The Open Source Definition

Version 1.9

The indented, italicized sections below appear as annotations to the Open Source Definition (OSD) and are not a part of the OSD. A plain version of the OSD without annotations can be found here .

A printable version of this annotated page is available here .

Introduction

Open source doesn’t just mean access to the source code. The distribution terms of open-source software must comply with the following criteria:

1. Free Redistribution

The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.

Rationale: By constraining the license to require free redistribution, we eliminate the temptation to throw away many long-term gains in order to make a few short-term sales dollars. If we didn’t do this, there would be lots of pressure for cooperators to defect.

2. Source Code

The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a product is not distributed with source code, there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost–preferably, downloading via the Internet without charge. The source code must be the preferred form in which a programmer would modify the program. Deliberately obfuscated source code is not allowed. Intermediate forms such as the output of a preprocessor or translator are not allowed.

Rationale: We require access to un-obfuscated source code because you can’t evolve programs without modifying them. Since our purpose is to make evolution easy, we require that modification be made easy.

3. Derived Works

The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.

Rationale: The mere ability to read source isn’t enough to support independent peer review and rapid evolutionary selection. For rapid evolution to happen, people need to be able to experiment with and redistribute modifications.

4. Integrity of The Author’s Source Code

The license may restrict source-code from being distributed in modified form only if the license allows the distribution of "patch files" with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software.

Rationale: Encouraging lots of improvement is a good thing, but users have a right to know who is responsible for the software they are using. Authors and maintainers have reciprocal right to know what they’re being asked to support and protect their reputations.

Accordingly, an open-source license must guarantee that source be readily available, but may require that it be distributed as pristine base sources plus patches. In this way, "unofficial" changes can be made available but readily distinguished from the base source.

5. No Discrimination Against Persons or Groups

The license must not discriminate against any person or group of persons.

Rationale: In order to get the maximum benefit from the process, the maximum diversity of persons and groups should be equally eligible to contribute to open sources. Therefore we forbid any open-source license from locking anybody out of the process.

Some countries, including the United States, have export restrictions for certain types of software. An OSD-conformant license may warn licensees of applicable restrictions and remind them that they are obliged to obey the law; however, it may not incorporate such restrictions itself.

6. No Discrimination Against Fields of Endeavor

The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.

Rationale: The major intention of this clause is to prohibit license traps that prevent open source from being used commercially. We want commercial users to join our community, not feel excluded from it.

7. Distribution of License

The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.

Rationale: This clause is intended to forbid closing up software by indirect means such as requiring a non-disclosure agreement.

8. License Must Not Be Specific to a Product

The rights attached to the program must not depend on the program’s being part of a particular software distribution. If the program is extracted from that distribution and used or distributed within the terms of the program’s license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the original software distribution.

Rationale: This clause forecloses yet another class of license traps.

9. The License Must Not Restrict Other Software

The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software.

Rationale: Distributors of open-source software have the right to make their own choices about their own software.

Yes, the GPL is conformant with this requirement. Software linked with GPLed libraries only inherits the GPL if it forms a single work, not any software with which they are merely distributed.

Origins: Bruce Perens wrote the first draft of this document as "The Debian Free Software Guidelines", and refined it using the comments of the Debian developers in a month-long e-mail conference in June, 1997. He removed the Debian-specific references from the document to create the "Open Source Definition."

Copyright © 2002 by the Open Source Initiative
Send questions or suggestions about the website to Steve M.: webmaster at opensource.org

5. References