Microsoft's IIS is Twice as Likely to Host Malware?

eldavojohn writes "According to Google, Microsoft's server software is at least twice as likely to host viruses or malware. The reason why? 'Google reports that IIS is likely used to distribute malware more often than Apache because many IIS installs are on pirated Windows versions which aren't configured to automatically download patches. (Even pirated Windows versions can automatically receive security fixes, however.) Our analysis demonstrates how important it is to keep web servers patched to the latest patch level,' Google notes."

Re:Help me out

[AKAImBatman]

See! The same thing is going to happen to Macs and Linux as soon as they become popular! Because popularity means that these OSes will get pirated more. Which will lead to more infections of unpatched systems. Even though Linux is "free" (as in beer) and Mac OS X only works on legitimate Mac Hardware. Because free... and official hardware...

Wait...

What was I saying again?

It made be hard to get patches for pirated windows

[Anonymous Coward]

...but it is IMPOSSIBLE to get patches for a pirated copy of Apache.

I doubt anyone on Slashdot can prove they did it even with the most leet of cracking skillz.

It may be reckless to run pirated IIS, but it is simply gross negligence to run pirated Apache.

Re:Help me out

[mrsteveman1]

I agree, I'm currently on my way to getting a CCSP at the moment, and there are people in the college classes i take who barely understand how a windows domain works, let alone network systems and authentication.

Recently one of them was trying to connect to the VPN at his job, which is part of a windows domain, and it wouldn't work because he hadn't authenticated against the schools wireless login yet and obviously wouldn't be able to connect to anything. The wireless auth system basically just grabs users from the mail server, and inserts a access list rule in the router behind it allowing traffic from your MAC address to get out.

So he entered in his user and such, and was able to connect to the VPN at his job. He then went on to say that he forgot to login to the wireless page and that they had to login to the domain at work to use the servers. I explained to him that the wireless login didn't have anything to do with the windows domain where he works, but he pulled out one of those "i don't actually know anything" lines and said "All I know is we have to login to the wireless system at work to use the network, you can use the internet but not the servers", which is completely different and reverse situation. The result being that now he thinks the wireless login authenticated his laptop against the windows domain at his job, never mind the fact that they are completely distinct and unrelated networks, not even using the same authentication system or user database.