Slashdot Mirror


Microsoft No Longer a 'Laughingstock' of Security?

Toreo asesino writes "In a Q&A with Scott Charney, the vice president of Trustworthy Computing at Microsoft, Charney suggests that security in Microsoft products has moved on from being the 'laughing stock' of the IT industry to something more respectable. He largely attributes this to the new Security Development Lifecycle implemented in development practices nearly six years ago. 'The challenge is really quite often in dealing with unrealistic expectations. We still have vulnerabilities in our code, and we'll never reduce them to zero. So sometimes we will have a vulnerability and people say to me, "So the [Security Development Lifecycle (SDL)] is a failure right?" No it isn't. It was our aspirational goal that the SDL will get rid of every bug.'"

282 comments

  1. the bar is set so high. by yagu · · Score: 4, Interesting

    I have to sometimes wonder how, when security is considered so important, how Microsoft has been allowed to take so long. It's also a bit funny to consider how high the bar is set that they get credit for achieving "no longer the laughingstock..." status.

    It kind of reminds me of the cell phone industry and their "high" standard where they get away with advertising braggadocio like "the provider with the fewest dropped calls". It's funny, I grew up with a phone infrastructure where I never experienced a dropped call -- granted, a less complex (wired) achievement, but had "wired" phone service been invented today, I suspect the standard would have been "less dropped calls", too... because maximized profit dominates the industries' collective motivations, not quality products.

    (Case in point... if you'd ever owned the amazing Harmony() remote controls before they were bought by Logitech, they were wonderful devices -- rock solid, great feel to them... now, they're sexied up with cheap buttons, lousy feel, and questionable reliability. And get ready, Logitech just bought Slimline devices. Thought the Squeezebox was a great gadget? Better get the remaining quality ones before profit-think forges it into a cheap crappy imitation of it's former self.)

    And, to save you all a little time.... mod(self, -1, offtopic);

    1. Re:the bar is set so high. by nine-times · · Score: 2, Insightful

      It's also a bit funny to consider how high the bar is set that they get credit for achieving "no longer the laughingstock..." status.?

      Do you mean how low the bar is set? It seems kind of funny to me to hear someone from Microsoft admit that they were a laughingstock, and that they're looking for kudos for not being a laughingstock. It reminds me of Chris Rock's bit about people who brag, "I've never been to jail!" What do you want, a cookie?

      Anyway, I guess it's true that Microsoft has gotten more secure and therefore isn't as much of a security laughing stock. There's still something to make fun of in how annoying UAC is, but I guess it's better than what they had before. So... yeah, I guess I'll give it to him. Microsoft is no longer a security laughingstock. They're just a marketing laughingstock for producing the disaster that is Windows Vista.

    2. Re:the bar is set so high. by Captain+Splendid · · Score: 1

      And get ready, Logitech just bought Slimline devices.

      Fucking hell. I just went 10 rounds with a Logitech Quikcam and lost. Better splurge on that Squeezebox, I suppose...

      --
      Linux, you magnificent bastard, I read the fucking manual!
    3. Re:the bar is set so high. by Anonymous Coward · · Score: 0

      get an MX remote. they are way ahead of any Harmony remote in look/feel/programming.

    4. Re:the bar is set so high. by TheNetAvenger · · Score: 1

      I have to sometimes wonder how, when security is considered so important, how Microsoft has been allowed to take so long.

      You have to consider the product's market and the legacy of some of the products.

      When you had NO NETWORKING or DOS/Win95 based OSes that were NOT designed with ANY security, the hardest part has been moving the industry and 3rd party developers to even 'respect' or code for security. Vista is the first Version that 'requires' developers to code for security that are coming from the Win9x era of computing.

      Mac System users faced the same challenges, and Apple took the road to virtualize the System9 portion of the OS.

      Microsoft screwed up with XP and allowed everyday people and developers to write software that assumed it or the user had admin rights. This was a 'usuability' decision so it didn't break all the Win9X applications, but it also was a 'security' mistake in trying to compete with *nix, and even original NT itself that was all about security.

      So questioning the 'bar' you also have to have perspective. Consumer based OS models from the 90s had little to no security. And sadly this does include non-MS OSes from the same timeframe like OS/2, BeOS, System7-9, and even early Linux and other *nixes. (To make this point, put the 1997 Linux kernel and distribution on a server and put it on the Internet and count the seconds until it can and will be exploited.)

      I think it is strange that people seem the lack of security from the early 00s in MS products as a result of MS being inept in doing secure OSes, when they already had a good track record with NT until they moved it to be the next consumer version of Windows, and 'lightened' the security for application compatibility.

      I also realize though that a 'lot' of SlashDot users stopped using Windows or 'seriously' using it around the Win9x/ME era, and this is also sad, as the OS from that era is as far from XP and Vista as DOS is from Linux.

      Just like Vista, it in itself it not drastically more secure than XP SP2, but it does start the 'force' of getting 3rd party application and driver developers to take security seriously.

      Windows itself has not ever been a poor performer or horrible with security, but because the model from the 90s allowed 'too much' program access and customization (ie changing core system files) it left a lot of doors open that were not inherently insecure in the base OS, but as software from 3rd parties strapped into or replaced portions, stability and reliability became a nightmare for a lot of users.

      This is just like the debate in 'why' to upgrade to Vista, if none of the other features or reasons MS offers makes sense to a person or business, six months down the road the chance it will have reduced reliability or security due to 3rd party application bloat is virtually non-existent even in comparison to XP which started to do a pretty good job around SP2.

    5. Re:the bar is set so high. by HalAtWork · · Score: 1

      UAC is [...] better than what they had before

      Not by much... all it does is instead of solidifying their OS, they're putting you in charge of approving every interaction between user software/system software. They're putting up warnings in front of everything safe or not in order to make it your fault when something bad happens. The OS should be in charge of this, but MS is covering their ass by leaving it up to you because if you "allow" something that exploits the OS (even if it gave no indication of doing so prior), then it's your fault.

    6. Re:the bar is set so high. by Dr.+Stavros · · Score: 1

      </i>

      Phew, that was close.

    7. Re:the bar is set so high. by encoderer · · Score: 2, Interesting

      I LOVE how many people misunderstand what UAC is and what it will accomplish.

      I recently opined on this subject and I'd rather not retype it, so here's the copy/paste from a few weeks ago. Please excuse the parts that are obvious retorts and don't really apply here....

      1. I wasn't bashing Linux or OSX or anything else for being insecure. Well, I suppose you could say I was, but if you do, you'd have to acknowledge that I was bashing them all equally. And I certainly gave them credit for being more secure than Windows (the fence analogy, 9 feet vs 6 feet). As desperately as you want me to be, I'm not a windows fanboy or a microsoft apologist. If I were you could dismiss me. I'm a realist. Just that simple.

      2. If you think that UAC is "security by annoyance" than you are not seeing the big picture! As more and more people buy new computers with Vista (which is a predetermined reality. A truly bad OS could hurt MSFT, but not in one product cycle.), anyway, as people buy these computers, and load up their software, you're going to see--I believe--darwin-like natural selection occur. You're going to see Vista-friendly apps "selected" in the wild, making them more popular, which makes them more selected, and a positive feedback loop occurs.

      In a roundabout way--in a way much less destructive than your "break compatability" suggestion--the "annoyance" of UAC has driven users to more secure software. It's actually an inspired piece of psychology meeting software. They tried to make users care about security. They've promoted things like running only at the PowerUser level or below, running with aggressive IE security settings, etc. But users just don't care. A computer to them is a tool and nothing more and that's that. They want to just do what they want to do. So by creating UAC prompts for bad-actors and non-secure apps, it aligns the users interest with the interest of us security-minded folks. Not brilliant, but, perhaps, inspired.

      3. Only in the beatnik granola eating linux world (sorry for the stereotype) can anyone take seriously your suggestion for just breaking compatibility with every app that today throws a UAC. It's just not REALISTIC. It's not even utopian. It's an under-thought solution that suggests that there's no other way to solve the problem than to throw away BILLIONS AND BILLIONS of dollars worth of labor.

      Windows is a powerful brand. But again, most users see a PC as a tool and Windows is maybe like the toolbox. A good toolbox can make your life easier. Your suggestion is to make a toolbox that none of the users existing tools will fit into. But that would cause them to just throw out that toolbox. And they'd keep using the insecure software. What Microsoft is trying to do is point out in an in-your-face way that "the tool you just picked up is not safe to use." Over time, I find it likely that they'll replace their unsafe tools. People deep down WANT to conform, they WANT to meet expectations, they WANT to be responsible. But VERY few would just be cool with throwing out all their tools and never using them and replacing them all at once because their new toolbox said the tools were unsafe and wouldn't let them use them anymore.

      4. My point, for reiteration, is REALISM. We have a real problem. It's not just Microsofts problem. It's the entire software industry. Very few companies are concerned with making secure software. In all fairness, this wasn't an issue until the advent of the ubiquitous high speed internet connection, which hit critical mass no more than 7 years ago.

      We have to accept that this problem exists. And we have to accept reality:

      - Microsoft is not going away. Windows is not going away. Even if Microsoft never sold another copy of windows it would STILL be on hundreds of millions of computers for YEARS and YEARS to come.

      - Tens--even hundreds--of billions of dollars of software exists (both in-house and commercial) that relies on Administrator privs or otherwise insecure techniques. All of this software, every last byt

    8. Re:the bar is set so high. by wanderingknight · · Score: 1

      Well, actually, in *nix it's the same business: You need to acknowledge by yourself that you're allowing a certain program to run with administrative privileges.

      What Windows has screwed up is the ridiculous amount of unnecessarily provided rights the apps get. The administrator/user dichotomy has been completely forgotten in the Windows world for too long, which means most apps aren't coded to explicitly address this type of design, which also results in tons of badly designated privileges.

    9. Re:the bar is set so high. by QuietObserver · · Score: 1

      AFAIK, one thing *nix does that Vista doesn't is demand passwords for everything that requires administrative privileges without exception. Linux and MacOS X have always demanded that I authenticate myself whenever I'm trying to do something restrictive, even though I'm always logged in as an administrator on both machines, and sometimes, I'm asked twice. I've read and heard that UAC merely asks those logged in as an administrator to accept/refuse a request without asking for a password for anything it thinks requires more attention. IMO, that's a significant difference.

    10. Re:the bar is set so high. by drsmithy · · Score: 1

      AFAIK, one thing *nix does that Vista doesn't is demand passwords for everything that requires administrative privileges without exception. Linux and MacOS X have always demanded that I authenticate myself whenever I'm trying to do something restrictive, even though I'm always logged in as an administrator on both machines, and sometimes, I'm asked twice. I've read and heard that UAC merely asks those logged in as an administrator to accept/refuse a request without asking for a password for anything it thinks requires more attention. IMO, that's a significant difference.

      You can configure Vista to do this (and it does so by default when in a domain/managed environment).

      For a home/unmanaged user scenario, the difference between typing a password and clicking a button is zero. Indeed, if anything the former is worse as it is likely to encourage bad habits relating to passwords.

    11. Re:the bar is set so high. by drsmithy · · Score: 1

      Not by much... all it does is instead of solidifying their OS, they're putting you in charge of approving every interaction between user software/system software. They're putting up warnings in front of everything safe or not in order to make it your fault when something bad happens. The OS should be in charge of this, but MS is covering their ass by leaving it up to you because if you "allow" something that exploits the OS (even if it gave no indication of doing so prior), then it's your fault.

      Which is different from other OSes.... how, exactly ?

    12. Re:the bar is set so high. by rtb61 · · Score: 1
      Perhaps I could point out the most obvious security problem with Vista, WGA and DRM. What do works and viruses do, they deny you access to complete you work upon your computer, whether they delete your data, prevent you booting up, or just produce 'reduced functionality'.

      When WGA and (FU)DRM fail, they do exactly the same thing. So have the failed since Vista came out, the answer is yes, so Vista has a serious security flaw, the program itself. So now M$ is now a new kind of security laughing stock with built in virus features.

      When it comes to the customer's computers security, reliability and stability, M$ had better learn that piracy is it's fucking problem and not the customers who have bought and paid for the software.

      --
      Chaos - everything, everywhere, everywhen
    13. Re:the bar is set so high. by TheNetAvenger · · Score: 1

      WGA and DRM

      WGA is dead and being shut off, go read the news please...

      DRM in Vista is NO FREAKING different than DRM in XP, with the exception of the protected Video pipeline that allows for DRMed HD-DVD and Blu-Ray. Which all HD-DVD and Blu-RAY players on the market ALSO FREAKING HAVE. So next time you see a Toshiba HD-DVD player at Wal-Mart, yell to everyone it is crap because it is full of DRM.

      Geesh. Are people really stupid enough to believe people like the idiot writing papers on Vista DRM that hasn't even used Vista, when technical people and developers have continually refuted it over and over and over and over again...

      Vista locks you out of NOTHING, and can lock you out of NOTHING. I can even go in and change and remove any aspect of the OS, as you do have FULL CONTROL over the OS. People yelled about XP for the same reasons because it didn't let 'average' users or crap 3rd party software overwrite system DLLs without permission, everyone yelled that XP took away their control. Guess what, they were also freaking idiots, and have been proven wrong and wrong again countless times. Heck even look up old XP articles on SlashDot, you will hear the FUD of XP and why it is evil and restricts users, blah blah blah. Same crap, just insert Vista inplace of XP...

      This gets tiring, why can't people do research on something they care to comment on beyond 'SlashDot' or 'SlashDot' mentallity?

    14. Re:the bar is set so high. by Anonymous Coward · · Score: 0

      I kinda don't understand what you were looking for, these are all pretty basic examples... I really don't see how you think other OSes put you in charge of every decision... because on other OSes, every software interaction does not involve escalated priveledges that require you to approve them, but I'll try and be general...

      For one thing other OS's don't rely on bugs for backward compatibility, so they don't have to wrap everything in a sanity check that exploits can bypass and take advantage of.

      Another reason is permissions between different user levels are not well defined, and most applications require deep permissions to be able to do everyday things... security is not as fine-grained in Windows. Check out all of the ActiveX exploits.

      You still need to be admin to run certain apps, certain apps need to be run with elevated priveledges... you can't just do everything as a guest user. In other OSes, you can easily download and install applications just for the user, and not have it affect the rest of the system at all. You can effectively sandbox the user. This is really difficult in Windows.

    15. Re:the bar is set so high. by drsmithy · · Score: 1

      I kinda don't understand what you were looking for, these are all pretty basic examples... I really don't see how you think other OSes put you in charge of every decision...

      I am looking for a way UAC is meaningfully different to its equivalents in other OSes.

      because on other OSes, every software interaction does not involve escalated priveledges that require you to approve them, but I'll try and be general...

      "Every software interaction" in Vista doesn't involve escalated privileges either. Indeed, on the one Vista machine I have, I rarely see UAC dialogs - and never unexpectedly or unreasonably.

      For one thing other OS's don't rely on bugs for backward compatibility, so they don't have to wrap everything in a sanity check that exploits can bypass and take advantage of.

      What ? Windows doesn't "rely on" bugs for backwards compatibility.

      If you don't think other OSes remain bug-compatible with previous releases, I'm afraid you're sadly mistaken.

      Another reason is permissions between different user levels are not well defined, and most applications require deep permissions to be able to do everyday things... security is not as fine-grained in Windows. Check out all of the ActiveX exploits.

      No, they dont "require deep permissions" to be able to do "everyday things". While many badly written apps do stupid things like, say, store runtime data in system areas, or try to open system files read/write rather than read-only, this is not in any way the fault of Windows or Microsoft, nor is it "required" to be able to run a Windows application.

      You still need to be admin to run certain apps, certain apps need to be run with elevated priveledges...

      This has nothing to do with Windows. It is caused by incompetent (and/or lazy) developers.

      you can't just do everything as a guest user. In other OSes, you can easily download and install applications just for the user, and not have it affect the rest of the system at all. You can effectively sandbox the user. This is really difficult in Windows.

      Because of the *applications*, not Windows. There's nothing in Windows - in terms of either architecture or recommended best practices - that stops the scenario you are describing - *nor has there been for a decade or more*.

    16. Re:the bar is set so high. by turbidostato · · Score: 1

      "(To make this point, put the 1997 Linux kernel and distribution on a server and put it on the Internet and count the seconds until it can and will be exploited.)"

      I can take your challenge any day of the week and beat your ass out of the sand with one hand on my back.

      By 1997 no distribution left opened any network service after installation. Do you want telnet? Install it; do you want httpd? install it; do you want ftpd? Install it. I can bet that even installed today it will take more that "seconds" to exploit a Debian Bo, an Slackware 3.1 or a Red Hat 3.0.3. Try that with Windows 95 or Me.

      You *might* had a point if you were talking about something like Red Hat by year 2000 (and then, because they tried to emulate Windows' use easyness, loading a crapfull of services by default), but not on 1997.

  2. Says who? by A+beautiful+mind · · Score: 3, Insightful

    I'm sorry, respect in security is like with all kinds of respect. It is earned, not demanded or bought.

    --
    It takes a man to suffer ignorance and smile
    Be yourself no matter what they say
    1. Re:Says who? by morgan_greywolf · · Score: 4, Funny

      I'm sorry, respect in security is like with all kinds of respect. It is earned, not demanded or bought. But look [Allow | Cancel] "Allow" at how much more [Allow | Cancel] "Allow" secure Microsoft's [Allow | Cancel] "Allow" products are [Allow | Cancel] "Allow" today!

      How can you [Allow | Cancel] "Allow" say that they [Allow | Cancel] "Allow" are still a [Allow | Cancel] "Allow" laughingstock?

    2. Re:Says who? by cepayne · · Score: 1

      Apparently you aren't listening hard enough.....they are a security company now (cough, gag)

    3. Re:Says who? by Anonymous Coward · · Score: 0

      When was the last time we've seen a Code Red or Nimda? Nowadays Windows 2003 servers are rock solid and very secure. It's not perfect, but MS made a lot of progress in securing the OS.

    4. Re:Says who? by HartDev · · Score: 1

      Hahahahaha I bet that was very frustrating to write out, let alone have to deal with!

      --
      To see a few of my Android apps goto: www.hartwired.com
    5. Re:Says who? by mpapet · · Score: 3, Interesting

      You've never noticed the Microsoft public relations jugernaut then.

      I admin a combination of 2000/2003/2003r2 boxes and there are still things that make a security-minded sysadmin's head spin.

      -The boxes *still* advertise and have a great number of open ports.
      -Root is *still* is allowed remote access by default. System root, under a domain controller still advertises itself as ready and waiting for you to login.
      -Did I mention root remote control is still enabled by default?
      -I doubt most win32 sysadmins have any idea the number of undocumented systems logging in and doing who-knows-what to the system. If they configured and read their logs the way I do, at least a few of them would wonder what the heck is going on.
      -Don't get me started with their Rube Goldberg security objects system. Complex and extremely difficult to use, yet exceptions abound when trying to simultaneously harden a system and keep the undocumented features from throwing errors.

      Their security reputation has been purchased and PHB's everywhere are lulled into another false sense of security. The good news is I'll never run out of work because they require so much baby sitting compared to a Linux server.

      --
      http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    6. Re:Says who? by Anonymous Coward · · Score: 1, Informative

      -Root is *still* is allowed remote access by default. System root, under a domain controller still advertises itself as ready and waiting for you to login.

      What exactly do you mean by remote access? Are you talking about Remote Desktop being enabled by default? AFAIK it is disabled by default in Windows Server 2003. If you aren't talking about RDP, can you please elaborate what you mean by "remote access"?

      And what about a domain controller advertising itself? First of all, Windows Servers are not domain controllers by default. You either have to create a domain or promote a server to be a domain controller. Second of all, I don't know what you mean by advertising itself, other than some type of NetBIOS broadcasts on the network? As far as the server "waiting for you to login", thats the point of a domain controller. And it's not like anyone can just randomly log into the domain controller without proper authentication. Workstations/servers are required to join the domain using an account with proper credentials (at least "server operator" group I believe). If a computer is trying to access domain resources without being on the domain, they are still required to be authenticated.

    7. Re:Says who? by The+Faywood+Assassin · · Score: 1

      You are so right.

      Besides, this upgraded security will only be seen on the "next" version of its OS. Screw the millions of security vulnerabilities out there right now!

      --

      "I'm a humble person really,

      I'm actually much greater than I think I am"

    8. Re:Says who? by somersault · · Score: 3, Funny

      I wonder if anyone's ever tried 'cancel'.. I'm guessing that doing so would cause the machine to hang.

      --
      which is totally what she said
    9. Re:Says who? by Anonymous Coward · · Score: 0

      Yeah, I know what you mean. It's pretty gay how you have to authorize for each snap-in panel in the GUI configurator.
      http://gentoo-portage.com/up_img/img_800px/1453.png

    10. Re:Says who? by morgan_greywolf · · Score: 0, Flamebait

      That's Gentoo. This is unnecessary on Ubuntu, which uses 'sudo' instead of kdesu

    11. Re:Says who? by mpapet · · Score: 1

      AFAIK it is disabled by default in Windows Server 2003
      You would be wrong.

      Maybe my comments were too brief regarding servers in a domain controller environment. My point is there are still plenty of open ports and advertised services on a default win2k3 install either joined to a domain or not.

      --
      http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    12. Re:Says who? by dave562 · · Score: 0, Flamebait
      Parent is spewing FUD. I just did a net view on three different DCs and the only two shares advertised by default are NETLOGON and SYSVOL. Both of those are necessary shares for a DC to provide DC functionality to the clients they are supposed to serve.

      Remote Desktop is not enabled by default on a Win2K3 box. You need to explicitly turn it on. In fact even after you turn it on in default configuration, the Domain Admins group isn't even given rights to log on and needs to be explicitly granted those rights.

      I'm not quite sure what advertising the parent is talking about. The whole purpose of file servers and domain controllers is to serve up resources to network clients. The clients need to find those resources some how. Therefore the servers broadcast their status. Following the assumed train of logic, NBC has a huge problem. They're advertising these wacky TV programs that anybody can access... and they don't even authenticate who accesses them. Newflash... Microsoft more security than major television broadcasters!!

    13. Re:Says who? by morgan_greywolf · · Score: 2, Interesting

      I just did a net view on three different DCs and the only two shares advertised by default are NETLOGON and SYSVOL. That's correct, but I'm not sure where the grandparent was talking about shares.

      Remote Desktop is not enabled by default on a Win2K3 box. You need to explicitly turn it on. In fact even after you turn it on in default configuration, the Domain Admins group isn't even given rights to log on and needs to be explicitly granted those rights. Uh, no, I'm also pretty sure it's enabled by default.

    14. Re:Says who? by dave562 · · Score: 1, Informative
      Uh, no, I'm also pretty sure it's enabled by default.

      It's a good thing that you're not totally sure, because then you'd be TOTALLY wrong instead of just PRETTY wrong.

      http://www.windowsdevcenter.com/pub/a/windows/2004/05/04/serverhacks_remote.html

      From reading the above article it's clear that remote desktop isn't enabled by default and if you ship out a server to a remote location without enabling remote desktop, you have to do some registry tweaking to enable it.

    15. Re:Says who? by Anonymous Coward · · Score: 0

      I call BS on this one also. I've deployed numerous Win2K3 server boxes and it is in fact disabled by default. It is installed, but disabled.

      Here is a how to guide for remote administration:

      http://www.informit.com/articles/article.aspx?p=174352&rl=1

    16. Re:Says who? by dave562 · · Score: 1, Insightful
      Just to further emphasize the point with a quote straight from the horse's mouth...

      By default, Remote Desktop for Administration is installed when Windows Server 2003 is installed. However, Remote Desktop for Administration is DISABLED for security reasons.

      http://support.microsoft.com/kb/814590

      Now tell me, where did you get the idea that it is enabled by default? Certainly not from first hand experience... unless that experience is installing images that someone else created for you?

    17. Re:Says who? by mithras+invictus · · Score: 1

      ctrl-c, ctrl-v, ctrl-v etc?

    18. Re:Says who? by Anonymous Coward · · Score: 0

      I wonder if anyone's ever tried 'cancel'.. I'm guessing that doing so would cause the machine to hang.

      Historically (such as the infamous Abort, Retry, Fail) Microsoft uses a Zork interface: there's only one right answer and you won't get off that dialog until you give it.

    19. Re:Says who? by Anonymous Coward · · Score: 0

      Dave562, meet WMI.

    20. Re:Says who? by dave562 · · Score: 1

      Hahahahaaa!! I point out how someone is obviously spewing FUD, then back it up with factual information and that makes me a troll? Whoa! I wonder what alternate reality the guy with mod points is living in where sharing factual information makes someone a troll.

    21. Re:Says who? by dave562 · · Score: 1
      Oh noes... I shot down the anti-Microsoft FUD. I'm obviously flaming the original poster for his FREAKING IDIOCY and complete lack of comprehension of the subject he's talking about.

      Note to mods, this completely unnecessary post is -1 Flamebait, -1 Troll, or -1 Off-Topic. The original post of mine was just pointing out a factual error. It's a good thing I've got some karma to burn.

    22. Re:Says who? by morgan_greywolf · · Score: 1

      Dude...take a pill. The W2K3 machines I've built have been built from a standard image that has RDP for Administrator turned on by default, and this image was made by someone else (i.e., not me). I've never installed a Win2K3 machine from original media.

    23. Re:Says who? by scumbaguk · · Score: 1

      yep I've installed plenty and remote desktop is most certainly disabled upon install.

  3. Riggghhhht! by Mikkeles · · Score: 3, Funny

    Now we just snicker and giggle!

    --
    Great minds think alike; fools seldom differ.
  4. my opinion of MS security by Anonymous Coward · · Score: 0

    As a $1000 per hour Foundstone security consultant (you'd know my name, I'm extremely famous - ok I'll give you a hint, my name rhymes with Fan Darmer), I am inclined to agree. MS products are now completely secure. I know, because *I* can't hack them.

    1. Re:my opinion of MS security by BUL2294 · · Score: 5, Insightful

      Unfortunately, Microsoft's security problems are masked, not fixed. Seriously, software firewalls should not need to exist. All software firewalls do is cripple other code running on the OS (drivers, services, programs, etc). Fix the underlying code and don't default to running services that home users will never need and, presto, no need for a firewall...

      Someone at M$: "XP with IE is full of 'critical' security holes."
      Someone's manager: "Let's write a firewall and we can get away with calling those security holes 'important' and not fix them."

      --
      Windows 3.1x calc: 3.11 - 3.10 = 0.00
    2. Re:my opinion of MS security by deftcoder · · Score: 1

      Really?

      I use netfilter on my laptop running Debian Linux for various things, and it seems to do the job acceptable.

      Of course, I don't run any day-to-day programs as a user (read: root) who can actually use iptables to change my rules either.

      Oh well.

      --
      Peace sells, but who's buying?
    3. Re:my opinion of MS security by Akaihiryuu · · Score: 1

      Firewalls *are* a good thing, but only if they're implemented properly (see Linux/*BSD). A firewall should be an extra line of defense, not the only security on the system. The Microsoft way: "All services run with full privileges and listen on all interfaces. Wow, look at all these ports open, every single one of them is a huge security hole. Just put a firewall on it so noone can access them." The problem with this approach...firewalls (especially software firewalls running in Windows) can be breached (in Windows case, pretty easily). The *nix approach: "Don't open any unnecessary ports. Only have services listening on interfaces where they're needed. Don't run services as root or give them unnecessary privileges. There, now there's nothing exploitable exposed, so noone can break in. Now put a firewall on top of it." If I really wanted to, I could completely take the firewall down on my Linux server and not really be any less secure. Ideally, the actual security is in the OS itself. The firewall is just there as the furthest line of defense. In Windows there is NO security whatsoever and the firewall is the only defense. Bad design.

  5. Get that man a dictionary! by navygeek · · Score: 4, Funny

    No Longer a 'Laughingstock' of Security
    He keeps saying those words... I do not think they mean what the thinks they mean...
    1. Re:Get that man a dictionary! by provigilman · · Score: 3, Funny

      My name is Scott Charney, you laugh at my company, prepare to die.

      --
      "Life's short and hard, like a body building elf." -- The Bloodhound Gang
    2. Re:Get that man a dictionary! by Anonymous Coward · · Score: 0

      Yes, but he too is lefthanded!

  6. STILL the Laughing Stock! by tjstork · · Score: 0

    Now, Microsoft has Windows and IE asking so many security messages, that the users automatically say yes, once again, reducing all of their efforts to ashes. And you still can't run IE under a separate user account.

    --
    This is my sig.
    1. Re:STILL the Laughing Stock! by Bill+Wong · · Score: 5, Informative

      And you still can't run IE under a separate user account.
      Uh, sure you can?
      Shift-Right-Click -> Run-As -> The-Following-User?
      I do it all the time...
    2. Re:STILL the Laughing Stock! by alexhs · · Score: 2, Insightful

      Now, Microsoft has Windows and IE asking so many security messages, that the users automatically say yes, once again, reducing all of their efforts to ashes. When a program ask the user to "confirm" (without even authentification) for each byte it receives from the network (without much clue about the signification of that byte), you can't say the user is reducing their security efforts to ashes. Asking the user to be the IP stack is not the solution.

      I'm exagerating of course, but I hope you get the point, asking an uneducated user is not a security measure.

      And you still can't run IE under a separate user account. I think you're wrong on that point, there's no reason runas wouldn't work.
      --
      I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
    3. Re:STILL the Laughing Stock! by MyLongNickName · · Score: 1

      I'm exagerating of course, but I hope you get the point, asking an uneducated user is not a security measure.

      You are severely exaggerating this. I get them message a lot, only because I do a lot of configuration. But overall, the average user will only get questioned on things that are really important. If you are saying the average user cannot even be trusted to do this, then you may as well have Microsoft hold the administrator account, and you need to call them to install anything (at a small fee).

      Overall I hate Vista with a passion. See my prior comment in the history for evidence of this. However, I believe they have made great strides in the security realm.

      --
      See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
    4. Re:STILL the Laughing Stock! by Anonymous Coward · · Score: 0

      Now, Microsoft has Windows and IE asking so many security messages, that the users automatically say yes, once again, reducing all of their efforts to ashes. And you still can't run IE under a separate user account. Moderators are on crack again? Why is this modded "insightful"? It's full of false information.

      First, have you ever run IE7? The only security warnings you get are for Radioactive-X controls (which nowadays no major site has any). And those who have em, are probably malware anyways. So you are better off with a warning. And second, the other warning you get from IE are for SSL certificates the browser can't validate properly (fake, self signed, whatever...). The same stuff Firefox will also warn about. So what are these "many" security warnings? Every fricking browser will warn you about SSL stuff and executables. Not saying IE7 is perfect, but let's not spread FUD ... oh wait, it's ./. My bad.

      Then there is IE running under separate user account. Hit the start menu. Hit execute. Type in cmd.exe and hit enter. You will see a command prompt appear. Now in that window type runas /user:(username) iexplore. Tada! Done. You can also simply create a shortcut and right click and select run as option.

      I wish people like you would start actually using IE and Windows before spreading FUD...
    5. Re:STILL the Laughing Stock! by GreyPoopon · · Score: 4, Funny

      Now, Microsoft has Windows and IE asking so many security messages, that the users automatically say yes, once again, reducing all of their efforts to ashes. And you still can't run IE under a separate user account.

      You are considering becoming complacent and answering yes to all security pop-ups. Accept or Deny?
      --

      GreyPoopon
      --
      Why is it I can write insightful comments but can't come up with a clever signature?

    6. Re:STILL the Laughing Stock! by 0p7imu5_P2im3 · · Score: 1

      Now in that window type runas /user:(username) iexplore. I don't know about Vista, but that wouldn't work in XP. You have to specify the entire path to iexplore because the IE directory is not in the PATH environment variable.
      --
      Resistance is futile. Your technological distinctiveness will be added to our own. You will become one with the morgue
    7. Re:STILL the Laughing Stock! by Anonymous Coward · · Score: 0

      asking an uneducated user is not a security measure.

      But combined with appropriate phrasing in the EULA, it can create the perception that any legal responsibility for security breaches is shifted squarely to the user. Security thus becomes a simple matter of user training (ooh, that's SMUT!)

      That clear shift in responsibility helps secure Microsoft's continued profits and market dominance. In general, smutty security practices are a good thing for they advance the core stuff Microsoft is all about.

    8. Re:STILL the Laughing Stock! by Anonymous Coward · · Score: 0

      Yeah, changing the display settings is really important.

    9. Re:STILL the Laughing Stock! by Anonymous Coward · · Score: 0

      Now, Microsoft has Windows and IE asking so many security messages, that the users automatically say yes, once again, reducing all of their efforts to ashes
      But now any security failures are the users' fault, not Microsoft's. Buck passed! Mission accomplished!
    10. Re:STILL the Laughing Stock! by Malc · · Score: 1

      Stop splitting hairs. The message was clear. If one were to do use that command often enough then presumably one would add it to the path, which makes it technically correct too.

    11. Re:STILL the Laughing Stock! by Malc · · Score: 1

      And Aaron Margosis' blog explains how to make it more useful (PrivBar).

    12. Re:STILL the Laughing Stock! by 0p7imu5_P2im3 · · Score: 1

      One of the issues with Windows is LCD (Lowest Common Denominator). If you don't spell it out almost exactly (which I, too, am guilty of) most Windows users will type the command exactly as you said and when it doesn't work most Windows users will assume that you were wrong and not research the mistake. Most Windows users think that the PATH has something to do with religion. :)

      In other words, I was just trying to help. I apologize for offending you, Malc.

      --
      Resistance is futile. Your technological distinctiveness will be added to our own. You will become one with the morgue
    13. Re:STILL the Laughing Stock! by Anonymous Coward · · Score: 0

      In all seriousness - is "authentification" even a word?

    14. Re:STILL the Laughing Stock! by Anonymous Coward · · Score: 0

      This was changed in IE7. I used to to use the *Shift-Right-click* method in IE5 and IE6 to run installs in Windows Explorer aka Internet Explorer from a non-admin account. As of IE7, however, this has been disabled and I don't know of any way to Run IE As...

    15. Re:STILL the Laughing Stock! by Anonymous Coward · · Score: 0

      as someone else in the thread mentioned, you can't do this to the icon on the desktop, you have to do it via the taskbar's quick launch or via the start menu. HTH

    16. Re:STILL the Laughing Stock! by Orethrius · · Score: 1

      You are considering becoming complacent and answering yes to all security pop-ups. Accept or Deny? *Deny*

      You are considering becoming complacent and answering yes to all security pop-ups. Accept or Deny? *Deny*

      You are considering becoming complacent and answering yes to all security pop-ups. Accept or Deny? *DENY*

      ...ad nauseum.

      All UAC has succeeded in doing is increasing my anxiety over the day when I finally click "Deny" only to be met with:
      You failed to turn on the light and have been eaten by a grue.

      --
      Now back to my regular pseudo-scientific reading.
    17. Re:STILL the Laughing Stock! by Nazlfrag · · Score: 1

      It's just authentication.. aww geez being a grammar nazi is no fun when someone asks politely.

  7. rear-view mirror by Anonymous Coward · · Score: 5, Interesting

    Inasmuch as this constitutes any sort of admission that Microsoft products were not always exemplars of good security, it should not be forgotten that Microsoft has always insisted that they were.

    So really, they are not saying anything different than they have always said. "Back then" when their products were insecure, they insisted that their products were secure. Now, they are admitting that "back then" their products were not secure, and are continuing to insist that their products are secure.

    Why should we believe them? Once bitten, twice shy, and with good reason.

    1. Re:rear-view mirror by darkonc · · Score: 3, Insightful
      In other words, the headline really should be:

      Microsoft Finally Admits Lying About Security
      Admits that security is still bad, but claims to be no longer 'laughing stock' bad.
      --
      Sometimes boldness is in fashion. Sometimes only the brave will be bold.
    2. Re:rear-view mirror by Jerry · · Score: 2, Informative

      Especially in view of these results, where Microsoft's "OneCare" detected only 90% of new malware thrown at it:
      http://www.av-comparatives.org/seiten/ergebnisse_2007_08.php

      Those results are in improvement. The March results had them finding only 82%. Meanwhile, much more viable commercial products are around 99+%. Still, even for them, letting 50 out of every thousand bugs in doesn't say much about their security, even if OneCare is so much worse.

      --

      Running with Linux for over 20 years!

    3. Re:rear-view mirror by ozmanjusri · · Score: 1
      AV detection rate comparisons tend to be somewhat questionable. Many of the testers are sponsored by anti-virus vendors.

      It's a shame Clamwin/Winpooch wasn't included in the test - it normally scores resonably highly (http://advosys.ca/viewpoints/2007/08/clamav-beats-mcafee-and-norton/), and it would have been nice to see how Microsoft's effort compares to that of some unpaid volunteers.

      --
      "I've got more toys than Teruhisa Kitahara."
    4. Re:rear-view mirror by Jace+of+Fuse! · · Score: 1

      "claims to be no longer 'laughing stock' bad."

      They're probably more like 'running joke' bad now.

      --

      "Everything you know is wrong. (And stupid.)"

      Moderation Totals: Wrong=2, Stupid=3, Total=5.
  8. not there yet by Reader+X · · Score: 2, Interesting

    I concede that MS is not the laughingstock that it once was, but they are a ways from the respect that some of their competitors of similar scale (cough*IBM*cough) have long since earned. Eliminating the repeat vulnerabilities such as the recent ANI vuln might be a good place to start.

    1. Re:not there yet by Anonymous Coward · · Score: 0

      Ah, but it is worthy to note that in Vista it was not possible to exploit the ANI vulnerability through a malformed animated cursor on a web site using Internet Explorer 7.0 with default security settings. Well, technically, yes, it was possible to exploit, but because the process was sandboxed the malicious payload would not be capable of causing any damage to the system, even to the current user's own profile.

      Vulnerabilities will pretty much always exist. Good programming practices will help to reduce them considerably but all it takes is a little mistake, or a third party plugin, and you're back in the same situation. This is not a situation unique to Windows. The best we can really do is to reduce the attack surface for directed attacks and attempt to mitigate the damages for user initiated malware. Jail the browsers, as Vista is doing, so if the user does happen to visit a site that contains a payload, even in a third party plugin, the malware can't do anything.

    2. Re:not there yet by Rob+the+Bold · · Score: 1

      I concede that MS is not the laughingstock that it once was, but they are a ways from the respect that some of their competitors of similar scale . . .

      I've had this thing as a triple sell, and I am upgrading it, right here, right now! I think this thing could even go as high as a "Don't Buy."

      --
      I am not a crackpot.
    3. Re:not there yet by Anonymous Coward · · Score: 0

      I assume you know the poster. ;-)

  9. I say, set a standard by downix · · Score: 5, Interesting

    I'm thinking (in part to stroke Theo's ego a bit) set OpenBSD as the security standard out there. Every OS, compare it security-wise to OpenBSD. Put a "percentage" for how secure, then we can see hard numbers for how securly an OS is out of the box.

    --
    Karma Whoring for Fun and Profit.
    1. Re:I say, set a standard by Barny · · Score: 1

      Hey, that could be good, since it would be an "out of the box" test, it might even stop MS from having IE as part of the OS.

      "where would you like to go tod..."

      "ahh shit, its got smitfraud again"

      --
      ...
      /me sighs
    2. Re:I say, set a standard by 0p7imu5_P2im3 · · Score: 0, Troll

      The only thing OpenBSD sets a standard for is having a complete cockshiner in charge of the project.

      If you want a project with a world class cock wallet in charge, look to OpenBSD. ... or look to Microsoft...
      --
      Resistance is futile. Your technological distinctiveness will be added to our own. You will become one with the morgue
    3. Re:I say, set a standard by forrestt · · Score: 1

      I say do it the other way around. Make Windows the standard and measure every other OS in Window Security Units. Then you can have a measurement on the box sort of like how Scoville Units are used for hot sauce.

    4. Re:I say, set a standard by the_humeister · · Score: 0, Flamebait

      I don't think that's quite fair since the base OpenBSD distribution that's audited doesn't include things such as X Window. Maybe a better comparison would be Mac OS X?

    5. Re:I say, set a standard by SwordsmanLuke · · Score: 1

      Or... we could pay more attention to the OS security standards which already exist, such as the one the DOD uses: http://en.wikipedia.org/wiki/TCSEC

      --
      Any plan which depends on a fundamental change in human behavior is doomed from the start.
    6. Re:I say, set a standard by renoX · · Score: 1

      I disagree with the moderator that the parent (assuming that he's right when he says that OpenBSD project doesn't audit X) is flamebait: not auditing X is perfectly reasonable for a server usage, but of course not for workstation/desktop usage.

      So indeed securing a desktop PC is *much* harder than securing a server: you cannot assume that the user know how is working the PC and there are much more software installed, etc.

  10. Yeah, unrealistic by hotfireball · · Score: 1

    The challenge is really quite often in dealing with unrealistic expectations.
    Rather unrealistic results... Windows is really wonderful: full of things to wonder about.
  11. Of COURSE they're not the laughing stock... by 15973 · · Score: 5, Funny

    ...now if you'll excuse me, I have to go delete the spam that was sent from a botnet of computers that are running a series of a particular OS that shall remain nameless...

    1. Re:Of COURSE they're not the laughing stock... by MyLongNickName · · Score: 1

      If a user becomes a part of a botnet because the user just must download the cool new toolbar, is it the fault of the OS? If the user chooses to use administrator privileges? What stops a linux box from being the victim of a similar program?

      --
      See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
    2. Re:Of COURSE they're not the laughing stock... by Spy+der+Mann · · Score: 2, Insightful

      Not all botnets are spread with a browser toolbar. Most of them infect unpatched machines via insecure open ports. Linux is safe from these, while Windows is not. My specific concern is pirated machines which CANNOT be patched due to Microsoft's policies (see my nearby post).

    3. Re:Of COURSE they're not the laughing stock... by mattpalmer1086 · · Score: 4, Insightful

      Yes, it is the fault of the OS. No, linux isn't any better in this regard. They all essentially use the multi-user (on a single box), non-networked security models devised in the late 60s and early 70s.

      Why should downloaded (i.e. tainted / potentially unsafe) code have any rights at all except to its own files by default? Should it be able to read your documents, open a network connection and send them out? Should it be able to format your disk? Hell, why even have a globally accessible file system at all?

      We can't improve the users much, so we're going to have to improve the OS. Actually, some of the early security models were much better than the ones we use now, but carried too much overhead for the machines of the day.

    4. Re:Of COURSE they're not the laughing stock... by badboy_tw2002 · · Score: 2, Interesting

      I think the Singularity OS (interestingly enough its being developed at Microsoft Research) has a pretty cool model of forcing components in the system to only interact over a well established contract. They also have the concept of installing built into the OS, such that only verified code can be built into the system. If you can't run a malicious program and it can't get out of its box, what can it do? I just wish they would release more to the public for outside analysis of their ideas.

    5. Re:Of COURSE they're not the laughing stock... by Anonymous Coward · · Score: 0

      Ok, but what are you going to do with a program that can't read your documents, can't open a network connection, and has access only to its own files? And how do you differentiate between a downloaded program, one that is installed from local media, and one that comes with the OS? If the program is going to be of any use to the user, it will need to be able to do certain things like opening a network connection or reading their documents. If those require some special permission then inevitably there is going to be a method for the user to enable it (either by prompting them for permission a la Vista or performing a check against a blacklist/whitelist, which can probably be modified by the user anyway). If the user is physically sitting at the computer they can get code to run; there is no way around that. It sounds like you are just trying to make it harder for dumb users.

    6. Re:Of COURSE they're not the laughing stock... by drsmithy · · Score: 1

      Why should downloaded (i.e. tainted / potentially unsafe) code have any rights at all except to its own files by default?

      The question is, does the end user get to decide whether or not to override those defaults ? Because if they can, all you do with the much more complex model is buy a few more "are you sure" dialog boxes.

    7. Re:Of COURSE they're not the laughing stock... by RobertM1968 · · Score: 1

      I think the Singularity OS is probably as real as whatever Vista was supposed to be - or even XP for that matter.

    8. Re:Of COURSE they're not the laughing stock... by mattpalmer1086 · · Score: 1

      Agreed, the way that the additional complexity is managed will be key to its success. But it's also true that abstracting out some the current mess may actually simplify its management.

      For example, at present network access policy is left up to individual applications - your browser has a policy, java has a policy, etc. None of these things can be centrally controlled or managed. You are left to rely on a software firewall to block outgoing connections, but you can't enforce more interesting policies or consistent ones, for example, e.g. same sender policies. Non technical users won't even try to understand all of that. If we centralise access control to the network, we can reduce the overall amount of work to be done, and make more transparent to the user what is actually going on.

      I'm very much against the idea that users are dumb (not that I'm saying you said that). I prefer to believe that our systems and metaphors are dumb. The old paradigm is that a computer is a hotel. We are in full control of our own room, but have no knowledge or control over the other rooms. We can send messages to other rooms, but we don't receive guests.

      Our current paradigm is that we leave our door open to any visitor, invited or otherwise, and we hardly know who anyone is, or even if they are there or not. We need a way for non-technical people to intuitively understand what is safe and what is not, and to be able to manage those risks in the same way that they very capably do in the physical world.

  12. Botnets by Megane · · Score: 3, Insightful

    So Microsoft is so secure that those botnets with hundreds of thousands of zombie computers running Windows will disappear overnight? Great!

    --
    #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    1. Re:Botnets by Jugalator · · Score: 1

      Those computers will never stop being zombies until they're 1) patched up with security fixes, and 2) cleaned of trojans. There's nothing magic that makes these Windows installs zombies and somehow still not being infected. There exist plenty of antivirus tools for Windows, and they're intended for the kind of users who're either novices or careless or both. The kind of users who're at risk at without knowing it support spam networks.

      I will never blame Windows for allowing a trojan to install if it was granted admin privilegies by a user, as little as I will blame Linux to run a trojan that wipes more or less of the distribution under granted root privilegies.

      The ONLY thing I think can be argued here is whether Microsoft should include an antivirus tool or not, but there's really no way MS can win that. If they don't, they're blamed for not caring enough for Windows security and attacking viruses, and if they do, they're abusing their market position. I don't envy the CEO at Microsoft for his job, even if what he ran was a company with better reputation.

      --
      Beware: In C++, your friends can see your privates!
    2. Re:Botnets by turbidostato · · Score: 1

      "The ONLY thing I think can be argued here is whether Microsoft should include an antivirus tool or not"

      I never ran an antivirus on any unix-like system I ever administered -except for mail and fileservers for Microsoft-based clients, not even Internet-facing servers.

      Why do you assume a Microsoft OS *must* carry an antivirus (either provided by Microsoft or any other thir party) when no other OS seems to need one? Maybe the "Microsoft" part on the "Microsoft OS" expression is the culprit?

  13. A good example - IIS by duplicate-nickname · · Score: 5, Insightful

    I think a good example of this is how many security problems have been found in IIS in recent years. For example, go to the MS Security Bulletin site and look up bulletins for IIS 6.0 compared to IIS 5.0 -- http://www.microsoft.com/technet/security/current.aspx.

    There are only two "Important" bulletins for IIS 6, while IIS 5 has almost 30 bulletins over the same inital time period. It is amazing how far IIS has come since that nightmare that was IIS 4.

    --

    ÕÕ

    1. Re:A good example - IIS by porkThreeWays · · Score: 1

      IIS and SQL server were the biggest laughing stocks. The slammer worm (I think that was it anyway) was the fastest spreading worm ever at the time. It may still hold this record. It spread around the world in just a few minutes. While I would still only say their security is average and many times they don't take it seriously, they had a responsibility to their shareholders to clean up their act after the many embarrassing SQL server and IIS worms. It's not nearly as bad as it was at its crest.

      --
      If an officer ever threatens to taze you, say you have a pacemaker.
    2. Re:A good example - IIS by UncleTogie · · Score: 2, Insightful

      ...and Microsoft doesn't play down threats? Hark to the ol' l0pht website:

      Microsoft - ""That vulnerability is completely theoretical."
      l0pht - "Making the theoretical practical since 1992." ...and thanks for the laugh!
      --
      Don't tell me to get a life. I'm a gamer; I have LOTS of lives!
    3. Re:A good example - IIS by asuffield · · Score: 5, Interesting

      There are only two "Important" bulletins for IIS 6, while IIS 5 has almost 30 bulletins over the same inital time period. It is amazing how far IIS has come since that nightmare that was IIS 4.


      You do realise that you are measuring the "quality" of IIS by counting the number of security flaws that Microsoft will admit to having fixed?

      You're not counting the number of known flaws. You're not counting the number of flaws that Microsoft knows about. You're not even counting the number of flaws that they've actually fixed. You're interpreting this change in the numbers as indicating an improvement, when it might just as easily indicate that they fix less flaws than they used to.

      And don't forget that Microsoft has a long history of not bothering to fix security flaws until significant numbers of exploits have been noticed in the wild. We can only guess at how many unfixed flaws there are in IIS today.
    4. Re:A good example - IIS by masdog · · Score: 2, Insightful

      Slammer was embarassing, but that one was hardly Microsoft's fault (although they do share some blame). They had released a patch for that vulnerability six months before the attack occurred.

      Security isn't just something you can pin on the software vendor and expect them to solve all your problems. It takes good system admins to keep the systems up-to-date with security patches and have them on a network that is designed for security.

    5. Re:A good example - IIS by duplicate-nickname · · Score: 1

      No doubt you are correct about counting bulletins, but that doesn't invalidate my point that IIS has become much more secure over the years. Maybe you could point out to us how IIS 6 contains many more unpatched vulnerabilites compared to IIS 5 or IIS 4?

      Also, take into consideration how IIS 6 finally installs with most features/filters/add-ins disabled by default, where as previous versions enabled rarely used features and dropped insecure .vbs scripts into your site by default.

      --

      ÕÕ

    6. Re:A good example - IIS by Blakey+Rat · · Score: 1

      Except Slammer was patched months before the attack happened. How is it Microsoft's fault that a lot of MS-using system administrators hadn't installed the patch?

    7. Re:A good example - IIS by king-manic · · Score: 1

      I think a good example of this is how many security problems have been found in IIS in recent years. For example, go to the MS Security Bulletin site and look up bulletins for IIS 6.0 compared to IIS 5.0 -- http://www.microsoft.com/technet/security/current.aspx.

      There are only two "Important" bulletins for IIS 6, while IIS 5 has almost 30 bulletins over the same inital time period. It is amazing how far IIS has come since that nightmare that was IIS 4.


      Third party vendors are to blame as well. I had to install a proprietary DB and web front end that required me to allow "full control" to everyone (basically chmod a+rwx) to several virtual directories. These directories contained executables (.dll and .ASP). You can imagine what a gaping security whole this is.

      --
      "There are more things in heaven and earth, Horatio, than are dreamt of in your philosophy."
    8. Re:A good example - IIS by Anonymous Coward · · Score: 0

      "They had released a patch for that vulnerability six months before the attack occurred."

      Ummm....no. Look into the details a bit more. True, they had released a patch that fixed the vulnerability. However, they later released a patch that reintroduced the vulnerability. (Version control is hard, I will admit.) If you applied all the patches Microsoft had said to apply, you were at risk.

    9. Re:A good example - IIS by I'm+Don+Giovanni · · Score: 3, Insightful

      IIS 6 Vulnerability Report since 2003:
      Three vunlerabilies, none classified as "highly" or "extremely" critical, all patched.

      Apache 2.x Vulnerability Report since 2003
      33 vunlerabilies, 3% classified as "highly" critical, 9% unpatched, 3% only partially patched.

      Sorry, I know if offends the delicate sensibilites of slashdotters, but IIS6 has a virtually perfect record since its release.
      You spouted a lot of speculation that IIS6 has tons of undisclosed flaws, but you've provided zero evidence. If there are so many flaws, why have they not manifested themselves? Microsoft is better on security than they were in the past, whether you like it or not. Deal with it.

      --
      -- "I never gave these stories much credence." - HAL 9000
    10. Re:A good example - IIS by asuffield · · Score: 1

      You spouted a lot of speculation that IIS6 has tons of undisclosed flaws, but you've provided zero evidence.


      You've spouted a lot of speculation that IIS6 doesn't have tons of undisclosed flaws, but you've provided zero evidence. I claim that my evidence is at least as good as yours. Deal with it.
    11. Re:A good example - IIS by Anonymous Coward · · Score: 0

      I'm sorry, but no such claims were made by the parent. You fail at reading comprehension.

    12. Re:A good example - IIS by Anonymous Coward · · Score: 0

      seriously you think that means anything?

      I've just had to put together the release notes for the latest version of a product, which involved getting the list of all the changes, formatting it in a nice document & deleting all the things which we don't want the customers to know that we had to fix.

      Anyone who thinks that any commercial software company actually tells its customers the truth about the quality of its product obviously has never worked in such an environment.

    13. Re:A good example - IIS by lmpeters · · Score: 1

      You spouted a lot of speculation that IIS6 has tons of undisclosed flaws, but you've provided zero evidence. If there are so many flaws, why have they not manifested themselves?

      I don't claim to be an expert, but Microsoft does have a history of hiding and/or denying the existence of bugs, and/or patching them secretly (i.e. patching them in a patch that is advertised as fixing a less serious bug). As long as there is no evidence that they have improved in this regard, I think it is fair to assume that they are still as dishonest as they have been in the past.

      Or is there new evidence I don't know about that Microsoft is being more forthcoming about security flaws?

    14. Re:A good example - IIS by naetuir · · Score: 1

      Why is it that people on slashdot feel compelled to put each other down? But since that is apparently what we are doing..

      If you want to talk about statistics (which there is a reason they have the saying 'there are three types of lies: lies, damn lies and statistics'), then at LEAST have some basic understanding that when you do want to use them, you need to find the right metric, and verify its validity.

      Microsoft does not publish (nor are they likely ever to) how they arrive at their patches. The same cannot be said about Apache. I know I certainly haven't seen a [bugzilla|Jira|other-bug-tracking-webapp] site for IIS. For all we know they could have 100 critical flaws that were all rolled up into the one patch release.

      If you could please point me in the direction of Microsoft bug tracking application (assuming that they religiously keep that up as the Apache-people do), I would be happy to provide some real, valid statistical feedback for you.

      Until then, stop comparing apples to oranges. It'll make all of us that have an understanding of Microsoft business practices feel better.

      --
      Use what works.
  14. Old, coroded, closed, insecure "standards" by 0p7imu5_P2im3 · · Score: 1

    I'm just surprised that the various governments of the world have let so many state secrets get locked up in Microshaft's closed, insecure standards. If Microshaft ever folds, the only people that will be able to access those old documents that tell you how to turn off that automated attack system of yestercentury are the Chinese hackers.

    --
    Resistance is futile. Your technological distinctiveness will be added to our own. You will become one with the morgue
    1. Re:Old, coroded, closed, insecure "standards" by Anonymous Coward · · Score: 0

      I dare you to name one serious competitor to the office suite that is not able to open ms word or ms excel files.

      The formats to all of MS's core office suite products are well known and any country that is worth its salt (Including China) DOES have access to the windows source code.

  15. Aim higher? by GigaHurtsMyRobot · · Score: 0

    They should really set their goals a little higher... You could as least aspire to fix everything, even though you probably won't.

    1. Re:Aim higher? by Anonymous Coward · · Score: 0

      They should really set their goals a little higher... You could as least aspire to fix everything, even though you probably won't.

      I think what Microsoft has done is genius. They created a multi billion dollar security industry who's sole purpose is to plug holes in software and all they had to do was nothing. The less they do.. the bigger the industry gets. Now they can slowly begin to squeeze the other companies out of this sector and make even more money.

      UAC is nothing more to Microsoft than an excuse, a way to shift blame to the user. Now when a machine is compromised, they can blame it on the user clicking Allow.

  16. Moved on... by Anonymous Coward · · Score: 0

    moved on from being the 'laughing stock' of the IT industry to something more respectable Yeah, now it's the giggling stock of the IT industry.
  17. Serious computing indeed by Dystopian+Rebel · · Score: 1

    There's no question that Microsoft is responsible for some of the most powerful computing initiatives in the world today.

    Redmond's other bots will want to set the record straight.

    --
    Rich And Stupid is not so bad as Working For Rich And Stupid.
  18. Use "Runas" in a command prompt by 0p7imu5_P2im3 · · Score: 1

    Yeah, you can. Right-click and choose "Run as..." or pull up a command prompt and use the "Runas" command specifying a separate user and pointing to "C:\Program Files\Internet Explorer\iexplore.exe"

    It may not be exactly like that in Vista but it works perfectly in XP even if explorer has been blocked for alternate users.

    --
    Resistance is futile. Your technological distinctiveness will be added to our own. You will become one with the morgue
  19. Translation by symbolset · · Score: 1

    It's not funny any more.

    Was it ever?

    --
    Help stamp out iliturcy.
  20. MIcrosoft guy says MS's security is ok? by jcr · · Score: 3, Insightful

    Sorry, I don't see why this story is even here. Microsoft has been telling bald-faced lies about their security for at least a decade. What's different this time?

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
    1. Re:MIcrosoft guy says MS's security is ok? by jimicus · · Score: 1

      So has every other commercial vendor. Oracle are a particularly good (bad?) example but SunOS was famously insecure, as was Irix.

    2. Re:MIcrosoft guy says MS's security is ok? by Toreo+asesino · · Score: 2, Informative

      See for yourself:

      SQL Server 2005 - http://secunia.com/product/6782/?task=advisories

      IIS6 - http://secunia.com/product/1438/?task=advisories

      Vista too is looking good so far too, but it's very new, and only time will tell - http://secunia.com/product/13223/?task=advisories.

      --
      throw new NoSignatureException();
    3. Re:MIcrosoft guy says MS's security is ok? by OffTheLip · · Score: 1

      I think the analogy being made here is they now suck less. That's not to say MS security is okay.

    4. Re:MIcrosoft guy says MS's security is ok? by AusIV · · Score: 1

      Sorry, I don't see why this story is even here. Microsoft has been telling bald-faced lies about their security for at least a decade. What's different this time?
      This time they started out by admitting that their security used to be lacking. Clearly they started out being honest, they're going to be honest throughout the entire statement.
    5. Re:MIcrosoft guy says MS's security is ok? by TheRaven64 · · Score: 5, Interesting

      SunOS was famously insecure, as was Irix. Why pick on just two vendors. It wasn't until the '90s that anyone could say 'UNIX security' without laughing. Take a look at the CVS logs from the first year of the OpenBSD project, when they first did a full audit on code much of which dated back to the original BSD UNIX, used as a base by a lot of commercial UNIX vendors and found hundreds of vulnerabilities. Now, OpenBSD enjoys a good reputation for security, but it's taken over a decade of continuous code auditing to get there.
      --
      I am TheRaven on Soylent News
    6. Re:MIcrosoft guy says MS's security is ok? by homer_ca · · Score: 2, Interesting

      Oracle is much worse. Look at archives of the Bugtraq list around the time of their "Unbreakable" marketing campaign.

    7. Re:MIcrosoft guy says MS's security is ok? by jcr · · Score: 1

      This time they started out by admitting that their security used to be lacking.

      Well, they've done that every time they shipped a new version of Windows. Part of the sales pitch has always been "Security: this time, for sure!"

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    8. Re:MIcrosoft guy says MS's security is ok? by rs232 · · Score: 1

      "Take a look at the CVS logs from the first year of the OpenBSD project"

      "Only two remote holes in the default install, in more than 10 years!"

      --
      davecb5620@gmail.com
    9. Re:MIcrosoft guy says MS's security is ok? by TheRaven64 · · Score: 1

      Yes. Now look at the CVS logs from between forking the project from NetBSD and the first OpenBSD release, as I said. You will see hundreds of security fixes as a result of that first complete audit.

      --
      I am TheRaven on Soylent News
  21. Pardon? by kaiwai · · Score: 2, Insightful

    No longer a laughing stock?

    Mate, people have stopped laughing, not because Microsoft has changed but because we've become so desensitised to the security issues it no longer brings the same attention it used to; its expected.

    If Microsoft do want to correct their security issue, they need to start at the bottom and work their way up; they need to go through their product, they need to document, clean up, remove parts that are security risks, replace parts which are added because they're nice rather than needed. They need to stop the lie that 'computers are easy to use' when in reality, they're complex machines that actually might require a bit of book reading and learning (to the screams of the ignorant out there).

    They also start needing to stop re-inventing the wheel and start working in groups; yes, groups are inefficient but like any brain storming, issues are raised which the original author might not have thought about - when you're an organisation all thinking along the same line, you can't adequately scrutinise the specification for every possible scenario - that is why standardisation is desirable. Issues of compatibility and security can be raised, and addressed. Microsoft on the other hand thinks because it has the cash and are a big organisation, it can address all the concerns internally.

    1. Re:Pardon? by truesaer · · Score: 1
      Mate, people have stopped laughing, not because Microsoft has changed but because we've become so desensitised to the security issues it no longer brings the same attention it used to; its expected.


      Despite all the bleating about how security is as bad as ever, it simply isn't true. A current version of XP is pretty secure, comes with a firewall, recommends anti-virus software to users, the browser has anti-phishing technology, etc. You would almost have to try to get infected on an up to date version of windows. If it were as bad as it was before why haven't there been any more iloveyou or other crippling vulnerabilities since SP2?

    2. Re:Pardon? by businessnerd · · Score: 2, Insightful

      why haven't there been any more iloveyou or other crippling vulnerabilities since SP2?
      Partly due to the maturation of the criminal population. Today's criminal population is now computer literate and have discovered how much money is to be made in taking advantage of Window's vulnerabilities. The iloveyou virus was both brilliant and retarded. It was brilliant in that it could replicate itself in so many ways and so quickly, which is what caused all of the destruction. Most of the damage was not from what the code does to your machine itself, it's what it does to a mail server when it becomes overloaded. To date it is still the most destructive (in terms of money lost by companies) virus ever written. But there was one little piece of code in there that people don't really hear much about. It had the ability to search for credit card numbers and dial-up internet account numbers/usernames/passwords and save them to a remote server. Unfortunately, the brilliance of its replication was why it was also retarded. The thing spread so fast, that within hours, everyone knew it was out there and authorities had already located the remote server it was logging this information to and shut it down. If it hadn't been so destructive, the writer could have made a lot of money selling all of that information. However, not only did he not collect any sellable information, he got caught. If the guy had designed the virus to be very discreet and slowly replicate itself. Users would be infiltrated and their information would be stolen without the user every knowing it.

      Today we don't see as many of those super destructive e-mail viruses because they are pointless. You can't make any money with them because they are like walking into a bank with a black mask and a gun during normal business hours. Everyone knows you're there and what you're up to. Good luck making it out of the building with a sack of cash, cause the cops already have the place surrounded. Now if you were to exploit a hole in that banks security and sneak in and out undetected, now you're talking. Even better, use "zombie" employees to do your dirty work for you. And that's what we see today. Huge botnets full of zombie computers, whose users are completely unaware. All were infected by security holes in Windows XP (yep SP1 and 2). These guys aren't hackers, they're crackers. They make a profit (illegally) by hacking. The reason they make a profit, is because you don't know they were ever there.
      --
      "It's not whether you win or lose, it's how drunk you get." -- H. J. Simpson
  22. Not a laughing stock? by boudie2 · · Score: 0

    I think they'll be a laughing stock until they find a way to make all those funny videos of Steve Ballmer go away. Jeez, that guy cracks me up!

  23. Mod parent insightful! by Spy+der+Mann · · Score: 1

    I had asked Microsoft's Security VP, Mike Nash, about the problem of infected pirated machines. And what did he say?

    "It's hard for me to feel too bad for the person who you know who doesn't have a licensed copy of Windows and is infected. They are using stolen software."

    In other words, we ALL are suffering spam, viruses and worms because Mike Nash got picky about not providing security to "stolen software".

    It $hould be clear now that Micro$oft got their prioritie$ $traight. Right?

    1. Re:Mod parent insightful! by geeknado · · Score: 2, Insightful
      I agree with you principally on one point-- this is everybody's problem-- but realistically, how is Microsoft going to support owners of pirated software? Let's assume for a moment that they don't just download a version of the OS that's already rooted by something nasty...By the very nature of the thing, these OSs aren't going to be consuming automated updates and thus maintaining a current patch level.

      There also seems to be a disconnect here-- if pirated Windows machines are presenting a problem that everyone has to face, why do we blast Microsoft for its desire to see these machines taken offline? Moreover, why are we putting "stolen software" in quotes when we're talking about people who're actually willfully using unlicensed software?

      Is the idea here that pirates are "good" because they're not playing the "evil" Microsoft's game? Is Microsoft still more "evil" because they aren't improving the security of machines that are already well out of the bounds of their support model?

    2. Re:Mod parent insightful! by MotorBheaded · · Score: 1

      Why should a company be bothered to provide support not to their clients, but to users who pirated /stole the product? OK, one may argue it's MS themselves who fostered piracy to establish their monopoly...

    3. Re:Mod parent insightful! by tim_mcc · · Score: 0, Redundant

      Moreover, why are we putting "stolen software" in quotes when we're talking about people who're actually willfully using unlicensed software? Copying != Stealing
    4. Re:Mod parent insightful! by i.r.id10t · · Score: 1

      And if they really cared, they'd provide "updates" that break the OS completely... Sure, some honest folks who bought computers from dishonest "local dealers", etc. will get burnt but MS has already said they were willing to fix those people up with valid licenses if they reported who they got the machine/os from...

      --
      Don't blame me, I voted for Kodos
    5. Re:Mod parent insightful! by turbidostato · · Score: 1

      "but realistically, how is Microsoft going to support owners of pirated software?"

      Realistically: do you really think Microsoft gives a damn about "secure" their IP from this point of view? Do you really think Microsoft has done its best to avoid piracy? Do you really think that allowing pirated copies of their software ihas not traditionally been part of their marketing policy in order to "lock in" future corporate users?

      Realistically: Microsoft has allowed a high percentage of their installed base to be pirated. Those pirated boxes cause a hugh mess on the Internet as a whole.

      Realistically: Microsoft is responsible by a big percentage on such a mess and realistically, it has the funds to be held responsible and thus being forced to be a big part of the solution too.

      "if pirated Windows machines are presenting a problem that everyone has to face, why do we blast Microsoft for its desire to see these machines taken offline?"

      Because we know that Microsoft's intent was not to take those machines offline but let them to be online an unprotected just making more of a mess for everybody else.

      "why are we putting "stolen software" in quotes when we're talking about people who're actually willfully using unlicensed software?"

      Because "unlicensed" is a *very* different thing than "stolen".

      "Is the idea here that pirates are "good" because they're not playing the "evil" Microsoft's game? Is Microsoft still more "evil" because they aren't improving the security of machines that are already well out of the bounds of their support model?"

      The idea is that Microsoft used the "first dose for free" on purpouse and that brings a lot of problems for everything else (ie: me? I haven't used Microsoft software for ages, still, my spam folder holds 4111 spam messages right now, and every single one of them can be directly tracked down to Microsoft marketing decisions).

    6. Re:Mod parent insightful! by turbidostato · · Score: 1

      "OK, one may argue it's MS themselves who fostered piracy to establish their monopoly..."

      This is a strong argument, no doubt, but it is not the only one. What about this?

      Due to the fact that lawfully or unlawfully Microsoft OS is almost a monopoly and the network effect involved, by taking offline all that Windows-based malware they are in fact protecting their own clients: the less Windows-focused malware on the Internet, the less malware that can affect their paying customers. It's quite a lot like vaccination policies: even if you are rich and can pay for your own high quality health services it's in your very own benefit vaccinate the unwashed masses; it makes you much less exposed to dangerous diseases (much better not being exposed to cholera than having a expensive treatment to cure it once you are ill, even if you belong to the lucky ones that can pay for it). If the Rockefeller's and Rothchild's of this world were able to understand it, I think Microsoft CxOs can understand it too.

  24. Well, I don't know about you... by RobertM1968 · · Score: 1

    ...but I'm still laughing. :-)

  25. *points* by ThreeDeadTrolls · · Score: 2, Funny

    hahahahaahahahahah! *falls over* hahaha haa lmao lol hahahahahahahahahahahahahahahahahaahahahahahaahaha ha... *breath* haha... ha ahhhhhhhh Nope, still works.

    1. Re:*points* by superpulpsicle · · Score: 1

      What still works? The virus? The hole left wide open?

  26. Poor security makes money. by Futurepower(R) · · Score: 4, Informative

    Poor security makes money for Microsoft because Corrupted PC's Find New Home in the Dumpster.

    1. Re:Poor security makes money. by Stachybotris · · Score: 1

      It's not just poor security - it's a combination of poor security and lazy, uneducated users who would rather trash & replace a system than take the time to fix it. The article you cited made me mad enough the first time I read it, but upon re-read it got worse. A Ph.D. in CompSci couldn't fix his own box? I refuse to believe that he's so busy that he honestly doesn't have the time. I also find it difficult to believe that he doesn't have the skills and habits necessary to keep the system clean in the first place.

      Anyway, MicroSoft isn't making a huge amount of money on those replacements, since they're all shipping with wholesale-priced OEM installs. If they really wanted to make a buck or ten, they'd try to get users to purchase a(nother) retail copy of the software every time a re-install is needed. Perhaps implement something like a one-time key that you must activate either on-line or with a paired one-time key obtained by phoning into Redmond.

      Of course, poor security does make money for other companies. Symantec, McAfee, Panda, Grisoft, ZoneLabs, Spysweeper, and Lavasoft wouldn't have very good bottom lines if Windows were a little harder to exploit. And think of all the new boxen that get purchased because a 1-year-old PC is so cluttered with malware that it BSoDs on a regular occasion.

      Which makes me wonder... How much money could be made by offering to take old PCs from people, refurbishing them (perhaps w/ a quick Linux install), and then distributing/selling them at a low cost? I think this could work, given that I've had customers call in for configuration info for their 'new' PC that is running Win '98...

  27. unchecked buffers by Anonymous Coward · · Score: 0

    Still finding 'em.
    Need I say more?

  28. Source by BloodyIron · · Score: 1

    So, we are supposed to trust a group INSIDE Microsoft, who comment on Microsoft products?

    Sorry, tits or GTFO.

  29. Consider the Source by LifesABeach · · Score: 1

    Microsoft Security in its software has never been funny to its victims. From my perspective; Scott Charney's observations are like observing a battered wife rationalize the need to live using wires, and tubes.

    1. Re:Consider the Source by shking · · Score: 1

      From my perspective; Scott Charney's observations are like observing a battered wife rationalize the need to live using wires, and tubes

      ...but we need TUBES! We all know that the INTER-WEBS are built with TUBES!

      --
      -- "At Microsoft, quality is job 1.1" -- PC Magazine, Nov. 1994
    2. Re:Consider the Source by LifesABeach · · Score: 1

      Good One! Now how we work the angle about the Wires?

  30. Never had a problem myself... by Bullfish · · Score: 1

    I have to say I have used many OS's and really have never had a security problem with any of them. That includes Windows in most iterations. Most of the security stories I have heard have been from other people on the net. The odd time I have attended to a friend or relative's machine, it has almost always been because of something they themselves have done. I still maintain that the main source of computer (including security) problems is with the users themselves. Not saying the others are liars but if the expectation is that you can protect users from themselves, then that is an unrealistic expectation.

    1. Re:Never had a problem myself... by psbrogna · · Score: 1
      MANY people do have problems with Windows security. Here's a summary of my personal experience.

      Work: I've been responsible for a small (75 users) heterogeneous (Win & Posix) server & desktop infrastructure for 10 years. I observe all the best practices regarding securing boxes (firewalls, o/s specific tightening, anti malware & anti virus, etc). In this time frame I've had two incidents of Posix boxes getting hit and ten instances on Windows boxes (viruses). In the case of the Posix boxes the incident was automatically detected an resolved promptly without any impact. In the case of the Windows boxes the incident frequently went undetected for some time and in most cases until there was an impact and corresponding soft cost to recover from the incident.

      Personal: As many other IT professionals and enthusiasts do, I end up supporting boxes of friends and family. My incident rate for Windows vs. Posix outside of work (being less controlled than my work environment) is MUCH worse for Windows. The last couple of years I've been porting the willing to Ubuntu so that we can go a few years between "house calls" vs. the sometimes more than once a year visit I have to pay them if they run Windows.

  31. Its all marketing and FUD by mlwmohawk · · Score: 1

    Windows is still a disaster, and I think I know why people don't care. It is the "Big target" rational nonsense.

    Microsoft has been successful in seeding in people's minds that "all computers are insecure and the only reason why Windows *LOOKS* so bad is that they are so many of them, and if [apple][linux][foo] were as popular, there would be just as many security holes."

    It is a plausible argument when one is ignorant, as most are, of the basics of security. Unfortunately, the argument is getting traction and letting them off the hook.

    1. Re:Its all marketing and FUD by Mongoose+Disciple · · Score: 1

      The thing is, it's true and it's not.

      Linux is an inherently more secure OS than, say, Windows XP. It makes much smarter choices about what's enabled by default. It doesn't leave a bunch of ports open for no reason.

      It's also true that there's much, much more incentive to try to find a security hole in Windows XP because it's the most popular desktop choice and is thus most likely to have the highest density of ignorant users with credit card information.

      So! The reason that the argument is plausible is that it's true -- it's just not the whole story.

    2. Re:Its all marketing and FUD by mlwmohawk · · Score: 1

      Linux is an inherently more secure OS than, say, Windows XP. It makes much smarter choices about what's enabled by default. It doesn't leave a bunch of ports open for no reason.

      This is, possibly, a reason but not a main one.
      It's also true that there's much, much more incentive to try to find a security hole in Windows XP because it's the most popular desktop choice and is thus most likely to have the highest density of ignorant users with credit card information.

      So, you have fallen hook, line, and sinker into Microsofts disinformation campaign.

      It never has, and never will, have anything to do with popularity or "incentive." That is a red herring put out there. The *real* incentive for crackers is to crack the "uncrackable." Windows is so easy, even script kiddies can do it.

      Slashdot is not a good place for this debate because it is a complex issue that has to do with well researched facts and has nothing to do with "conventional wisdom" which is bought and paid for by advertising dollars.

    3. Re:Its all marketing and FUD by db32 · · Score: 1

      So I suppose you are telling me that the market penetration has nothing to do with them being a juicy target? Ok...sure... Lets you and I go wrangle up some botnets, you only get to target BSD and I only get to target Windows and then we will DDoS eachother until someone loses all their bots. To make it fair lets go ahead and assume you have root logins on all the BSD boxes so you don't even have to exploit them, so now you can't make argument that its hard for you because BSD is more secure.

      Windows is indeed defective by design, but a massive botnet of linux/solaris/bsd whatevers would be pretty damned worthless in comparison. In the meantime the monstrosity that Storm has become could DDoS most of them out of existance while still sending millions of make my penis bigger spams a day, and still have enough left over to extort money from pay sites and small countries by threatening attacks.

      The argument that the only reason Windows suffers more because of their domination is flawed. But fools like you saying the market penetration has nothing to do with it just make that argument look stupid. By the way, I have my own InsecureOS that I'm writing, would you care to tell me why there are no exploits in the wild for it?

      --
      The only change I can believe in is what I find in my couch cushions.
    4. Re:Its all marketing and FUD by mlwmohawk · · Score: 1

      Your response is a prime example of why security is such a joke. Where to begin?

      Your little home "insecure" OS is not a proper analogy as Linux, FreeBSD, and Macintosh are not obscure or unknown. Thus security through obscurity does not apply.

      The fact that Windows is a "big" target has NOTHING to do with vulnerability. Nothing. Vulnerability and security measures are technical issues which apply to everything from ATMs to servers. Trying to link a technical deficiency to an apparent popularity is a logical fallacy.

      If you do a proper break down of the attacks against Windows, and eliminate those which would not work against Linux or Mac, then you can have a proper understanding of the relative security of the systems.

      Any defense of the "Big Target" argument falls directly into the hands Microsoft marketbots.

    5. Re:Its all marketing and FUD by db32 · · Score: 1

      Your response is a prime example that you have no concept of what security is. 1. Linux and FreeBSD are absolutely obscure. They just aren't obscure to the people you know who know about them. The average owner of a zombied machine has no idea what any of those words are. Also Macintosh is not an OS.

      2. You are at least marginally right here. Windows being a big target does have nothing to do with its Vulnerability. Linking technical deficiency to popularity IS a logical fallacy. Unfortunately if you have a clue and work in security you would know that Vulnerability is only one part of the equation. Threat (the number of people wanting to exploit) and Capability (their ability to successfully exploit) are the other parts. The overlap between Threat, Vulnerability, and Capability is what determines Security Risk. Windows has a high vulnerability, a high number of threats (everyone wants a piece), and the threats have the capabilities to inflict damage (every skript kidde out there can do it)...huge security risk. Linux/BSD/OSX have lower vulnerabilties (better design), lower number of threats (not a high value target), and lower capabilities (takes more expertise than your average WinSkriptKid to haxor this gibson). My InsecureOS has a high vulnerability, virtual 0 threat (noone knows about it or cares), and virtually 0 capability (even if you did care you have no idea where to begin exploiting). My InsecureOS is a lower risk factor than even Linux/BSD/OSX. 3. Any denial of the "Big Target" argument falls directly into the hands of people who don't understand security and should never work in the security field. They are just $OS_of_choice zealots that can't see past their own upturned nose to understand the reality of things.

      --
      The only change I can believe in is what I find in my couch cushions.
    6. Re:Its all marketing and FUD by mlwmohawk · · Score: 1

      Your response is a prime example that you have no concept of what security is. 1. Linux and FreeBSD are absolutely obscure. They just aren't obscure to the people you know who know about them. The average owner of a zombied machine has no idea what any of those words are. Also Macintosh is not an OS.

      First: Linux and FreeBSD are not "obscure" they may be "arcane" but they are not obscure, there isn't a single competent IT professional that does not know of the existence of Linux, FreeBSD, or Macintosh.

      Second: Using "Macintosh" as a canonical term for a computer running OS/X is a reasonable and unambiguous short hand.

      Third: We have not been addressing risk in this conversation nor have we been addressing impact, we have been addressing "security," which, by the way, if done correctly mitigates the risks and impact of a popular platform.

    7. Re:Its all marketing and FUD by Mongoose+Disciple · · Score: 1

      It never has, and never will, have anything to do with popularity or "incentive." That is a red herring put out there. The *real* incentive for crackers is to crack the "uncrackable."

      Realllly. So if I decide I want to steal someone's credit card numbers, I'm going to try to crack a Linux box with a much higher probability of belonging to someone who actually knows something about security instead of a Windows box just because it's harder, and that's all I care about.

      I'm sorry, but that makes no sense at all.

      There surely are crackers who are after the "uncrackable", either for prestige or personal challenge. I won't deny that. Those guys possibly are out there looking for exploits in Linux, and they're going to have a hard time because, as I said, it is harder. There equally are crackers who are trying to actually accomplish something with their cracking, be it assemble an army of zombie machines for some other purpose, steal information, or write a virus that gains a lot of notoriety. Those guys, almost without exception, are going after Windows machines. Some of these guys are your aforementioned script kiddies -- they're looking for easy, yes, and Windows is it, but they're also looking to accomplish something to make themselves feel like big men.

      Computers are binary. The world and people generally aren't. It's possible for more than one reason to contribute to a problem, and that's the case here.

    8. Re:Its all marketing and FUD by db32 · · Score: 1

      First: We aren't talking about competent IT professionals. If everyone was a competent IT professional there wouldn't be such a huge problem with any OS shipping with stupid settings. We are talking about the reality that the vast majority of infections and security issues happen to NON IT professionals and that is why its such a huge issue. Thses are the people that those OSs are obscure. FYI Obscure is relatively unknown, Arcane is known to the initiated...so in this case they mean the same freaking thing.

      Second: Macintosh as shorthand for OS/X doesn't make sense on the OS level, or the fact that OS/X is about 5 characters less than Macintosh. Macintosh is ambigious because a Mac (shorthand) generally refers to the physical not the software. I have never heard anyone say "I am running Macintosh", but I have heard "I am running OS/X on a Mac"

      Third: Security != Vulnerability. Security is mitigating the effects of the overlap of Vulnerability, Threat, and Capability. The security of a particular system is greatly related to how widespread use it recieves as well as other factors such as technical vulnerabilities and so on. I never said Windows had more technical vulnerabilities because of their large deployment, that would be stupid. But saying that its widespread deployment isn't a huge part of its security problem is just arrogance and ignorance. I suppose next you will tell me because security through obscurity is something that you shouldn't rely on that you should never use security through obscurity in conjunction with other methods. You shouldn't rely on your seatbelt to save you, but you should still wear it because it does add protection on top of airbag, working brakes, paying attention, not being drunk, etc, etc. Security is going to be the sum of things you do, not the absolute value of one thing.

      --
      The only change I can believe in is what I find in my couch cushions.
  32. We're just catching our breath by genner · · Score: 1

    They're still funny. We just needed to catch our breath and rest our aching sides.

  33. You can't declare your own respect by Maxo-Texas · · Score: 1

    In line with microsoft's pronouncement,

    I want to recognize how much respect and admiration everyone at Slashdot now has for all my posts.

    ---

    Cool-- did that change anything? No. The fact is, that compared to the AS/400, microsoft operating systems are festering mounds of viruses that crash without warning at 10 times the rate. Compared to linux, microsoft O/S are boxers with glass jaws.

    Instead of adding all of these new features in Vista (which sucked a ton of performance) they needed to shut down all the buffer overflow exposures (which have been avoided because they cause a 1-3% performance hit).

    When we stop getting major Trojans, worms, email viruses, IM viruses, etc. then microsoft will get the respect they are proclaiming unilaterally they are getting.

    --
    She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
  34. Feh! by r3b00tm0nk3y · · Score: 2, Funny

    All modern operating systems are still struggling to catch up to the Atari 800.
    Even now it sits impenetrable with layer one security from both the Internet and power grid in my closet!

    --
    This sig is alpha and shouldn't be viewed on production machines
  35. Is this a confession ? by unity100 · · Score: 1

    "we were the laughing stock of security" - so it was like that. So then, you were serving faulty, lacking products to customers ?

  36. Windows APIs are inherently insecure. by argent · · Score: 5, Informative

    The biggest problem is, of course, the HTML control.

    Until Microsoft abandons the entire "security zone" model and makes the HTML control default to a secure or "closed" state completely under the management of the calling application Windows security will never be anything but a joke. The recent hole in Yahoo Instant Messenger, for example, is primarily Microsoft's fault... because the "security zones" should not be able to "fail open". Blaming Yahoo for not 'sanitizing' the input is nuts.

    No other HTML rendering library works this way. The two leading alternatives... Mozilla's Gecko and KDE's KHTML (and thus Apple's Webcore)... both implement a closed sandbox. If an application wants the page to have more capability, it must explicitly install hooks to grant it that capability. This way when an application renders a page using Gecko or KHTML there's no possibility of there being prepared holes to attack. In addition, when they DO install a controlled hole in the sandbox, they know that they're the only agency doing so... there's no concerns about some insecure ActiveX control in the system becoming an avenue of attack.

    Until Microsoft completely changes the API for the HTML control they won't solve their image problem, and they shouldn't expect to... because until they do this, they have a problem and the image only reflects that.

    ActiveX use in the HTML control, of course, is completely insane. Given all the layers of bandaids and patches and dialogs and settings and security levels wrapped around them, it's actually less effort to explicitly install a plugin than to open IE up to the point where you can use a "trusted" ActiveX control. They need to deprecate and eventually eliminate this.

    There are other problems, too. Applications have to parse command lines completely, using their own code to break them up into arguments and perform wildcard expansion. Both OS X and Linux use the UNIX "exec" call, which doesn't require the application to add this additional evaluation step. Many of the "URI" related holes found in applications on Windows... including several recent ones involving IE, Firefox, and Second Life... are due to this flaw in Microsoft's APIs.

    There's a second flaw in their URI handlers, and that is the inability to separate internal handlers that may expose more powerful capabilities than a sandboxed object should have access to with the ones that are designed for use by untrusted documents. The 'patch' to fix this is to try and sanitise the list of URI handlers that each application will use. This, like any other "sanitization-based" approach, is inherently flawed. They need to create a second registry that only supposedly secure applications will use... and then they won't need to worry about web pages containing links to ".CHM" files.

    (Apple, by the way, has copied this flaw from Microsoft. But at least they don't share the rest of the burden)

    The lack of a standard mechanism to bind network services to specific interfaces is a third problem. In UNIX most network services have traditionally been run from inetd, so if you replace inetd with something like xinetd or tcp wrappers you can prevent services from listening to anything but the local interface "localhost". This means that a firewall on UNIX is an extra defense, where on Windows it's the only way to keep insecure protocols from accepting connections from external sources.

    For Microsoft to get the same reputation for security that UNIX based systems have earned, it will have to correct these flaws. The easiest way, perhaps, would be for it to BECOME a UNIX-based system. It wouldn't take much, so much of the API is already inherited from Microsoft's one-time infatuation with UNIX, and they ship a subset of teh UNIX API with Windows in the POSIX subsystem.

    Or, though it would be less desirable from the point of view of people who have to write portable code, they could implement their own secure APIs and make the existing ones a deprecated and eventually optional add-in.

    But so long as they keep the current API unchanged in all details, though, they can not solve these problems they're faced with.

    1. Re:Windows APIs are inherently insecure. by rs79 · · Score: 1

      Good point.

      Of course this all started when Misrosoft decided HTML in email was a good idea. This was around the time Netscape was hot shit and t othe average user it seemed like a cool idea "ooooh, red text".

      Which if course is the moral equivalent of a crow going "oh, a shiny thing".

      Bad juju.

      --
      Need Mercedes parts ?
    2. Re:Windows APIs are inherently insecure. by I'm+Don+Giovanni · · Score: 1

      "The easiest way, perhaps, would be for it to BECOME a UNIX-based system. "

      Yes, because EVERY widely-used OS must be a Unix variant, after all, Unix is the be-all and end-all of OSes, designed by God himself.

      Do you really want every OS to be a unix?
      BTW, did you notice that NONE of the problems you talked about have anything at all to do with whether an OS is built on top of Unix or NT or whatever? So why even believe anything else in your post?

      --
      -- "I never gave these stories much credence." - HAL 9000
    3. Re:Windows APIs are inherently insecure. by drspliff · · Score: 1

      Yes, because EVERY widely-used OS must be a Unix variant, after all, Unix is the be-all and end-all of OSes, designed by God himself.

      Absolutely correct.

      Don't you know the 10 commandments?

      1. I am /unix, thine operating system, which have brought thee forth out of thy bondage to machine code, out of the days of the front panel; thou shalt run no other operating system above me, beneath me, or beside me.
      2. Thou shalt not make unto thee any graven core image in binary, nor in octal, nor in hexadecimal; thou shalt not bow down thyself to them, nor program in them, for my kernel is a jealous kernel, visiting the core dumps of the parent process upon the third and fourth gener- ations of them that defile my system calls, but shew- ing mercy unto thousands of them who love lint and read my man pages.
      3. Thou shalt not take the name of superuser in vain: for /unix will not hold him guiltless that invoketh super- user's name in vain.
      4. Remember the sabbath day, to keep me wholly archived. Six days shalt thou edit, and do all thy compiles; but the seventh day is the sabbath of the system admini- strator, who shall earn time and a half therefor: In it, thou shalt suspend all user processes, and create my weekly tar dumps.
      5. Honor thy parent process and thy process group, that thy connect time may be prolonged, and that thine exit status may be zero.
      6. Thou shalt not kill init.
      7. Thou shalt not adulterate my system files.
      8. Thou shalt not steal any material proprietary to, or under license or sublicense by, or protected by copy- right or trademark of, Unix System Laboratories or the vendor of thine implementation.
      9. Thou shalt not bear false witness on thy local host by running setuid programs across the network.
      10. Thou shalt not covet thy neighbors workstation, thou shalt not covet thy neighbors doc set, nor his uid, nor his gid, nor any hardware nor software that is thy neighbors.
    4. Re:Windows APIs are inherently insecure. by argent · · Score: 1

      Yes, because EVERY widely-used OS must be a Unix variant

      I didn't say "best", I said "easiest". As I noted, they already have the code implemented and working in NT, in the POSIX subsystem.

      Also, "becoming a UNIX based system" doesn't mean becoming a UNIX variant. There's nothing fundamentally wrong with the NT kernel on the desktop and (again) as I noted they have the code, they could expose as much or as little of it as they needed.

      In addition, I didn't say "must". The very next paragraph presented the alternative of creating a new API that avoided the problems of the current ones but still worked for traditional command line programs, and deprecating the use of the current API for launching programs. While it would be best for people who write portable code if this was based on the UNIX "exec" call, that's certainly not a requirement.

      did you notice that NONE of the problems you talked about have anything at all to do with whether an OS is built on top of Unix or NT or whatever?

      Actually they do.

      First, when launching a command line program under Windows the parameters are parsed into options and file names by the called program, not the calling program. In UNIX, this operation is performed by the calling program, so it can unambiguously pass strings containing quotes and other metacharacters to the called program without having to guess how they will be broken up into words. There have been a steady stream of exploits that take advantage of this design flaw.

      Secondly, program in UNIX universally inherit a lot of context from the parent, including open file descriptors. This allows a network superserver (like inetd on UNIX) to manage the connections for network services without having to have each application independently provide their own API and configuration tools to control the ports they listen to. This is not part of the NT API... first, because open files and sockets are not the same kinds of objects, and second, because the process hierarchy in NT is convention rather than something built in to the system.

      Both of these problems would be solved by deprecating CMD.EXE and the old DOS-derived Windows command line API, and the split between sockets and files that's the heritage of the old Lachman Winsock library, and going to a UNIX API for files and processes. Obviously there are other ways to do the same thing, but unless Microsoft actually implements one and takes steps to convert everything over to one that's kind of academic.

      Now this isn't the same thing as having the OS "built on top of UNIX", but that's not what I said. There are many UNIX-based operating systems that are built on quite different kernels and with quite different underlying designs... some which are proud of their membership UNIX family while clearly being a different kind of OS, like QNX and BeOS, and others that keep their UNIX roots at arms length and the APIs partitioned off in a separate subsystem, like Windows NT. Windows already has an enormous amount of such indirect inheritence from UNIX thanks to Microsoft's aborted plan to merge MS-DOS and Xenix (this started with MS-DOS version 2). Which is precisely WHY this would be "the easiest solution".

      Not the only. Maybe not even the best. But certainly the easiest.

      The third of the main points I brought up - the HTML control - wouldn't automatically be solved by this design, but this comment was addressing the second half of my message (starting with "There are other problems, too.") Obviously the flaws in the HTML control could be cloned in UNIX. Apple has managed to copy one of them, unfortunately, and some have been carried forward into the design of .NET and I'm concerned with the possibility of them resurfacing in Mono and Moonlight.

  37. Bridges not falling down is unrealistic? by Vellmont · · Score: 3, Insightful

    I love this comment. It's such an interesting insight into the mind of a Microsoft guy:

    Look, that bridge in Minnesota just collapsed. How long have we been building bridges? We know how to build bridges, right? Sometimes people just have unrealistic expectations of what we can do.

    I don't know anyone who thinks a major bridge in major US city in the richest country in the world not collapsing is an "unrealistic expectation". I actually DO agree that having zero security holes in any software as large as Windows (or Linux) is an unrealistic goal. Comparing that to a major bridge disaster that never should have happened is kind of a strange comparison though.

    --
    AccountKiller
  38. Scott Charney, let me say this to your assertion by 1shooter · · Score: 1

    Ha ha.
    Ha ha ha.
    Ha ha ha ha ha ha.
    Ha ha ha ha ha ha ha ha ha ha ha.
    Ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha.

    Nope, you're still the laughing stock.

    --
    6F 9E A9 1E 96 9F 74 27 ED B8 81 6D 0C 4E 1E 78
    My other Sig is a 229.
  39. Who's laughing now? by Anonymous Coward · · Score: 0

    Charney suggests that security in Microsoft products has moved on from being the 'laughing stock' of the IT industry to something more respectable. HAHAHHAHAHA!!!!

    Now *that* was funny!
  40. just ask them by wardk · · Score: 1

    they will tell you.

    "stop laughing, please. We're secure, really, why are you laughing harder, stop that."

    I guess they just need to say it 9 more times for it to stick

    cause saying means more than doing.

  41. Somewhere, I hear... You... Will.. Be... by davidsyes · · Score: 1

    Ass-immo-lated...

    --
    Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
  42. On the offensive again. by Anonymous Coward · · Score: 0

    I'll concede, in the last six years, some improvements were made. They did, it's true.

    So they're trying. Therefore, they are not on the bottom rung anymore. Is this true? Can we think of anyone with a worse reputation?

    They're fighting against "unrealistic expectations". I disagree: Had they applied forethought and design to their devices, they would have had less of a fight, and with them all of their users.

    So, we jaded cynics all immediately noticed the crux here: this is a marketing offensive. "C'mon, we're not all bad".

    This begs th question: Why now? What are they up to?

  43. Heh by gammygator · · Score: 2, Funny

    They aren't a laughing stock because it just isn't funny anymore.

    --

    No Nyarlathotep, No Chaos
    Know Nyarlathotep, Know Chaos
  44. microsoft logic by pdunning · · Score: 1

    M$ are saying they are no longer the laughing stock of security.
    This must mean that M$ admits that they used to be (that's a big jump for them).

    Furthermore why should we believe them as anyone who cares about security (well almost everyone) has jumped ship and uses something else (linux/mac/BSD/solaris/whatever). No one is likely to be tempted back because we know vista already has more holes than other OSes and M$ is now the laughing stiock of DRM.

  45. A larger view of the whole problem (link) by Anonymous Coward · · Score: 0

    A great writeup about the "boiling frog" problem we have. Don't miss the followup article either!

    Security Absurdity: The Complete, Unquestionable,
    And Total Failure of Information Security.

    http://www.securityabsurdity.com/failure.php

  46. haHa HA HA ha! tee-hee! by Anonymous Coward · · Score: 0

    Thank you for brightening my otherwise dreary Friday morning!

    Microsoft not a laughingstock of security... (wipes tears of laughter from eyes)

    And there aren't millions of zombies and botnets pumping out spam and phishing teasers to all us good little Windows users...

  47. The good news by Cro+Magnon · · Score: 4, Funny

    is that MS is no longer a laughingstock. The bad news is, now we're crying instead.

    --
    Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  48. Microsoft by WhiteWolf666 · · Score: 1

    It is not for you to determine when you are, or are not, a laughing stock.

    The subject of a joke does not get to determine whether or not it is funny. ;)

    --
    WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
  49. May we be... by Anonymous Coward · · Score: 0, Insightful

    ...the first to admit then that all other operating systems and vendors have said the same thing time and time again, including yours truly "Linux". Don't get cocky.

    1. Re:May we be... by Penguinisto · · Score: 3, Insightful

      ...the first to admit then that all other operating systems and vendors have said the same thing time and time again, including yours truly "Linux".

      ...except that in Linux, OSX, and *BSD's case, it has been (at various points in time) demonstrably true.

      While I certainly wouldn't say that the three have perfect security (and certainly not WRT dumb admin/user mistakes), I can say with confidence that they can rightfully be claimed as being among the most secure out there. Windows cannot, not has ever been, able to credibly claim that. Whether it can do so in the future remains to be seen.

      /P

      --
      Quo usque tandem abutere, Nimbus, patientia nostra?
    2. Re:May we be... by jnf · · Score: 1, Interesting

      Putting aside that you put OSX into that list (which is at least 5 years behind the security curve), Vista is honestly on par with a hardened linux (i.e. grsec/pax/etc) and openbsd. Over the past few years MS has actually made huge leaps towards better security, and the security of Vista shows it. You state that the whether the security of windows is yet to be seen, but you neglect that Vista has been out for about a year now, without a single critical flaw found to date, nor a single reliably exploitable heap overflow, and so on. Really, anyone who refuses to see the about-face that ms has taken is guilty of just being blindly zealoted.

    3. Re:May we be... by mrseth · · Score: 2, Interesting

      Maybe I am confused, but how do you explain this?

    4. Re:May we be... by kesuki · · Score: 1

      Security on opensource and non ms oses isnt what makes them great, its the tools for detecting and fixing machines...

      hardly a month goes by without my isps DNS server manages to get hacked long enough for it to try to access known vulnerabilities on certain ports (not probing for, trying to connect and upload vulnerabilities, my firewall only logs the connection attempts)

      but the problem never lasts for more than a few hours before my isp has managed to get their servers unhacked. windows is still a bear to get unhacked without elaborate third party software. so, really its the turnaround time from detection to cleaning the system that really matters.

      reminds me of when i ran a webserver and 50% of my traffic was exploited windows machines trying to exploit my server...

      and i have had opensource pcs compromized, usually because i was running optional software that i really didnt need... but ive had far more windows machines that ive had to deal with virus and trojan removal than open source problems...

  50. Ha! Microsoft's Internal Security by c0d3r · · Score: 1

    I was once inside of Microsoft and called for tech support 2 times. Both times i was directed to a support person in india on the other side of the world from hp. The asked me to do an application sharing session with netmeeting and both times ASKED ME TO CHECK AUTOMATICALLY ACCEPT REMOTE CONNECTIONS. I can't imagine how many people actually did this, but i refused. HAS MICROSOFT'S SECURITY BEEN REDUCED TO ONE CHECKBOX?

  51. Fewer logical fallacies, please. by mattgreen · · Score: 0, Troll

    All I see is hand-waving "I bet there are tons of unpatched holes in IIS" sentiments in your post. I'd like to see proof that there exist unpatched IIS holes, not vacuous appeals to emotion.

    You're perfectly aware if you'd said the same thing about Apache you'd be flamed to hell and back around here. I'm just keeping you intellectually honest.

    1. Re:Fewer logical fallacies, please. by Nevyn · · Score: 1

      You're perfectly aware if you'd said the same thing about Apache you'd be flamed to hell and back around here. I'm just keeping you intellectually honest.

      Apache-httpd is not known to have ever done this, MS have done "silent fixes". It would be significantly hard for Apache-httpd to do this, given that they have an open SCM ... all you get for MS are binary diffs. on released blobs. MS also have a much worse reputation for down playing known vulnerabilities, again Apache-httpd has never said "this can't be exploited" unless it can't ... I think they've said no known exploit once or twice when one was later found (the weird BSD memmove() bug comes to mind).

      So, yes, you'd be flamed for saying that about Apache-httpd ... but you wouldn't be flamed for saying that about say wu-ftpd, for the same reasons you won't be flamed for saying ti about IIS.

      --
      ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
    2. Re:Fewer logical fallacies, please. by asuffield · · Score: 1

      All I see is hand-waving "I bet there are tons of unpatched holes in IIS" sentiments in your post. I'd like to see proof that there exist unpatched IIS holes, not vacuous appeals to emotion.


      The only fallacy here is your straw man. The claim you quote is something that you made up yourself. It is clearly very deliberately not present in the original post.

      I'll spell it out, for the hard of thinking: saying that "Your evidence is flawed and can equally explain the opposite conclusion" (my post) is not the same thing as saying "The opposite conclusion is true" (your misquote).
    3. Re:Fewer logical fallacies, please. by mattgreen · · Score: 1

      Er, pulling out the "everything is relative" card doesn't really add anything to the discussion, now does it?

      Allow me to reiterate: I asked for concrete evidence that there exist serious flaws in IIS 6. If there are, I shall kindly shut up and contribute no further. Show me the proof I demand. Surely if it is as terrible as everyone is implying it is, you can provide this sort of proof, right? Leave the hand-waving and faith-based arguments at the door. They have no place in a discussion of computer security.

    4. Re:Fewer logical fallacies, please. by Anonymous Coward · · Score: 0

      I asked for concrete evidence that there exist serious flaws in IIS 6. If there are, I shall kindly shut up and contribute no further. Show me the proof I demand. Surely if it is as terrible as everyone is implying it is, you can provide this sort of proof, right?


      Nobody in the past few posts has made the claim that there exist serious flaws in IIS 6. You are trolling.
  52. They left the port open. by khasim · · Score: 3, Insightful

    Slammer was embarassing, but that one was hardly Microsoft's fault (although they do share some blame). They had released a patch for that vulnerability six months before the attack occurred.

    Yes, they had.

    But the problem was that that port was left OPEN on machines that DID NOT NEED IT OPEN.

    With security, you CANNOT rely upon the end user to keep current on patches. Your system HAS to be able to defend itself WITHOUT those patches.

    And the simple way to do that is to not have ANY open ports by default.

    Security isn't just something you can pin on the software vendor and expect them to solve all your problems. It takes good system admins to keep the systems up-to-date with security patches and have them on a network that is designed for security.

    Security is a process. You are arguing about the high end, theoretical levels ... meanwhile Microsoft systems are still at the very lowest end and every day more zombies are added.
    1. Re:They left the port open. by Anonymous Coward · · Score: 0

      You're right, security is a process. SDL is a process. And the patch that fixed this vulnerability - SQL 2000 SP3 - was also the first application of the SDL process. And since that release there hasn't been a single security bug in SQL 2000. That's, what, three or four years of zero security bugs? Sounds like the process worked.

    2. Re:They left the port open. by dave562 · · Score: 2, Insightful
      With security, you CANNOT rely upon the end user to keep current on patches. Your system HAS to be able to defend itself WITHOUT those patches.

      You bring up two things there. One, you can't rely on the end user to stay current with their patches. Microsoft went ahead and setup Automatic Updates. Therefore the end user doesn't really have to think about it. The box will reboot itself automatically once a month to install the latest patches.

      Your second point about a box being able to defend itself without patches is unrealistic. Software is constantly evolving. Nobody ever gets it right the first time. To make a car analogy here, you're pretty much saying that if Microsoft were an automotive company, they should sell cars that automatically change their own oil, but even if they don't automatically change the oil, the oil should never need to be changed in the first place. A properly designed machine should never need any maintenance, right?

    3. Re:They left the port open. by jedidiah · · Score: 1

      That attitude simply isn't acceptable for production enterprise software. It works for GAMES but not much else. Something that needs to be certified for use and then have all of it's changes approved and validated is not the sort of application where you can use the "we will just patch it after it ships" game company development mentality.

      It may take more than 6 months to properly test a patch and pass it through all the usual stages of release level promotion before you're finally ready to try and schedule a service outtage to apply the change.

      It's far far better to simply avoid doing really boneheaded things to begin with.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:They left the port open. by dave562 · · Score: 1
      It's far far better to simply avoid doing really boneheaded things to begin with.

      I agree. I think a famous person once said something along the lines of, "Show me a person who has never made a mistake and I will show you a person who has never done anything."

      I think Microsoft is kind of like Iran at this point. No matter how much they comply and how much they change, they are still going to get bombed. Yet like another poster pointed out in this discussion, if you put an unpatched Linux install from 1997 on the net, it is going to get owned just as fast an unpatched Win2000 machine. Software evolves. The real question here is whether or not Microsoft is serious about making their products as secure as possible going forward. Given the strides they've made in the last two years, I think it can be argued that they are starting to get it. Now, do they get it to the point that they are going to completely rewrite entire portions of their architecture... probably not, doing so would be almost unrealistic from a business point of view. Odds are that they are just going to add more spaghetti code to patch and augment the current mess of spaghetti code.

    5. Re:They left the port open. by Anonymous Coward · · Score: 0

      Microsoft is kind of like Iran at this point. No matter how much they comply and how much they change, they are still going to get bombed.

      Ummmm... So having security holes is now the same as working on nuclear projects when you are an oil-soaked country while issuing veiled threats to wipe out another country because of your racism? Crap -- I'm in trouble! I think I've had some security bugs in the past too!

      (But I do see your point and agree with you.)

    6. Re:They left the port open. by masdog · · Score: 1

      Now, do they get it to the point that they are going to completely rewrite entire portions of their architecture... probably not, doing so would be almost unrealistic from a business point of view. Odds are that they are just going to add more spaghetti code to patch and augment the current mess of spaghetti code.
      I'm not sure if they did some of this based on security concerns or if it was to eliminate the FUD of "See, even Microsoft uses Open Source," but they've rewritten their entire TCP/IP stack. I believe they also made significant changes to the Windows Server codebase that was used to build Windows Vista.
    7. Re:They left the port open. by dave562 · · Score: 1
      I'm not sure if they did some of this based on security concerns or if it was to eliminate the FUD of "See, even Microsoft uses Open Source," but they've rewritten their entire TCP/IP stack. I believe they also made significant changes to the Windows Server codebase that was used to build Windows Vista.

      That's good to know. Ever since I stopped consulting and became responsible for a single network, I haven't seen a compromised Windows box in over a year. For the most part, if you follow best practices and use some sort of web filter that prevents your users from accessing the really bad parts of the internet, it's pretty easy to run a clean Microsoft network. I haven't seen a compromised SERVER in years. The only server I've seen compromised in the last five years was an NT 4.0 box, and that only got compromised because the client went ahead and installed a WAP against my recommendation, and then failed to secure it properly.

      I'm not dumb enough to espouse any sort of "Microsoft products are secure by default." nonsense, but on the other hand, I've been using the stuff since DOS 3.3 and will be the first to say that they have gotten way better than they used to be.

    8. Re:They left the port open. by turbidostato · · Score: 1

      "But the problem was that that port was left OPEN on machines that DID NOT NEED IT OPEN."

      Not only that: I administered some NT4.0 boxes back those days and I remember what a nightmare it was aplying any hotfix from Microsoft. They (suppousedly) repaired one thing but it (certainly) broke three others. Under those circumnstances is no wonder quite a lot of boxes were unpatched after so much time. I know mine ones were unpatched for that precise hotfix (I remember in the previous weeks an RPC-related hotfix broke entire networks). Of course, coming from a unix background the Slammer didn't affect us: I already knew what a "listening port" was an why I didn't want an RDBM just listening unfirewalled to the Internet, so after (quite too much) reading about it our Ms SQL server was bound just to the loopback on our NT server on the DMZ (it didn't need anything else since all connections were local) and a freebsd-based firewall was in front of it blocking everything but ports 80 and 443 anyway but that opens another very interesting issue: to what amount can be held "guilty" a company that produces systems that *seem* (just seem) that can be managed by a monkey and even have the guts to marketing themselves as such? ("get the facts: Windows is sooo easy and Windows sysadmins are sooo much cheaper than unix ones... I forgot to mention that's maybe because all those so expensive unix sysadmins know their trade while the cheap Windows sysadmins are just clicketing monkeys, but who cares?") -but then Slammer just rides away and no company goes after Microsoft to bleed their money out of trials.

  53. Assuming true, then good for /., bad for Linux/OSX by WindBourne · · Score: 1

    The reason is that u get the window idiot here who claim that virus etc. attack Windows BECAUSE there are so many, Even with the virus writers saying that they attack windows because of the ease of doing it. But if Windows becomes more secure than Linux and OSX, then they will retarget weaker systems. The good news for /., is that finally we can put to rest that piece of FUD.

    --
    I prefer the "u" in honour as it seems to be missing these days.
  54. It Takes A long Time To Forget by curmudgeon99 · · Score: 1

    Do you remember that guy in 6th grade who farted in all-school assembly? I sure do. That has been a long time. You don't forget it when somebody--a person or an organization--does something really stupid. We won't forget about Microsoft's security screw ups for decades.

    1. Re:It Takes A long Time To Forget by Cro+Magnon · · Score: 1

      Do you remember that guy in 6th grade who farted in all-school assembly? I sure do. That has been a long time. You don't forget it when somebody--a person or an organization--does something really stupid.


      Yeah, I know. :(
      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  55. Users are protected even if they "say yes" by Dude+McDude · · Score: 0
  56. Security through obscurity no longer gold standard by Anonymous Coward · · Score: 0, Insightful

    MS's improvements have followed a progression, just like everything they do. There isn't all that much difference between Windows and any other OS, aside from age. Comparing Windows to BSD is kind of insane, given how old BSD is and how long they have had to find the security holes.

    Now teh Lunix and OSX are another story- their "reputations" for security are based exclusively on spin and obscurity, in a "OMG, look at the other guy!!!" effort to say that, since someone else's product may (or, as in reality, may not) be worse than theirs, that somehow means they are "secure". Teh Lunix and Apple have relied too long on MS-bashing as their method of "improving" their product... but ever since the release of Windows Server 2003, there has been a huge shift. They are now forced to compete on the merits of their software and code... and are being found lacking.

    Rather than improving their products, they engaged in MS bashing. Now that the market has become more security conscious, Apple and Lunix are being hoisted by their own petards.

    It's kind of interesting how computer software is about the only real case where a market-driven system actually works. But the true irony is how the market losers (Apple, Lunix, Open Office and IBM, Mozilla, Real Networks, etc) are the ones driving governments to interfere in that market dynamic. I guess we can just chalk it up to hypocrisy being the only core value of conservatives.

  57. It was our Aspirational Goal..... by hedkandee · · Score: 1

    I'm sure GWB's aspirational goal was to turn Iraq into a secular democracy...

    --
    Up for it.
  58. Yeah.... Ive heard that before...... by Anonymous Coward · · Score: 0

    They have used that excuse many, many times in the past. "Hey, look, we're not that bad. Other OSs have bugs too. Right?" Then they usually proceed to name the other OSs. I think I can make my point with one example/question. If MS security is so great, how come the zombie armies that phishers and spammers use to do their dirty work, are made up of almost exclusively MS machines? Don't give the tired old story about them being the predominant OS either. Don't blame the users either, because the average to low end user has always been MS's target market. In other words, they should have known better.

  59. And they're not being asked to have "zero holes". by argent · · Score: 2, Insightful

    I actually DO agree that having zero security holes in any software as large as Windows (or Linux) is an unrealistic goal.

    That's not what they're being asked for. What they're being asked for is for systematic holes to be eliminated, so they don't have to keep being patched over and over again. I've listed some of the systematic holes in the design that they keep getting bit by in the message I posted just before yours.

    The thing that really bothers me is that people are accepting the argument that holes Microsoft created are not Microsoft's fault. People are blaming applications that didn't sanitize untrusted content before passing it to insecure APIs, rather than blaming Microsoft for not providing a secure API they could use instead.

  60. But they still don't get it. by Eternal+Annoyance · · Score: 1

    They integrate everything in the core operating system. This tends to result in more bugs because it's more difficult to keep the code clear and understandable. This translates into longer and more difficult development cycles, unexpected side effects when implementing or fixing something and bloated packages.

    The end result is that Microsoft needs more and better coders to understand the pile of spaghetti windows must be by now.

  61. Cross platform gaming library? by psbrogna · · Score: 1

    Is that where they've set their bar? "Let's not be the laughing stock?" I can relate to that actually. Given how complex software & it's design process has become it certainly is a realistic goal to get software out the door that just "doesn't suck." However, I'd prefer if my server OS vendor aimed a little higher.

  62. Say Something Enough by Greyfox · · Score: 1
    And people will begin to believe it. That doesn't make it true. Saying Microsoft is no longer a laughingstock in the area of security is like saying heart attacks are no longer a laughingstock in the area of medicine. They're still a problem, but no one is laughing at such a serious problem. Their security issues are gumming up the Internet and causing billions of dollars a year in internet fraud-related cases. No one is laughing about that.

    If we're past the laughing phase then it's only because we're moving to the silent shunning phase.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  63. Security? How about reliability by phorm · · Score: 2, Insightful

    My girlfriend recently called me because the wireless internet connection on her laptop stopped working. After screwing around with it for awhile, updating the drivers, etc, I noticed a small notation on the latest driver that it would only work if the actual firmware on your card was greater than version XX. After updating the firmware, the wireless worked again.

    The apparent cause of the problem? Windows update happily auto-updated the wireless driver, neglecting to check that the firmware was compatible, and neglecting to also offer a firmware update. MS Security might have improved, but I don't think their reliability has. Many big corps tread carefully with update patches for this very reason.

    1. Re:Security? How about reliability by TheThiefMaster · · Score: 1

      Windows Update never updates drivers?

      They're available on the Windows Update site, but they won't install automatically and they're not selected by default on the website either.

    2. Re:Security? How about reliability by phorm · · Score: 1

      Must have been another autoupdate then, but the driver was my first guess. I do know that nothing was changed or installed between the two dates, and that the machine worked happily after I installed the updated driver+firmware.

  64. Offline != unpatched by Spy+der+Mann · · Score: 1

    why do we blast Microsoft for its desire to see these machines taken offline?

    The problem is that Microsoft does NOT desire to see these machines taken offline. If that was the case, they could have set a virus that would disable network connectivity on infected machines, as a "security measure". I would vote for this measure! We'd get rid of thousands of botnets in one pass.

    Instead, They keep these machines ONLINE, unpatched, and vulnerable to botnet infection.

    1. Re:Offline != unpatched by geeknado · · Score: 2, Insightful
      What I'm trying to establish here is just why it's Microsoft's responsibility to deal with these particular machines. Their software is being used without their permission. Moreover, given some of the reaction to WGA and other attempts by Microsoft to exclude pirates from their services, wouldn't we likely be blasting them for being draconian tactics?

      I don't think that Microsoft actually can solve this problem so long as piracy exists. As I'm not actually anti-pirate, I'd suggest that a community response would likely be necessary to resolve this issue on pirated machines...Pirate-spun patches, etc, would be helpful. I don't like the virus idea for the same reasons other benevolent viruses are generally a bad thing...They frequently have unintended consequences.

    2. Re:Offline != unpatched by Spy+der+Mann · · Score: 1

      What I'm trying to establish here is just why it's Microsoft's responsibility to deal with these particular machines.

      Let's assume that the govt bans a certain food-processing machine because it releases a toxic gas into the air, which produces cancer. Unfortunately, they found out after the machine became so popular that it became a necessity for people to live a decent life.

      Now imagine that the company which made that machine recalls all the defective products and replaces them with a safer product - as long as the people with the defective product have a "proof of purchase". If they don't, they'd have to buy the new one for an stratospheric price.

      The problem isn't just for those with the stolen machine, but those who live NEAR those with a stolen machine - they're affected too.

      Shouldn't it be the responsibility of the manufacturer to provide safer replacements FOR FREE, even if the products were stolen in the first place?

    3. Re:Offline != unpatched by geeknado · · Score: 1
      But it's not that simple.

      Taking your analogy, let's say that the food processor had a mechanism that allowed its motor to be refined remotely. A seperate entity copies the food processor, replicating every piece involved, but removes that self-updating functionality...It requires registration with the home office so they know where you are, and obviously you don't want your copied processor phoning home. They put these in the hands of consumers.

      The problem is identified, and the parent company tweaks all the motors still under via its magical remote control, and so those machines no longer produce noxious gases. However, the copied processors still plague the environment.

      How does it logically follow that the manufacturer should resolve the issues with processors that were, in essence, produced by someone else? That's the situation with the pirated copies of a proprietary OS-- you have individuals who have altered it in a manner that allows it to be distributed freely, frequently(and in this case, actually) at the expense of updatability. The OS in question has typically been altered(avoiding WGA, etc). It's unrealistic for a vendor to support a patch level that they did not themselves produce. Actually, many Microsoft service packs and hotfixes are available /even without/ genuine approval via download etc...You just can't use the auto-updating tools, so you'd have to rely on the person utilizing the pirated software to do the updating. This is usually where they fall down.

      I am not a fan of Microsoft. I'm a best-tools developer, and they produce mediocre tools at best, and they've been draconian in the past. This, however, is not an example of them being "evil".

  65. Well, duh... by QuietLagoon · · Score: 1
    What do you think he is going to say? That the security of Microsoft software is poor? Do you really expect a Microsoft employee not to lie?

    Most computer users are so accustomed to Microsoft's products being insecure, that they don't really notice the insecurity any more.

    If Microsoft product security has improved so much, they why do we still have all those Windows zombies spamming us each day?

  66. Say something often enough ... by thePowerOfGrayskull · · Score: 1

    .. and it becomes true. MS has been engaging in this kind of 'talk it up' behavior for years. "Okay, we admit we weren't that secure before.. but NOW, /now/ is a much different story." The sad part is, it works. If they repeat it often enough, loudly enough, and with enough different voices, the people responsible for making purchases will believe it's true. A prime example of this is the Linux v Windows TCO "debate" -- which didn't exist until MS spent millions of dollars to /make/ it exist.

  67. Initially I didn't realise the use of a firewall by Colin+Smith · · Score: 1

    Really. It wasn't until I used Windows and scanned a few machines that I realised just why personal firewalls appeared at all. Didn't occur to me that there would be so much exposed.

    --
    Deleted
  68. Moron hat for me... by tjstork · · Score: 2, Informative

    Here's what it is. The desktop icon for IE's right click brings up IE properties, not, IE the process properties. But, if I do the icon for IE's shortcut on the taskbar, then yeah, I can run as another user. Not too shabby MS.

    --
    This is my sig.
  69. Yeah, 'cause clean code is soooo easy to write. by mosel-saar-ruwer · · Score: 4, Insightful


    You know, the little things, like always remembering your </i>, and never forgetting to preview your work.





    Glass houses.

    Projectile stones.

    Whatever.

    1. Re:Yeah, 'cause clean code is soooo easy to write. by Shotgun · · Score: 1, Insightful

      The difference is that the grandparent post didn't advertise that it was syntacticly perfect and didn't charge you anything.

      I think there's at least a small difference in using monopoly powers to push a product on the open market vs a comment to /.

      --
      Aah, change is good. -- Rafiki
      Yeah, but it ain't easy. -- Simba
    2. Re:Yeah, 'cause clean code is soooo easy to write. by ch-chuck · · Score: 1

      You'll never get first post (or market monopoly) by paying attention to details like that!

      --
      try { do() || do_not(); } catch (JediException err) { yoda(err); }
  70. "These aren't the droids you're looking for." by psbrogna · · Score: 1

    Somebody please explain to Mr. Charney that his Jedi mind tricks may work on the general public but we're not falling for that!

  71. Onions make me cry by Dracos · · Score: 1

    An onion pretty much describes the MS security model. Take a core, wrap some layers around it, then add more annoying layers to protect the existing layers. And not every layer has to be from the same kind of onion.

    Coding practices can only get security so far... MS needs to revamp their security design.

  72. What do they expect ... by PPH · · Score: 1
    ... from the VP of Trustworthy Computing at Microsoft?


    He sort of reminds me of the Black Knight from Monty Python's Holy Grail.

    --
    Have gnu, will travel.
  73. Phone Quality by PackMan97 · · Score: 5, Informative

    It's funny, I grew up with a phone infrastructure where I never experienced a dropped call -- granted, a less complex (wired) achievement, but had "wired" phone service been invented today, I suspect the standard would have been "less dropped calls", too... because maximized profit dominates the industries' collective motivations, not quality products.


    What's really funny is that 20 years ago, wired long distance carriers were waging advertising battles over who had the clearest call. Sprint's "Pin Drop" ads probably set the bar in this respect.

    So, while you take the wired phone service for granted, it hasn't been that long since call quality was a very important part of a consumers purchasing system.

    Go back another 20 years to the '60s and you still had a significant portion of the phone network that was manually switched by human operators.
  74. Surprising.. by do_kev · · Score: 0, Offtopic

    I'm very surprised by this discussion for two reasons.

    First, nobody has seemed to point out that the man raised over $5,000, and thus his loss wasn't quite as bad as the full $7,500.

    Next and much more importantly, though, the man is making an important statement that police officers do not have the right to invent laws. The entire democratic process is based on police officers and judges having to follow laws that have been established by representatives voted for by the people. To bypass this process and allow police officers to do whatever they want because "it's not that much trouble" only opens the door to abusive law officials. He's out $2,500, for something that is at it's root a very worthy case (whether he should have just shown the receipt is a different issue, but I would argue that he is correct, he had no obligation to do so. If we as a society feel that he was obligated to do so, then we as a society should vocalize that we want a law stating this). Why are so many people being so judgemental?

  75. Scotts mom and Internet security .. by rs232 · · Score: 3, Insightful

    "One of the things I talk about often is my mom, because she is 78 and she's found e-mail .. You have to educate consumers not to make mistakes like clicking on attachments from unknown sources and not following links and all of that"

    No, all you have to do is build a Desktop System that can't be compromised by opening an e-mail attachment or clicking on a URL ..

    "more people are like, 'Microsoft got its act together, and others should follow their lead,' technologists say, 'OK, our job is done -- what next?'"

    "What I explain to people is that this isn't actually a technology problem we are solving; it's a crime problem"

    Self serving imaginary made up quotes and a nonsensical opinion expressed. Making it a twenty year felony crime for hacking Windows isn't going to make Windows any more secure ...

    --
    davecb5620@gmail.com
  76. Really by smartin · · Score: 1

    Tell that the the controllers of the botnets, they seem to be laughing.

    --
    The difference between Canada and the USA is that in Canada healthcare is a right and gun ownership is a privilege.
  77. Well... by Xenographic · · Score: 1

    Maybe they think this because we've been doing all the laughing behind their backs?

    Clearly, we need to laugh in their face more often. You know, perhaps we could have a good laugh over the Windows Media Player/IE vulnerabilities that still affect people whose default browser is Firefox?

    Or we could laugh at them over playing the blame game when those URL handler vulnerabilities were found. Mozilla fixed their end of it, I don't remember that Microsoft ever did...

  78. Secure Enough by Anonymous Coward · · Score: 0

    It's naive to think of security in terms of black and white. If you force everything into a false dichotomy of "secure" and "insecure", then nearly everything falls into the realm of "insecure". Maybe some information sealed in an iron ball and dropped into the deepest part of the ocean, *maybe* that's secure, *for now*.

    Security is best reduced to resources: Attacker has X dollars and Y hours, and is free to use any nasty trick in the book. How much of any of your resources do you want to commit to stopping it?

    For example, you could construct a car with bank-vault style locks on it. No car thief is going to try to steal it, because they'll look for easier targets. But, it probably cost you a small fortune to build the car. Most of us weigh the security risk and just buy car insurance and lock the (normal) doors. Is your car "secure" or "insecure"? In an absolute sense, it's insecure. A thief can pop the lock, hot-wire, and drive away. However, if you get beyond the false dichotomy; I leave my car parked on the street every day with locked doors; it's "secure enough".

    So instead of thinking as Microsoft products as "secure" or "insecure", ask yourself, "Are they 'secure enough'?"

    - Are you willing to let a competent linux geek use IE on your computer?
    - Are you willing to let an incompetent family member use IE on your computer?
    - Are you willing to let a child use IE on your computer?
    - In an e-mail from a stranger, are you willing to follow a link from Outlook to open in IE on your computer?
    - If run a server and have experienced a DDoS attack from zombies running Windows; do you feel Microsoft products are 'secure enough'?

    I left Microsoft for Linux a long time ago, because I didn't feel Microsoft was "secure enough". YMMV.

    1. Re:Secure Enough by ^_^x · · Score: 1

      Long ago I found it was secure enough for me to use on my own main PC, provided I was the only user, and it was behind a router. I'd still call them the laughing stock of the security industry though, but with a little tweaking I could lock down anything I needed to.

      Now... I'd say they aren't the worst, but I don't know who is... They're certainly moving up even if slowly, and I wouldn't call them a laughing stock anymore... ...but I would still take every precaution I did before, with the exception of a 24/7 software firewall, which I don't run simply because my router is doing such a good job of filtering, and the last virus/trojan I had was in the 1990s.

  79. Ask yourself about why there are virus scanners by Anonymous Coward · · Score: 0

    I wonder why the IT industry needs virus scanners, firewalls and tools to remove troyans...

  80. When is a goal not a goal? by dpbsmith · · Score: 1

    "It was our aspirational goal that the SDL will get rid of every bug. But let's get realistic for a minute: It's not a realistic goal."

    If you articulate a goal that you don't believe is realistic, and all the people working for you know that you don't believe it's realistic, it can't actually serve to measure or motivate progress and is not a real goal.

    If you can articulate a goal that is measurable, so that you can whether or not it's been met ("get rid of every bug,") but everybody knows it's not the real goal, and the real goal isn't measurable, then there is no goal at all.

    To the extent that I understand what he's saying, he's saying that there was no goal at all. (Or he's not telling us what it was, lest it be obvious that it was not met).

  81. Not laughing? by russotto · · Score: 1

    If people aren't laughing at Microsoft security as much nowadays, it's merely because the joke has grown stale.

    1. Re:Not laughing? by Dunbal · · Score: 1

      Also, exactly how unbiased can you expect the vice president of Microsoft's "Tustworthy Computing" department to be? What ELSE is he going to say?

      Why isn't this story in the "It's funny, laugh" section?

      --
      Seven puppies were harmed during the making of this post.
  82. Re:Initially I didn't realise the use of a firewal by DaedalusHKX · · Score: 1

    You weren't around for the days when port 139 ICMP/Nukes were around?

    Every idiot under the sun used to ask (on IRC no less) Win 95/98 users "what's UR IP, yo."

    Course running under Red Hat 5.2 at the time was a good laugh... hard to have your system rebooted when the service to receive said malformed packet wasn't present in the first place, and neither was the OS vulnerability. (Having spent hours coming up with a good ipchains ruleset helped keep the rest of the gaming rigs actually RUNNING Windows 95/98 safe behind the firewall :)

    --
    " What luck for rulers that men do not think" - Adolf Hitler
  83. Security is realitive? by Anonymous Coward · · Score: 0

    All I can say is that several years ago when I went to Defcon some guy from Microsoft took us all out to dinner and paid for the whole group. How can I sit on my ass now and type something bad about MS when it would be so easy and everyone else here seems to blindy follow the I hate MS crowd anyway.

    If you look at SQL Server there have been no vulnerabilities found in their server software since the slapper incident. All other vendors including/especially Oracle release regular streams of vulnerability after vulnerability. Heck one of my test systems even got rooted because I accidently left an oracle test server running.

    On the Windows VS Linux and MAC ... Its just not a fair comparision. Like it or not darn near everyone runs Windows so as a cracker why would I waste my time looking for problems in Apple or Linux when the return on my investment is soo much more with Windows?

    Apple market uptake and automated discovery tools are starting to chip away at Apples only security advantage... "obscurity".

    MS's security reputation will always be dragged through the mud due to the vast endless oceans of lusers that get tricked into installing all manners of crap on their computers. Linux users know better until the lusers start using linux :) Vistas run the browser in a vm sandbox approach is a real good idea to keep lusers from hurting themselves.

    I don't much care about what happened in the past. What I do care about is the offerings avaliable today and how well they work. People bitching about the past and the fun they had in the dialup erra with windows guest accounts can bitch away I guess but I would rather address reality, today and the future than the past that is over and done with.

    Now its time for me to bitch about all of the wrong directions software vendors are taking to make it appear as if their serious about security when their changes contribute nothing.

    Virus scanning as an answer?
    When you are infected by a virus its already game over/too late. Scanners are nice and useful for lusers that have already been owned but have very little to do with security.

    Firewalls are good?
    Firewalls make people think their safe and this in turn directly promotes complaicancy. They also ignore certain realities such as luser initiated compromise is the rule rather than exception and prevelance/cost of insider sabatage.

    UAC is good right?
    Not really, first and foremost its annoying and secondly while it may protect my operating system it does nothing to protect *my data* accessable by me.. which it seems to me most people care more about than a stupid OS that can be reinstalled at any time.

    Banking sites and anti-phishing countermeasures.
    This crap really needs to end right now along with those secure gif logos that make people think that since they see code words that only they know about or see a keylock that their transactions are somehow more secure. BS!!!!!!!!!!!! The banks cert is the only possible thing preventing active MITM and by steering the typical users attention away from the browsers SSL status window with a bunch of irrelevent crap you are just enhancing the possibility that a typical luser will get burned because these baseless countermeasures looked official.

    Which brings up my last point on my use of 'luser' I don't mean that to sound elitist or make fun of people who don't understand the specifics of a technology. They shouldn't have to!! The point is technology is only good if people know how to use it correctly and like the TSA/Airport situation soo many companies are shifting their focus from the hard useful work and education to CYA so they don't get sued and the *impression* of security that has no roots in reality.

    "Fear leads to Anger. Anger leads to Hate. Hate leads to suffering"
    - Master Yoda

  84. Agree: Things aren't true just because MS says so by KWTm · · Score: 1

    Agree. The fact that Microsoft says something doesn't make it so --but people don't know that.

    Earlier this month, Microsoft said that Google could not have done without them, and now they're saying that Microsoft products are no longer the butt of jokes.

    They can say that just because they are a big company and people listen to them. Whether we choose to believe Microsoft is a different matter.

    I remember wearing my first business suit, complete with starched shirt and necktie, early in my university years. People would take me seriously because I was dressed in business attire, no matter what I said. It was fun! Once I stood at the entrance foyer to the city concert hall with my sloppily dressed friends, and people would come up to me and ask for directions and generally assume that I was not part of that group of friends in T-shirt and jeans. I tell them some ridiculous thing with a straight face (like there were free concert tickets upstairs if they could show a McDonalds hamburger wrapper) and people would believe me. Another time I asked to see a high school friend of mine who was in the middle of some all-day meeting, just to socialize (I knew the event was boring) and they just assumed I was a university teacher.

    The pranks got boring after the first few times, but it made me realize how easily we accord credibility and respect to certain people for reasons that have nothing to do with the content of their message or their position.

    It takes a huge effort to constantly critically evaluate whether to believe something, whether to believe that silver-haired "doctor" on the TV commercials who says your male organ will grow by 50%, or that typical mom-looking woman in the magazine ad (cuddling her baby, no less) who says that XX works on her cold symptoms, or that bespectacled politician who says that illegal immigrants are the cause of failure to curb crime, or your friend at the bar who says, "The Linux kernel is insecure. Trust me --I write web pages for a living." (Yeah, so you know all about the Linux kernel, right?)

    So, we end up picking and choosing what we evaluate critically. When we're alert and fresh, we think critically; but after a long hard day at work, or when you feel like just flaking out with a beer in one hand and the TV remote in the other, we let our guard down. That's when the TV commercials hit us, when the Bill O'Reillys and the Wolf Blitzers insinuate their messages. Similarly, Microsoft gets its message splashed across any media space available, and people will listen. It's we geeks who are best able to peel away the facade, to say, "Hey, Microsoft, [[citation needed!]]"

    For all I care, next week Microsoft can go say that Microsoft has produced the best Linux for PalmPilots since George Washington invented the Internet.

    --
    404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
    [GPG key in journal]
  85. Secunia by Nightspirit · · Score: 1

    Secunia lists only one open vulnerability for Vista, which has to be executed by a local user.
    http://secunia.com/product/13223/?task=advisories

  86. but has it improved? by SgtChaireBourne · · Score: 3, Insightful

    Anyway, I guess it's true that Microsoft has gotten more secure and therefore isn't as much of a security laughing stock.

    Wait a sec. Don't project your own values onto a group that may not share them, nor assume a causal relationship where no data has been shown to indicate one.

    So the claim is that it's no longer a laughing stock in the realm of security. All right then. Let's pretend for a moment that claim is true. The next question is why?

    There are at least two possible answers:

    • the design of the software has been changed (security == design)
    • the public relations and marketing activities have been better at quashing unfavorable press and burying complaints

    We can see from the systems affected by vulnerabilities that the former has not happened, no redesign. Maybe it's the latter, better PR.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
    1. Re:but has it improved? by nine-times · · Score: 1

      Well, also my point was partially that they are kind of still a laughing stock. Vista has a number of security systems redesigned, and they still aren't quite good, but I think they're probably better, or at least closer to being better. Because let's face it, Windows 2000/XP pretty well stinks. It's hard as hell to get a lot of programs running under a non-privileged account. They've at least begun to address that with Vista.

      Sure, there are still vulnerabilities, but it's also true that OSX and Linux have vulnerabilities too. The question is, are Microsoft's products inherently less secure than the competition because of poor security design. The answer is (IMHO) "Yes". But at least they've shown they're trying to address those issues. Not going a spectacular job, but *trying* is better than not trying, and they didn't even try with previous versions of Windows.

      Remember, Windows 95/98/ME didn't really even have permissions in the filesystem-- I'm just trying to point out how much they were ignoring security in the past.

    2. Re:but has it improved? by leenks · · Score: 1

      Because let's face it, Windows 2000/XP pretty well stinks. It's hard as hell to get a lot of programs running under a non-privileged account.

      I'm not trolling, but what software is this? Pretty much everything I can think of I would want to use in my day job as a developer / researcher will work fine as a non-privileged user - albeit on a system with a comprehensive security policy applied.

    3. Re:but has it improved? by drsmithy · · Score: 1

      We can see from the systems affected by vulnerabilities that the former has not happened, no redesign. Maybe it's the latter, better PR.

      The design hasn't been the problem.

    4. Re:but has it improved? by drsmithy · · Score: 1

      Because let's face it, Windows 2000/XP pretty well stinks. It's hard as hell to get a lot of programs running under a non-privileged account. They've at least begun to address that with Vista.

      This is not the fault of Windows, or Microsoft. All Vista has done is put in a lot more shims so that the real culprits - the badly written applications - can be fooled into thinking they're not running in an unprivileged account.

      Sure, there are still vulnerabilities, but it's also true that OSX and Linux have vulnerabilities too. The question is, are Microsoft's products inherently less secure than the competition because of poor security design. The answer is (IMHO) "Yes".

      Why ? What poor design ? What about the security-related design problems in (classic) unix-like OSes ?

      But at least they've shown they're trying to address those issues. Not going a spectacular job, but *trying* is better than not trying, and they didn't even try with previous versions of Windows.

      How did they not try ? Windows NT has a vastly better design (from a security perspective) than OS X, Linux, et al (although in recent times SELinux is better, albeit unfortunately hardly ever used).

      Remember, Windows 95/98/ME didn't really even have permissions in the filesystem-- I'm just trying to point out how much they were ignoring security in the past.

      You are confusing engineering constraints with bad design.

    5. Re:but has it improved? by Anonymous Coward · · Score: 0

      "albeit on a system with a comprehensive security policy applied."

      Or maybe with a comprehensive security policy *un*applied?

      Is your %SYSTEM% dir world writable?

      Is your %TEMP% dir world readable?

  87. Microsoft no longer the laughing stock of IT by mazanoid · · Score: 1

    Sort of has the feel of detergent companies when they started saying "no longer with trisodium phosphate. phosphate free. doesn't clean worth a crap, but new and improved"
    which is great if you're a fish....

    So we laud the microsoft, you are now a level 2 product. welcome to being the "Toilet Paper of IT"

    and secretly, we know the success is from declining penetration of MS products. Norton, Mozilla, and leveraged code buyouts have all helped make possible increases in security for your products =)

    Now if you excuse me, I need to take a dump. Where's my VistaPaper?

  88. Re:Agree: Things aren't true just because MS says by Pogue+Mahone · · Score: 1

    For all I care, next week Microsoft can go say that Microsoft has produced the best Linux for PalmPilots since George Washington invented the Internet.

    What? It isn't true? But only last week someone swore it was so.

    --
    Every bloody emperor has his hand up history's skirt [Peter Hammill/VdGG]
  89. Ha [Accept/Deny] Ha [Accept/Deny] Ha... by flyingfsck · · Score: 1

    Well, the reason being that its hard to laugh in between all the security pop-ups. It breaks the rhythm.

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  90. All that can be said by iamthelinuxguy · · Score: 1

    is.....HA! HA!

  91. Hmm... by Anonymous Coward · · Score: 0

    Microsoft : Phew! we're no longer the laughingstock of security.

    Slashdot-crowd : Right, now you're the asstunnel of security AND resource-hoggage.

  92. So is this why by Master+of+Transhuman · · Score: 1

    their Windows Defender product is no longer in the top spyware detectors, and their AV stuff is near the bottom in detection?

    Is this why "Patch Tuesday" remains?

    Another bunch of fucking LIES from Microsoft.

    Why bother to read anything that comes out of Redmond?

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  93. Moving up. by SnarfQuest · · Score: 1

    They have advanced in their strategy to control all bad security. Moving on from laughing stock, they should soon have complete mastery of the entire laughing lock, stock, and barrel categories.

    --
    Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
  94. Cue Chris Rock: by Glowing+Fish · · Score: 1

    You know the worst thing about *****? They always want some credit for some s*** they're supposed to do... "I've never been in jail!" Whatcha want? A cookie?? You're not supposed to go to jail!"

    When you are the world's leading software company, with billions of dollars to spend on R&D, no longer being a laughing stock isn't something you should be bragging about. Vista took five years, and who knows how much money and programmer errors to make. With that much resources, it should be as close to unbreakable as an Operating System could be.

    Now, there is some reason to believe that the argument that Linux has less malware than Windows is just because it isn't popular enough to be targeted. But there is also, presumably, much less money for paid researchers to go through the Linux code and search for bugs. If the OSDL had a one billion dollar a year budget (which would be pocket change to Redmond), there is no doubt in my mind that Linux security could go from solid to virtually invincible.

    --
    Hopefully I didn't put any [] around my words.
  95. SDL? by Anonymous Coward · · Score: 0

    SDL totally rocks! Cross-platform game development is insanely great! That Sam Lantinga is a fucking genius!

  96. Re: Straight from the MS playbook... by CommandNotFound · · Score: 3, Insightful

    It seems kind of funny to me to hear someone from Microsoft admit that they were a laughingstock, and that they're looking for kudos for not being a laughingstock.

    This is classic Microsoft MO: as soon as a Windows version has been released for a few months, start badmouthing the previous versions. They did the same with XP to 2K/ME, ME to 98, NT4 to NT 3.5, etc.

    Just Vista marketing. Nothing to see here, move along.

  97. Is a down moderation the best you have? Poor job by Anonymous Coward · · Score: 0

    Bwahaha... typical! /. members (the "pro *nix" kind that is) can't come up with any better than a "down mod" instead of a score superior to the one that Windows Server 2003 user had on the multiplatform CIS tool security test.

    (The "pro *nix" crowd here sure 'talks big', but when it comes to actual contests of skill & backing up their b.s.? Well, anyone can see the results here... ZERO, for the /.'ers!)

  98. Backward compatibility by c0d3h4x0r · · Score: 1

    Microsoft can't fix Windows properly (by redesigning all its obviously flawed subsystems and conventions) because most people value backward compatibility with existing devices, drivers, and applications over anything else.

    If Microsoft introduced a version of Windows that had been re-written from the ground up in a robust, efficient, sensible way, nobody would buy it (because there wouldn't be any device drivers and applications for it), device manufacturers wouldn't write drivers for it (because the customer base for the OS was so miniscule), and application developers wouldn't port all their software to it (again, because the customer base for the OS was miniscule).

    Look at the modest architectural changes Microsoft took a risk and made with Vista. That broke driver compatibility, and messed with app compatibility in some fringe cases, so now you've got millions of complaints from people bitching that their existing hardware and programs won't work on Vista. It's a major reason that Vista hasn't been well received. Now imagine how Microsoft would have fared if the device and app compatibility had been 100% broken.

    People who claim Microsoft should take the OS X route (new clean OS design, providing backward compatibility by running other OSes in virtual machines) are again forgetting the drivers issue. A new OS architecture cannot generally use drivers from some other OS, and without drivers for your host OS, you're again stuck.

    Microsoft is in a tough position -- damned if they do, damned if they don't. But I just wish they would be transparent and honest about the position they are in. They haven't solved the security issues, and should just admit that they never will be able to as long as they don't control the hardware the way Apple does and customers keep valuing backward compatibility.

    --
    Moderator hint: a comment is neither "Flamebait" nor "Troll" if it is true.
  99. Microsoft is no longer insecure, says Microsoft by IGnatius+T+Foobar · · Score: 1

    Microsoft is no longer insecure, says Microsoft. Yup. It's true because they said it's true.

    I think today I shall declare that I am a seven foot tall baby chicken who can slam dunk a basketball. It's true because I say it's true.

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
  100. Not Yet News by Hercules+Peanut · · Score: 1

    This will be news when someone who isn't employed or funded by MS makes this statement. Until then, it's just more marketing crap that doesn't really belong on /.

    I mean really, this story is almost troll-worthy. What did they expect when they post this up here? "OMG he's right. Now we no longer need *nix to feel secure. The war is over!"
    phbt!

  101. We know the enemy and the enemy is them. by Anonymous Coward · · Score: 0

    I think that you've kind of hit upon the truth. The real security problem with Windows is not the bugs. The problem is that one of the user's main enemies is the operating system producer. DRM is designed to stop the computer owner doing things they might want to do. WGA is designed to force users to register where they might want to keep their privacy. These are just the very well known examples, however; this goes through the whole of everything Microsoft does. The difference between different editions of Vista is that most of them are deliberately crippled to help MS make money by forcing heavy users to pay extra; the reason that ActiveX used to automatically install is to allow MS advantages over existing technologies; as everyone now knows, at the cost of the users security. The reason Java isn't automatically and easily installed on Windows is because MS didn't want it to take over their market; this was a choice which damaged many companies existing investment in Java technology. The cases can go on forever. The difference is that, where before we could call it incompetence, now we know that it actually is a form of malice.

    The point is that security is mostly a matter of tradeoffs; my ability to back up my music against the record companies ability to stop unlicensed copying. Your ability to control the software on your system against Microsoft's ability to automatically change it. Your competitor's ability to find ways to control your computers against your ability to do business. With most companies, the realisation comes that it's more important that customers trust them than that the take every last bit of advantage of their power. I don't think that stage has arrived with MS and I don't see that their operating systems can ever be secure for their users just because that means they will never be secure for MS.

  102. "Get rid of every bug"...??! by grikdog · · Score: 1

    You're kidding, right? Microsoft is notorious for shipping buggy crap that gets fixed (sometimes) on the next iteration, provided you pay for the update. It's been that way since 1986, at least, and MS C V4. If somebody in charge is promising to submit MS stuff to QC with teeth, bravo. The short sharp exhalations are me not holding my breath.

    --
    ``Tension, apprehension & dissension have begun!'' - Duffy Wyg&, in Alfred Bester's _The Demolished Man_
  103. Domain Name Registrar: NameCheap by Futurepower(R) · · Score: 1

    SgtChaireBourne, off topic: You asked to tell you what Domain Name Registrar I chose. I chose NameCheap.

  104. Not suprising really - adult supervision of router by dbIII · · Score: 1

    Not suprising really - the rise of the ADSL modem that is also a NAT router and firewall is putting these windows machines on the net under adult supervision. Antivirus software has also taken on extra roles (and much now consumes incredible amounts of cpu time and memory as a tradeoff). Third place has to go to Microsoft adding in some decent improvements like the firewall and frequent bug patches - the company has a different attitude now than in the past. They managed to turn NT into a home computer operating system good for not much other than playing games but now many of the mistakes are being fixed. I think in a few years we will forget Vista (as with ME) and their updated server version of NT will be sold with a desktop version as well.

  105. r e s p e c t find out what it means from me.... by Anonymous Coward · · Score: 0

    > Microsoft products has moved on from being the 'laughing stock' of the IT industry to something more respectable.

    Yep, today they've moved on to be the laughing stock of just about every other industry too. Respect!

  106. You mean.. by Anonymous Coward · · Score: 0

    by not using vista, it'll be the most secure OS out there?

    too bad everyone beat you to that idea!

  107. Doesn't matter by jlarocco · · Score: 1

    The problem with Windows is the users. As long as people insist on remaining ignorant when it comes to "complicated" computers, whichever OS is most popular will be plagued with malware and viruses.

    If more people on Linux and Max liked reading "eCards" from strangers, their reputations would be just as bad.

    That being said, fuck Windows.

  108. They aren't the laughingstock.. by cyberjock1980 · · Score: 1

    We're the laughingstock for continually buying the OS despite numerous security problems. Let's not talk about the 'secret hidden update' that MS did a few short weeks ago. In the end, Mr. Enduser is the laughingstock for buying the OS knowing damn well all the problems that comes with it.

  109. 2 New Security Holes a Week Called Negligence by Anonymous Coward · · Score: 0

    Interestingly, there was an article over on the Internet Patrol about Windows security just this week in which they point out that if Windows was a car, there would be a forced government recall. With Microsoft announcing an average of two new security flaws a week, and with the huge spread of botnets as a result, the article says

    "If this were any other industry, the government would be mandating recalls - maybe even launching an investigation for criminal negligence.

    In no other industry - in no other time in memory - has a company been able to get away with putting so many unsafe products in the hands of so many people, for such a long time, and with the potential to wreak such widespread havoc."

    Amazingly, half of the comments to that article are sticking up for Windows. The article is at

    http://www.theinternetpatrol.com/microsoft-windows-unsafe-at-any-speed

  110. Is this based on a UK study? by houghi · · Score: 1

    Because there only 2% of the UK companies are able to say that they are still a laughing stock.

    --
    Don't fight for your country, if your country does not fight for you.
  111. CVS logs and remote holes ... by rs232 · · Score: 1

    "Yes. Now look at the CVS logs from between forking the project from NetBSD and the first OpenBSD release, as I said. You will see hundreds of security fixes as a result of that first complete audit"

    Could you do me the favor of finding them ?

    What do the CVS logs from the same time period say of Windows ?

    What correlation is there between CVS logs and number of actual breeches ?

    was: Re:MIcrosoft guy says MS's security is ok?

    --
    davecb5620@gmail.com
  112. Kind of like /. "Pro *NIX" people tell lies, jcr? by Anonymous Coward · · Score: 0

    "Microsoft has been telling bald-faced lies about their security for at least a decade. What's different this time?" - by jcr (53032) on Friday September 21, @11:08AM (#20696607)

    I see you say "Microsoft lies", well... what about you "Pro *NIX" Penguins & "bsd devils" here on slashdot?

    It was hilarious in this thread also where others from the "Pro-*NIX" camp here @ /. tried to say "Apache is more secure than IIS" &, lo and behold in the 2 url's below:

    ----

    APACHE UNPATCHED KNOWN VULNERABILITIES LIST (9%):

    http://secunia.com/product/73/?task=statistics

    IIS 6.x UNPATCHED KNOWN VULNERABILITIES LIST (0%):

    http://secunia.com/product/1438/?task=statistics

    ----

    Let's also move onto & take a look @ SQLServer 2005 also, shall we??

    SQLServer 2005 UNPATCHED KNOWN VULNERABILITIES LIST (0%):

    http://secunia.com/product/6782/

    ----

    Let's NOT stop there either... take a peek @ Microsoft Office 2007!

    Microsoft Office 2007 UNPATCHED KNOWN VULNERABILITY LIST (0%):

    http://secunia.com/product/13228/

    ----

    Given all that data (& yes, IE sux, & IE7 even needs more work in terms of security, but that is what Opera & FireFox are for imo)? It amazes me the b.s. you people here @ /. often spout, like "Windoze blows" etc. when clearly, it is a fine set of products MS produces for the MOST part...

    IE is really the LAST area/product from MS that need some work it seems/is all!

    APK

    P.S. => Also, see this URL where over 30++ /.'ers ran from a challenge regarding Windows vs. Linux security, in a thread post here on /., regarding "Hardening Linux" no less:

    SLASHDOT POST ABOUT "HARDENING LINUX":

    http://it.slashdot.org/comments.pl?sid=267599&threshold=-1&commentsort=0&mode=thread&cid=20203061

    (That's where no *NIX person here on this site @/., & other sites oriented around both LINUX &/or BSD could not do a better job on a valid multi-platform test of security (based on best practices for each OS platform than a Windows Server 2003 user could!))

    The *NIX folks were challenged on this site, who stated things along the lines of:

    "(Insert *NIX variant here) is more secure OR securable than Windows"

    & that's when I simply challenged them to that test in CIS TOOL... not a single one exceeded my score on Windows Server 2003 fully custom hardened for security. See this image which backs my score:

    http://img.techpowerup.org/070828/APK_AToutLeMonde_85.185CISToolScorePhotoProof.jpg

    "CIS TOOL" (by the center for internet security) has been noted as a tool to help secure yourself by BOTH Computerworld & SANS (sites often cited here on /. no less, regarding security data):

    Here is the outline for achieving that 85.185 score on CIS TOOL, for Windows users:

    http://forums.techpowerup.com/showthread.php?p=375355#post375355

    It works & so much so, it tends to "silence the F.U.D." spreaders here on /. about Windows vs. Linux (even SeLinux &/or BSD variants as well) regarding securability of them all!

    Again, for all their 'talk', not a single *NIX person here beat that score, failing to "put up, or shut up". Nobody from /. has exceeded that score a Windows Server 2003 user achieves on i

  113. Better, but not good enough. by Koda · · Score: 1

    When I started at my current job a little over a year ago, I was neutral on the subject of MS security. Read: *not* a zealot. I was originally brought on board as the lead programmer/analyst, but since it's a small company I now wear quite a few hats, including administering several servers. During THIS last year (not 10 years ago, not 5 years ago, but NOW), my opinion of Microsoft Windows as a server OS (whether 2000 or 2003) has completely tanked.

    I'll give you one case in point: one of the Win 2003 servers which was infected by a root kit. It turned out that neither the latest service packs, the monthly "malicious software utility", a strong windows password, nor current Symantec Anti-Virus were enough to keep the root kit out. I had to download and use "Ice Sword" just to deal with the RK. After checking all of the above, I tightened up the firewall. Eventually I found the RK's log files and traced the problem back to Microsoft SQL server. The root kit system had compromised the SA account of SQL server, and was then able to manipulate SQL Server (a mere RDMS, mind you) to install itself on the machine and circumvent the kernel. I couldn't even see the RK using windows explorer; I could only see it with Ice Sword. That is just poor design, and that was with a current patched MS Server product.

    I also found and resolved problems with other Windows servers, and it didn't take long for me to realize that NONE of the *nix servers had any issues. Zip. Zero. Nada.

    So I don't laugh at Microsoft security, but I sure as hell don't trust it. I have concluded that MS has *earned* their horrid security reputation for many YEARS through SEVERAL generations of products (including the current MS Windows 2003). Yet for YEARS they continually touted their improved security. Ever hear of the boy that cried wolf?

    In THIS last year I've also concluded that Solaris and Linux work beautifully, thank you. Not only have they proven themselves more secure, but they're more reliable *and* less expensive to purchase and maintain.