open source technology1

8/7/2019 Open source technology1

1/7

OPEN SOURCE TECHNOLOGY

by:

NEHA BHAVSAR

ADITI DHAYBAR

SOU. VENUTAI CHAVAN POLYTECHNIC,PUNE


2/7

2

ABSTRACT

Open source technology is defined as theproduction and developmentphilosophy ofallowingend

users and developers to not only see the source code ofsoftware, butmodify it as well. The Linux

operating system is a one ofthe best-knownexamples ofopen source software technology. Open source

code is made availablefree ofcharge to the generalpublic. The rationalefor this is that a large

community ofdevelopers who arenot concerned with proprietary ownership willproducemore usefuland bug-freeproductforeveryone's benefit. The open source concept relies on community members to

find andeliminate bugs in theprogram code, a process which commercially developed andpackaged

programs do not utilize. Theprocess ofeliminating bugs and improving the software happens atmuch

quicker rate than through the traditional development channels ofcommercial 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.


3/7

3

Introduction

Open-sourcesoftware (OSS) is computer

software that is available in source code form for

which the source code and certain other rights

normally reserved for copyright holders are

provided under a software license that permits

users to study, change, improve and at times also to

distribute the software.

Some open source licenses meet the requirements

of the Open Source Definition. Some open source

software is available within the public domain

Open source software is very often developed in a

public, collaborative manner. Open-source

software is the most prominent example of open-

source development and often compared to

(technically defined) user-generated content or(legally defined) open content movements.

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

1983. In 1998, a group of individuals

advocated that the term free software should be

replaced by open source software (OSS) as 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 or

understand its internal functioning. Open

source software generally allows anyone to

create modifications of the software, port it to

new operating systems and processor

architectures, share it with others or market it.

Scholars Casson and Ryan have pointed out

several policy-based reasons for adoption of

open source, in particular, the heightened value

proposition from open source (when compared

to most proprietary formats) in the following

categories:

Security Affordability Transparency

Perpetuity Interoperability Localization.

CriteriaofOpen Source Code

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.


4/7

4

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 notdistributed 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 obfuscatedsource 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

Personsor Groups

The license must not discriminate

against any person or group of

persons.

6. No Discrimination Against

FieldsofEndeavor.

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 ofLicense

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

toa 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


5/7

5

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

Technology-Neutral

No provision of the license may be

predicated on any individual

technology or style of interface.

Open Standards Requirement

for Software

1. No Intentional Secrets: The standardMUST NOT withhold any detail

necessary for interoperable

implementation. As flaws are

inevitable, the standard MUST define

a process for fixing flaws identified

during implementation and

interoperability testing and to

incorporate said changes into a

revised version or superseding

version of the standard to be released

under terms that do not violate the

OSR.

2. Availability: The standard MUST befreely 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 toimplementation of the standardMUST:

o be licensed under royalty-free termsfor unrestricted use, or

o be covered by a promise of non-assertion when practiced by open

source software

4. No Agreements: There MUST NOTbe any requirement for execution of a

license agreement, NDA, grant, click-

through, or any other form of

paperwork to deploy conforming

implementations of the standard.

5. No OSR-IncompatibleDependencies: Implementation of the

standard MUST NOT require any

other technology that fails to meet the

criteria of this Requirement.

Open Standards Compliance

Compliance Levels

To assist governments and other bodies in

recognizing and adopting

standards that conform to this Requirement,

the OSI defines two levels

of compliance:

OSR Compatible


6/7

6

This indicates that the owner of the

standard has self-certified

that their standard complies with this

Requirement, and all Compliance

Criteria. Anyone may ask the OSI to review anOSR Compatible standard;

if the OSI finds that the standard is

incompatible, the owner must either

modify the standard or stop using the OSR

Compatible mark.

OSR Conformant

This indicates the OSI has reviewed a

standard, as submitted by the owner,

and certified that it fully conforms to the OSR.

The OSI may charge a fee

to offset the costs of this certification.

Open Source Software Security.

More people can inspect the source codeto find and fix a possible vulnerability.

Proprietary software forces the user toaccept the level of security that the

software vendor is willing to deliver and

to accept the rate that patches and updates

are released.

The end-user of Open Source code has theability to change and modify source to

implement any extra "features" of security

they may wish for a specific use, which

can extend to the kernel level if they so

wish.

It is assumed that any compiler that isused creates code that can be trusted, but it

has been demonstrated by Ken

Thompson that a compiler can be

subverted using an eponymous Thompson

hackto create faulty executables that are

unwittingly produced by a well-

intentioned developer.With access to the

source code for the compiler, the

developer has at least the ability to

discover if there is any mal-intention.

Kerckhoffs' principle is based on the ideathat an enemy can steal a secure military

system and not be able to compromise the

information. His ideas were the basis for

many modern security practices, and

followed that security through obscurity is

a bad practice.

Conclusion.

Although open source software is often free to

download and use, open source licenses rarely

transfer any ownership of the software to the

end user or developer. Open source is not

limited to software. Open source philosophies

have been applied


7/7

7

Refrences.

http://en.wikipedia.org/wiki/Open-source_software www.opensource.org/ www.sourceforge.net

open source technology1

Documents