Home arrow linux for dummies arrow The safety of open code

Login Form






Lost Password?
No account yet? Register

Syndicate


SUSE 9.1 Professional PDF Print E-mail
 
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 Plock Buy Joomla Templates atorvastatin 10mg med the most important, I was afraid to open the box. Collected a little courage I opened it. I could not go with admiration. SUSE AG postarala really to give SUSE. Yes it should appear each boxed version of GNU / Linux. In the middle of a consumer who bought the package is 2 books dealing with Linux: Administration speed test SEO červené víno Guide "and" User Guide ", a package of CDs and the 2 disc DVD bilateral (DVD1 and DVD2 installation source), plus a package of regular CD needed for installation - total 7 discs. In addition, SUSE AG, the plate with a full version of the database SQL Anywhere Studio for Linux v9.0 and SUSE extra sticker with the logo - with the chameleon. That was a first impression.


The safety of open code PDF Print E-mail
Written by Administrator   
Quite often claim, raised at OpenSource solutions, is the question of its safety. Argues that, since the software is available, then everyone can go inside and catch the error, which would enable him to break such as web server operated by the running program is flawed. How much truth is in these statements? It actually creates openness sources such options as described above. However, this is an asset, not a defect! Why? Answer to this question, the software should be compared with closed software, whose code is publicly available:     1. By purchasing the software open, you never have 100% sure whether the manufacturer is not included in the code, for example, that all invoices to rounding of amounts transferred to his account [is there such stories ...], or the last day of each month not to send financial data to our his seat on the Internet. Open software, but does not exclude such a possibility, but it significantly minimizes. In extreme cases you can simply view the suspect piece of code and see whether it contains commands that are in some way dangerous to our data. Recalling the analogy of the cake - who give us confidence that the cookie has not been virused since we do not have, or provision, or we can not bake it themselves, but only buy it in the confectionery?

    2. Bugs closed in the software are sometimes removed at the request of customers, sometimes at the time of releasing the new version of the program, and sometimes never. In an open software, the error is usually removed immediately after its discovery. And if we have suitably qualified staff, simply delete the error yourself.

    3. Openness fosters writing good software programs. No one will be hard-headed to your opinion on the software, by making source, which shows lack of knowledge or simple sloppiness. The software can be written in closed well, but need not - in the end the customer does not see any way.
 
Next >