Security and Open Source - 2 February 2012 - Blog - | LINUX - SECURITY |
Saturday, 2016-12-03, 6:37 PM
Welcome Guest | RSS
Statistics

Total online: 1
Guests: 1
Users: 0
Site menu
Our Documentations
1* METASPLOIT
Blog Category
# Only for beginners [39]
This category contains some introductions and tutorials about UBUNTU and BACKTRACK for those who just start using LINUX.
# Computer Security [11]
In this category, you will find all courses about the Informatique Security
# LINUX [2]
EVERYTHING ABOUT LINUX - UBUNTU & BACKTRACK - (NEWS, VIDEOS, TUTORIALS, ... )
# BackTrack 5 Tutorials [6]
In this categorie, I will post all tutorials about BackTrack5 (Installation, Configuration, Update, Hacking...)
# TechnicDynamic Tutorials [12]
Technic Dynamic is a source of education focused in the following categories of technology: (Computer - Design - Gadgets - Networking - Security) Link : http://technicdynamic.com
# Vishnuvalentino Tutorials [2]
He is a computer security specialist, and also freelance website designer. Read more : http://vishnuvalentino.com/about/
# Hackers News [6]
All news about the hackers of the world ...
# Tools [18]
All Security Tools
MEMES PICTURES [0]
Entries archive
Shopping


Follow us
facebook
Main » 2012 » February » 2 » Security and Open Source
7:29 PM
Security and Open Source
Security and Open Source

Introduction 

Since Linus Torvalds and his Linux system, open source has grown considerably. But what is Open Source? It is the act of making public the source code of software. Open source is governed by a set of licenses, the best known is the GNU Public License . This source code is no longer the Possession of a private person, a group of people, or society, as was the case since the birth of the computer in 60 years, until the 80/90 years. Larger companies followed suit currently no independent developers and in turn offer professional-quality software as open source. But behind this intellectual ferment, what are the consequences for safety, for open source projects? 

The benefits 


Multiple re-readings of the code 

Whether student, professional, amateur or just whatever their level, methods, culture, nationality, the programmer has access to the code. He can read it to understand and anticipate debugging. Readings of these cross many bugs can be detected. Among these bugs, there are certainly directly affect the security of software, such as buffer overflow. This is called application security holes. 

Reactivity of open source 

Another advantage of open source is that the community responds more quickly in the bug fix. This even happens frequently that the programmer discovers a bug also proposes allowing the patch to fix it, when information is made ​​public. The traditional software companies take longer because their structure is more hierarchical, larger and less reactive. 

The disadvantages 


Multiple re-readings of the code 

Proofreading multiple code can detect a greater number of security holes in software. By cons, it would be naive to think that all the security holes are seen! Software is becoming more complex and some even exceed the vision that a programmer can have all the software. This is true of Linux programmers are confined to write patches in the best modules, and few people have a global view of all the pieces of code that make up the Linux kernel. If we add to this that there is a kernel for each OS, and each OS has different behavior for safety in programming ... 
In addition, across all programmers in the world, there are few people qualified to do a reading of open source code, looking for security holes. It is therefore quite conceivable that a security hole exists in open source software and that no one finds out for months, even years. 

Open source is ... Open! 

Putting the code accessible to everyone is risky: If someone discovers a security hole, nothing prevents him to keep for him to make a profit of some kind. A security hole that can not be corrected if known. So as hackers keep their information for them, the target software will not be corrected. And it can take months. 

Conclusion 

Everyone knows that security based on a proprietary program is not safe: Any hacker can disassemble the code to understand how the protection is made. It is a fact. This is why open source is generally considered more secure than proprietary code. As we have seen, it is not. The mere fact that goes in the direction of open source is that a security bug is usually more quickly discovered and corrected more quickly.
Category: # Computer Security | Views: 351 | Added by: Administrator | Rating: 0.0/0
Total comments: 0
Name *:
Email *:
Code *:
Visitors

Share This On:
Google Translator
Search
Login form
Our poll
Rate my site
Total of answers: 17
Clock & Calendar

«  February 2012  »
SuMoTuWeThFrSa
   1234
567891011
12131415161718
19202122232425
26272829