|
Written by Administrator
|
|
Myth, which unfortunately is often duplicated in the media, it is feared that the opening of the code will leak outside the company's confidential data. "If we just look ..." you should be aware at this point important distinction: transparency code, or even publicity the way in which they were saved data [ie. encryption algorithms] has nothing to do with the transparency of the data. From a mathematical point of view, even knowing how the data was encrypted, we can not read confidential data, if we do not have the keys needed to read them. And if we have the key or not, has nothing to do with the openness or closure of the software, and only from properly conducted the company's security policy - access to sensitive data should be protected under similar conditions as access to corporate cash, and not by concealing the source program.
The existence of any relationship between openness and security code data, it is rather the opposite relationship. Use a very simple example here: who will guarantee us that, in a program with closed source software have not included terms such as Christmas tree, after which you type can be read all of our documents? In software, open all that is done to ensure the safety of your data, you can see visually - and so also check whether the developer has not left a Christmas tree fatal password saved on firmly "in the program. In a closed software - almost by definition - it is possible to verify such a threat does not and will not be. |
linux for dummies 
During the last week I had the opportunity to test the Proffesional new version of SUSE 9.1. As is usually the first impression is often