OPEN SOURCE TECHNOLOGY

by:

NEHA BHAVSAR

ADITI DHAYBAR

SOU. VENUTAI CHAVAN POLYTECHNIC,PUNE

 ABSTRACT

Open source technology is defined as the production and development philosophy of allowing end
users and developers to not only see the source code of software, but modify it as well. The Linux
operating system is a one of the best-known examples of open source software technology. Open
source code is made available free of charge to the general public. The rationale for this is that a large
community of developers who are not concerned with proprietary ownership will produce more useful
and bug-free product for everyone's benefit. The open source concept relies on community members to
find and eliminate bugs in the program code, a process which commercially developed and packaged
programs do not utilize. The process of eliminating bugs and improving the software happens at much
quicker rate than through the traditional development channels of commercial software. The
information is shared within open source community and does not originate or channel through a
corporation's research and development department.

Keywords: Introduction, History, Terms , Security.

2
 Some open source licenses meet the requirements
of the Open Source Definition. Some open source
Introduction software is available within the public domain

Open source software is very often developed in a

Open-source software (OSS) is computer
public, collaborative manner. Open-source
software that is available in source code form for
software is the most prominent example of open-
which the source code and certain other rights
source development and often compared to
normally reserved for copyright holders are
(technically defined) user-generated content or
provided under a software license that permits
(legally defined) open content movements.
users to study, change, improve and at times also to
distribute the software. A report by Standish Group states that adoption of
open-source software models has resulted in
savings of about $60 billion per year to consumers

History

The free software movement was launched in  Transparency

1983. In 1998, a group of individuals  Perpetuity
advocated that the term free software should  Interoperability
be replaced by open source software (OSS) as  Localization.
an expression which is less ambiguous and
more comfortable for the corporate world
Software developers may want to publish their
software with an open source license, so that
anybody may also develop the same software
Criteria of Open Source Code
or understand its internal functioning. Open
source software generally allows anyone to
create modifications of the software, port it to 1. Free Redistribution
new operating systems and processor The license shall not restrict any party
architectures, share it with others or market it. from selling or giving away the
Scholars Casson and Ryan have pointed out software as a component of an
several policy-based reasons for adoption of aggregate software distribution
open source, in particular, the heightened value containing programs from several
proposition from open source (when compared different sources. The license shall
to most proprietary formats) in the following not require a royalty or other fee for
categories: such sale.

 Security
 Affordability

3

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.
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.
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.
5. No Discrimination Against
Persons or Groups
The license must not discriminate
against any person or group of
persons.
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.
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.
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
4
 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.
9. 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.
10. License Must Be
under terms that do not violate the
OSR.
2. Availability: The standard MUST be
freely and publicly available (e.g.,
from a stable web site) under royalty-
free terms at reasonable and non-
discriminatory cost.
3. Patents: All patents essential to
implementation of the standard
MUST:
o be licensed under royalty-free
terms for unrestricted use, or
o be covered by a promise of non-
assertion when practiced by open
source software
4. No Agreements: There MUST NOT
be any requirement for execution of a

Technology-Neutral license agreement, NDA, grant, click-

through, or any other form of
No provision of the license may be paperwork to deploy conforming
predicated on any individual implementations of the standard.
technology or style of interface. 5. No OSR-Incompatible
Dependencies: Implementation of the
Open Standards Requirement standard MUST NOT require any
for Software other technology that fails to meet the
criteria of this Requirement.
1. No Intentional Secrets: The standard
MUST NOT withhold any detail
necessary for interoperable Open Standards Compliance
implementation. As flaws are
inevitable, the standard MUST define
a process for fixing flaws identified
during implementation and Compliance Levels

interoperability testing and to

To assist governments and other bodies in
incorporate said changes into a
recognizing and adopting
revised version or superseding
standards that conform to this Requirement,
version of the standard to be released
the OSI defines two levels
of compliance:

5
 OSR Compatible  The end-user of Open Source code
has the ability to change and modify
This indicates that the owner of the source to implement any extra "features"
standard has self-certified of security they may wish for a specific
that their standard complies with this use, which can extend to the kernel level if
Requirement, and all Compliance they so wish.
Criteria. Anyone may ask the OSI to review an
OSR Compatible standard;  It is assumed that any compiler that is
if the OSI finds that the standard is used creates code that can be trusted, but it
incompatible, the owner must either has been demonstrated by Ken
modify the standard or stop using the OSR Thompson that a compiler can be
Compatible mark. subverted using an eponymous Thompson
hack to create faulty executables that are
OSR Conformant unwittingly produced by a well-
intentioned developer.With access to the
This indicates the OSI has reviewed a
source code for the compiler, the
standard, as submitted by the owner,
developer has at least the ability to
and certified that it fully conforms to the OSR.
discover if there is any mal-intention.
The OSI may charge a fee
to offset the costs of this certification.  Kerckhoffs' principle is based on the
idea that an enemy can steal a secure
military system and not be able to
Open Source Software Security.
compromise the information. His ideas

 More people can inspect the source were the basis for many modern security

code to find and fix a possible practices, and followed that security

vulnerability. through obscurity is a bad practice.

 Proprietary software forces the user to Conclusion.

accept the level of security that the
Although open source software is often free to
software vendor is willing to deliver and
download and use, open source licenses rarely
to accept the rate that patches and updates
transfer any ownership of the software to the
are released.
end user or developer. Open source is not
limited to software. Open source philosophies
have been applied

6
Refrences.

 http://en.wikipedia.org/wiki/Open-source_software

 www.opensource.org/

 www.sourceforge.net