News for hackers. Stuff that matters.
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?