WINDOWS - liian riippuvainen etäproseduurikutsusta:
RPC stands for Remote Procedure Call. Simply put, an RPC is what happens when one program sends a message over a network to tell another program to do something. For example, one program can use an RPC to tell another program to calculate the average cost of tea in China and return the answer. The reason it’s called a remote procedure call is because it doesn’t matter if the other program is running on the same machine, another machine in the next cube, or somewhere on the Internet.
RPCs are POTENTIAL SECURITY RISKS because they are designed to let other computers somewhere on a network to tell your computer what to do. Whenever someone discovers a flaw in an RPC-enabled program, there is the potential for someone with a network-connected computer to exploit the flaw in order to tell your computer what to do. Unfortunately, Windows users cannot disable RPC because Windows depends upon it, even if your computer is not connected to a network. Many Windows services are simply designed that way. In some cases, you can block an RPC port at your firewall, but Windows often depends so heavily on RPC mechanisms for basic functions that this is not always possible. Ironically, some of the most serious vulnerabilities in Windows Server 2003 (see table in section below) are due to flaws in the Windows RPC functions themselves, rather than the applications that use them. The most common way to exploit an RPC-related vulnerability is to attack the service that uses RPC, not RPC itself.
LINUX:
As stated above in the section on Windows, RPC stands for Remote Procedure Call. Simply put, an RPC allows one program to tell another program to do something, even if that other program resides on another computer. For example, one program can use an RPC to tell another program to calculate the average cost of tea in China and return the answer. The reason it’s called a remote procedure call is because it doesn’t matter if the other program is running on the same machine, another machine in the next cube, or somewhere on the Internet.
Most Linux distributions install programs with network access turned off by default. For example, the MySQL SQL database server is usually installed such that it does not listen to the network for instructions. If you build a web site using Apache and MySQL on the same server machine, then Apache will interact with MySQL without MySQL having to listen to the network. Contrast this to SQL Server, which listens to the network whether or not it is necessary to do so. If you want MySQL to listen to the network, you must turn on that feature manually, and then explicitly define the users and machines allowed to access MySQL.
Even when Linux applications use the network by default, they are most often configured to respond only to the local machine and ignore any requests from other machines on the network.
Unlike Windows Server 2003, you can disable virtually all network-related RPC services on a Linux machine and still have a perfectly functional desktop.
Lähde: The Register, Security Report: Windows vs Linux
RPC stands for Remote Procedure Call. Simply put, an RPC is what happens when one program sends a message over a network to tell another program to do something. For example, one program can use an RPC to tell another program to calculate the average cost of tea in China and return the answer. The reason it’s called a remote procedure call is because it doesn’t matter if the other program is running on the same machine, another machine in the next cube, or somewhere on the Internet.
RPCs are POTENTIAL SECURITY RISKS because they are designed to let other computers somewhere on a network to tell your computer what to do. Whenever someone discovers a flaw in an RPC-enabled program, there is the potential for someone with a network-connected computer to exploit the flaw in order to tell your computer what to do. Unfortunately, Windows users cannot disable RPC because Windows depends upon it, even if your computer is not connected to a network. Many Windows services are simply designed that way. In some cases, you can block an RPC port at your firewall, but Windows often depends so heavily on RPC mechanisms for basic functions that this is not always possible. Ironically, some of the most serious vulnerabilities in Windows Server 2003 (see table in section below) are due to flaws in the Windows RPC functions themselves, rather than the applications that use them. The most common way to exploit an RPC-related vulnerability is to attack the service that uses RPC, not RPC itself.
LINUX:
As stated above in the section on Windows, RPC stands for Remote Procedure Call. Simply put, an RPC allows one program to tell another program to do something, even if that other program resides on another computer. For example, one program can use an RPC to tell another program to calculate the average cost of tea in China and return the answer. The reason it’s called a remote procedure call is because it doesn’t matter if the other program is running on the same machine, another machine in the next cube, or somewhere on the Internet.
Most Linux distributions install programs with network access turned off by default. For example, the MySQL SQL database server is usually installed such that it does not listen to the network for instructions. If you build a web site using Apache and MySQL on the same server machine, then Apache will interact with MySQL without MySQL having to listen to the network. Contrast this to SQL Server, which listens to the network whether or not it is necessary to do so. If you want MySQL to listen to the network, you must turn on that feature manually, and then explicitly define the users and machines allowed to access MySQL.
Even when Linux applications use the network by default, they are most often configured to respond only to the local machine and ignore any requests from other machines on the network.
Unlike Windows Server 2003, you can disable virtually all network-related RPC services on a Linux machine and still have a perfectly functional desktop.
Lähde: The Register, Security Report: Windows vs Linux
Vastaukset 7
Vanhimmat
Ne jotka perustelevat Linuxin turvallisuutta sillä että sitä käytetään Windowsia vähemmän eivät ota huomioon sitä, että jo 5-6 vuotta sitten n. 2/3 nettisivustoista pyöri Apachella kun taas IIS:n osuus oli vain viidennes. Siitä huolimatta juuri IIS:ään hyökättiin rajusti. Miksi? Siksi koska haittaohjelmien laatijat käyttävät ensisijaisena kriteerinä kohteen haavoittuvuutta, eivät yleisyyttä.
Windows-fanit voisivat joskus vakavissaan miettiä sitäkin, miksi Windows-haittaohjelmia laaditaan 5000 kertaa enemmän kuin kaikkia muita yhteensä vaikka Linuxin, Macin ja muiden osuus työasemistakin lähenee jo 20% ja on ylivoimainen servereissä.
Tosiasia on se, että Windows on synnynnäisesti turvaton käyttöjärjestelmä verkkomaailmaan. Faktat puhuvat puolestaan. Missä Windows, siellä ongelma.
Kainalohiki se jaksaa jauhaa paskaa linuxesta ja sen toimivuudesta.
http://www.w3schools.com/browsers/browsers_os.asp
http://www.w3schools.com/browsers/browsers_explorer.asp
http://www.statowl.com/operating_system_market_share.php
Taas löytyi uusi amerikan market share lol..
Pitänee paikkansa ostettujen pakettien mukaan.
Vaikkakin, mitä harvinaisempi, sitä parempi. Ainokaista ei paraskaan "hakkeri" löydä.
Kaupalliset pay-per-click käyttöjärjestelmälaskurit ovat yhtä tyhjän kanssa. Linux-käyttäjät käyttävät rahaa yleensä vain kaupallisten pelien hankkimiseen. Sen sijaan miksi Linux-käyttäjä vierailisi ostotarkoituksessa jollakin MS Office-sivustolla? Net Application ja eteenkin Statscounter näyttävät Mac OSX:n osuuden aivan liian suurena.