News for hackers. Stuff that matters.
Re:Google ditches Windows on security concerns by beagle3 on Tuesday June 01, 2010 @05:52AM (#1394723)
And yet, when you looked at e.g. the web server data back in the early 2000's, you had 70% apache 25% IIS -- and yet about 20 times as many exploits (and much more effective at that) for IIS.

The reason was, to put it bluntly, that IIS was designed without any regard to real security, whereas Apache had _some_ regard to security.

That's also the case for Windows through its history; it has been making leaps recently, but doing things more securely requires it to become less convenient / not backwards compatible, and therefore it is still, relatively speaking, way more vulnerable when used by your average user.

I'm not up-to-date, but up until 2007 or so, a significant number of web browser vulnerabilities were directly or indirectly a result of Windows and Explorer's love of executing files after wrongly identifying them as e.g. wav or doc files.

The single Unix design decision that a file must have an executable flag out-of-band, and the convention that by default this flag is off, both of which date back to 1970, have kept Unix safe from these kinds of bugs. Sane default permissions on system directories are another decision; the latter has been adopted by Windows in XP SP2 IIRC, the former still hasn't.

Re:Google ditches Windows on security concerns by tptacek on Tuesday June 01, 2010 @10:59AM (#1395181)
I would like to hear the specific ways in which you think that Apache was designed for security in ways that IIS wasn't, and how those things persist into modern IIS.
Re:Google ditches Windows on security concerns by beagle3 on Wednesday June 02, 2010 @04:38AM (#1397448)
To start with, Apache default setup would bind to port 80 and switch to user 'apache' or 'httpd', whereas IIS (back then, that was IIS4/5 days) default and hard-to-change setup was that it was running with SYSTEM priviliges.

There had been security audits of the apache code base since its early dates (as NCSA Web Server), whereas IIS didn't (or, judging from its track record, if it did have they were done by incompetents who didn't notice the strcpy(host_field, ...) would overflow with a host name > 1024 bytes.

IIS had everything in the same process, meaning every thing exploitable somewhere would bring the whole server with it. Apache used a worse-performing but better compartmentalized process-per-request model.

Just to be clear, apache at the time was NOT a beacon of security or good design or anything. But it did follow standard Unix practices, which put it a significantly better place than the IIS of the time (which was written like a Windows desktop program). At the time, IIS exploits were being found at a rate of 4 remote roots per month, with worms actively exploiting them, whereas apache had one of these every several months, usually only exploitable if you knew the exact O/S version it was running on.

Re:Google ditches Windows on security concerns by adolph on Tuesday June 01, 2010 @11:58AM (#1395354)
Not a serious reply: Well, for one, IIS was designed to run on Windows servers rather than *nix.
Re:Google ditches Windows on security concerns by tptacek on Tuesday June 01, 2010 @12:18PM (#1395405)
Rejoinder in equivalent tone: you mean, the servers that ran rexd, the "run any command for me without credentials" RPC service? Or the servers that had remote calendar managers that would run commands for anyone who knew what the semicolon character meant to the shell? Or the ones that got confused if you sent FTP commands in the wrong order and too fast and would accidentally upgrade you to root instead of logging you off?