Slashdot Mirror


Microsoft to Clean Up Code

the_pooh_experience writes "Microsoft has decided to beef up their security group by adding a code cleaning group according to Infoworld. As the director of MS security engineering says: 'Microsoft is a long way from its ultimate goal where users can take security for granted in its products...the majority of viruses written attack Microsoft products.'" The new group is called Security Engineering Strategy and while it may seem long overdue to many, it's still a step in the right direction for the folks in Redmond.

466 comments

  1. more of the same by malus · · Score: 3, Insightful

    more of the same lip service from our friends at Redmond. is this the 3rd, or 4th 'security' initiative?

    1. Re:more of the same by DShard · · Score: 5, Insightful

      Lip service or not, these developers have in their job description to be scapegoats. That is not an enviable position.

    2. Re:more of the same by Martigan80 · · Score: 5, Funny

      Actually this was in itself a security leak, the matter is being looked into.

      --
      This SIG pulled due to lack of funding. (This damn war is costing too much!)
    3. Re:more of the same by JayJay.br · · Score: 5, Funny

      Might be the 6th initiative. But don't worry, they're goin to get back to the source, and Zion will be destroyed again.

    4. Re:more of the same by JimDabell · · Score: 1
    5. Re:more of the same by SkArcher · · Score: 1, Flamebait

      Basically, this news story ammounts to 'M$ are doing what they are paid to do and making their software secure'?

      Why is this considered newsworthy?

      On second thoughts...

      --

      An infinite number of monkeys will eventually come up with the complete works of /.
    6. Re:more of the same by muffen · · Score: 1, Insightful

      Even before I read the comments for this article, I knew I would find lots of comments trashing MS.

      MS has always given users what they want, the majority that is (not at the prices they want, but thats a different issue). This is my opinion, and it is based on the number of ppl using MS products.

      Now, a few years back, MS was completetly open about the fact that they priorities functionality. Most ppl know that there is a tradeoff between functionality and security, so this simply means they were not prioritising security.

      They have just started to focus on securtiy, so it will obviously take them a while to fix it. Just because they have a lot of money doesn't mean it will go quicker. You cant throw 100 developers on one project and expect it to go twice as fast as 50 developers.

    7. Re:more of the same by cshark · · Score: 2, Interesting

      I have yet to see anything substantial in this area from this company. In my experience, the only way to fix code that messed up is to do a complete re-write plugging in bits of the origenal where it can. It's a lot of work, but worth it in the end.

      --

      This signature has Super Cow Powers

    8. Re:more of the same by lionchild · · Score: 1

      Hmmm...I wonder if this group of developers will be contrators, or real employees?

      --
      Awk! Pieces of eight. Pieces of eight. Pieces of seven... ERROR: General Protection Fault. [Paroty Error.]
    9. Re:more of the same by nolife · · Score: 2, Insightful

      MS has always given users what they want

      Do you really believe that? I view it as MS always does what THEY want with a PR screen twisting it to appear to be to your advantage. The things they do strictly for the consumer are always an after thought and only implemented when the PR machine can't "fix" the problem, security being a major one. Wouldn't it be nice if IE had half the user controls and advanced features of every other browser made like cookie blocking, web bug identification, ability to block certain scripts. I'm sure the users would like these things. How about allowing Windows update from other browsers. Any reason they could not make a small standalone app to get updates like every other software maker has? Why is the MS Office file format not fully open and documented for compatibility? How about some more specs for SMB transactions? How about getting rid of the constant nagging with passport and Hotmail on XP?
      You may view people that complain or "trash" MS as trolls and winers but there are major issues with the way they do business (monopoly) that causes problems and frustration for computer users and IT folks everywhere.

      --
      Bad boys rape our young girls but Violet gives willingly.
    10. Re:more of the same by Sparkle · · Score: 0

      Just remember M$ Marketing is the best the world has ever known. They could sell ice to an Eskimo. This is just another bullet on their powerpoint foils as they proceed to build the latest-greatest total gotta-have rewrite to extract more of your cash.

    11. Re:more of the same by Anonymous Coward · · Score: 0
      Lip service or not, these developers have in their job description to be scapegoats. That is not an enviable position.


      They may be scapegoats, but I'm not sure that their position is not enviable. They will probably retire 5 years from now on their stock options.

    12. Re:more of the same by molnarcs · · Score: 1

      "MS has always given users what they want..." Like the wonderful Internet Explorer? I used windows for quite some time, and the general feeling among windows users (thanks to the billions spent on advertisement) is that IE is _The Browser_. And since MS wants you to believe (they can't make a speech without mentioning 'innovation' at least 20 times) that their software The Bleeding Edge technology, the majority of its users won't even consider alternatives. They are browsing the net more slowly, more incoveniently than those who use Opera or Mozilla. That's what they want, yes? MS wants to keep users in the dark, and what I have read on mandrakeusers.org, its succeeding. A guy there set up a client in an internet coffee running KDE with an Aqua like interface. He also provided a screenshot - it was quite beautiful. However, some people noticed the blue e on the panel, and asked what its doing there. The answer is simple: the average windows user Joe could not find the Internet (IE=Internet you see?). Giving the customers what they want I guess..

    13. Re:more of the same by Tony-A · · Score: 1

      Whatever. It won't be their last.

      "'Microsoft is a long way from its ultimate goal where users can take security for granted in its products"
      Taking security for granted is how you run into trouble.

      "Security Engineering Strategy" [Emphasis added]
      Better to get your Tactics right before you start daydreaming about Strategy.

    14. Re:more of the same by walt-sjc · · Score: 1

      MS has always given users what they want

      Nice try, but not even close. People have been asking for MS to open their file formats and api's for years. They have yet to comply. People have been asking MS to concentrate on reliability and security since the Windows 1.0 days. 10 years later we are still waiting.

      Most ppl know that there is a tradeoff between functionality and security

      This is just not true either. Most people that know ANYTHING AT ALL about software realize that you can have BOTH. Exactly what functionality is lost when you fix a buffer overflow problem for example? If you look at MS's security patches, they don't remove needed functionality, they fix the security problem.

      MS's priorities are about marketshare and profit. That's IT. The ONLY times that they actually do anything in response to user request is when they perceive a market share loss to a competitor. Case in point: IE sucked blendered toad doo doo until MS decided to capture market share from Netscape. Users are begging for pop-up relief but it is NOT AVAILBALE from Microsoft. They have ZERO incentive to add it as there is no effective competition anymore. In fact, the ONLY changes to IE that we will see now is further departures from W3C standards and more "lock-in" to MS proprietary technology.

      MS has brought this "trashing" upon themselves. As long as they continue to release garbage software (like the latest XP security patch that they had to pull when it trashed peoples machines) they will continue to earn this ire.

      MS has the resources and potential to do the right thing and release good software, they just choose not to. Lip service is the only thing we are getting out of redmond.

    15. Re:more of the same by tomhudson · · Score: 3, Interesting
      and putting it in the hands of a review group, rather than educating their coders (who are, after all, the ones who wrote the bugs in the first place) on how not to write buffer overflows, etc, is the WORST way to go about it.

      So, here's a rather obvious 1-2-3-profit list

      1. patent the buffer overrun
      2. sue microsoft for every infringement
      3. profit!
    16. Re:more of the same by Troll_Kamikaze · · Score: 1

      more of the same lip service from our friends at Redmond. is this the 3rd, or 4th 'security' initiative?

      Oh, but this one's different--they're hiring 3D Realms to implement it.

    17. Re:more of the same by Anonymous Coward · · Score: 2, Insightful

      I see a couple of things to think about here.

      First: Many of the problems with MS software are not code bugs; but bad decisions regarding what you allow code to do. So a cleaning team will not really address the issue of whether or not you allow Outlook to run X or Y.

      Second: If they do clean up their code, it will help to entrench them. XP and 2000 have already sparked comments of "They've come a long way with... or ... is actually pretty stable." This will only further that, which (if you see life in competitive terms) could make the OSS community have to work harder to keep up.

    18. Re:more of the same by muffen · · Score: 1

      People have been asking for MS to open their file formats and api's for years.

      I guess I should have been more careful with my wording, I wrote the post in a hurry (was actually just on my way to a meeting). When I said that they always gave users what they wanted, I was refering to average users, which are the majority of computer-users. Most of them don't even know what an API is.

      Most ppl know that there is a tradeoff between functionality and security

      Again, I should have been more clear in my original post. The tradeoff is, do you create a more secure product, or do you have a more functional product. Buffer overflows (or other "common" exploits) will occur in the beginning for most products, the questions is, how much time do you spend fixing them. Well, if the product functions, and you do not prioritize security, you let the product go knowing it has flaws.

      MS's priorities are about marketshare and profit.

      The company I work for is not close to as big as MS, but trust me, they (and every other medium to large company) prioritize profits and marketshare above anything else. In the end, I chose to work for this company because I get a part of the profit the company makes and, well, I like getting a decent salary with benefits and stockoptions.

      I personally think that IE is crap, and I use MozillaFireBird myself. I use Windows on my desktop, but any server I setup gets to run Linux.
      Why do I not use IE on my desktop or Windows on my servers?
      Well, it simply doesn't have want I want. However, most people choose to use IE, so it must have what they are looking for in a browser.

    19. Re:more of the same by Anonymous Coward · · Score: 0

      I suppose you are also still running win95? ...Windows Server 2003 has been out for a month, and so far nobody has been able to find a security problem with it.

    20. Re:more of the same by acebone · · Score: 2, Interesting

      Most people do not CHOOSE to use IE - it is simply what is available from the get go on their computers with windows pre-installed...

      On win2k you can't even remove outlook express (yeah of course you can - but not by simple means).

      Click the outlook express by mistake once - it won't even ask you - it will just take over as default mail app.

      --
      Check out my PHP Url Validator
    21. Re:more of the same by Anonymous Coward · · Score: 0

      Would it have really mattered what they said? I'm fairly certain that the moment microsoft's name is uttered, you can't wait to say what crap their products are. You know what? Who cares if it's just lip service. Nothing you do is ever going to make a real dent in their bottom line. "Oh, but I use linux, because i'm so damn l33t."

      I don't care what you think, and no one else here does either. Long live the architect.

    22. Re:more of the same by Opie812 · · Score: 1

      Microsoft *does* give people what they want. You think they don't because the people you are talking about are different than the people Microsoft are talking about. For instance, my sister uses Windows and is happy with what Microsoft has provided. She doesn't care about file formats, or api's. Microsoft has given her what she wants. She can turn the computer on and go. Microsoft has aimed at satisfying people like her, not people like you (me, developers, competitors, etc...)

      People have been asking MS to concentrate on reliability and security since the Windows 1.0 days
      Is this true? In the days of Windows 1.0 virtually the only type of security breach was a physical one. You had to be at the machine to do anything malicious. From that perspective security was basically a non-issue. That is why they've been burned so badly once networks became ubiquitous. Their development philosophy could not incorporate the new levels of security required for networked computers.

      MS's priorities are about marketshare and profit.
      Like every other corporation on the planet. Any corporation that says otherwise thinks they can increase their market share and profit by saying how different they are from everybody else. Corporations are not altruistic regardless of how much they say they may be.

      --
      I'm not a nerd. Nerds are smart.
    23. Re:more of the same by Anonymous Coward · · Score: 0

      Who the hell moderated this up? It's not even true, let alone interesting.

    24. Re:more of the same by DShard · · Score: 1

      Seeing as OSS is simply beating the pants of them when it comes to ACTUAL and PERCIEVED security and bug resolution, I think that no matter how good there effort MS puts forth, the OSS community could do a LOT less and still beat them senseless.

      OSS is not a competitor like ANY software company has ever seen. You have a mix of hobbyist and corporate producers all interested in the best common experience. The only common interest in Windows CORE developement is strictly in microsoft's org. That is how they make their money and that is why they will (future tense) not be able to compete.

      Adding an elegance team will not make their lack of resources any different. They simply cannot compete vs the world.

    25. Re:more of the same by AME · · Score: 1

      Wait.

      --
      "I have a good idea why it's hard to verify programs. They're usually wrong." --Manuel Blum, FOCS 94
    26. Re:more of the same by Anonymous Coward · · Score: 0

      "more of the same lip service from our friends at Redmond. is this the 3rd, or 4th 'security' initiative?"

      Some of you just wouldn't be completely satisfied with Microsoft unless Bill Gates contacted you personally with the invitation to line up and assrape each of their executives, eh?

    27. Re:more of the same by wallsg · · Score: 1

      is this the 3rd, or 4th 'security' initiative?

      Since versions 1 and 2 of all Microsoft products are crap and version 3 is the one that takes over, maybe it'll really happen this time...

  2. Poppycock. by Anonymous Coward · · Score: 2, Insightful

    This "emphasis on security" crap is just a PR screen for TCPA^WPalladium^WNext Generation Secure Computing Base.

    1. Re:Poppycock. by Anonymous Coward · · Score: 5, Funny

      TCPA^WPalladium^WNext Generation Secure Computing Base.

      vi commands are not known by your browser. Please use backspace.

    2. Re:Poppycock. by rasilon · · Score: 1

      It would appear that vi command are not known by Anonymous Cowards either.

      (^W in Bourne deletes words, in vi you would use :dw )

    3. Re:Poppycock. by Anonymous Coward · · Score: 0

      I do hate being a pendantic asshole, but *IN* vi you would use 'bdw'.

    4. Re:Poppycock. by zoiblot · · Score: 1
      (heading way off topic here)

      For the record, yes, "dw" or whatever variant will "delete word" in vi's command mode. But ctrl-w (or what your terminal (see stty -a) has set for "werase" will work in input mode as well (provided the word in question is involved in the current edit).

      I myself must use a browser that allows me to redefine keystrokes. ctrl-w as "word erase" is so ingrained in my head, I've lost countless hours of postings due to Microsoft's decision that ctrl-w means "close window".

      Now any code cleanup worth its salt would get tid of this default meaning for ctrl-w - or more reasonably, allow you to change it on a system level.

      (did that get us back on topic here?)

  3. Clean Code? by Eowaennor · · Score: 1

    Bleh you know that their 'clean' code will have just as many problems ;)

    1. Re:Clean Code? by superdan2k · · Score: 2, Insightful

      And probably more new ones, too. Let's face it, something, somewhere, is going to be calling the code they're "cleaning" and if it doesn't work right, it's going to break shit. Bigtime.

      --
      blog |
    2. Re:Clean Code? by orionpi · · Score: 1

      Time to clean up all those VMS rements.
      Open sourcefile in notepad, Ctrl+H, Search for: VMS Replace with: NT, Replace All.

  4. This proves it! by jkrise · · Score: 0, Troll

    "Microsoft has decided to _beef_ up their security group by adding a code cleaning group "

    As close to their admitting the code is full of bullshit!

    Warning: Slashdot is dissing Microsft. Watch out for monkeys and Gorillas.

    --
    If you keep throwing chairs, one day you'll break windows....
    1. Re:This proves it! by ackthpt · · Score: 2, Insightful
      "Microsoft has decided to _beef_ up their security group by adding a code cleaning group "

      As close to their admitting the code is full of bullshit!

      Fool me once, shame one you

      Fool me twice, shame on me

      Fool me over and over and I must be the IT selection manager/commitee/group at a fortune 500 firm.

      Anyone remember Douglas Adams' concept of the SEP field generator? It generates a sense that something is Someone Else's Problem and people's natural predisposition to overlook it makes the something invisible. Makes me wonder if that's not built into the code somewhere...

      --

      A feeling of having made the same mistake before: Deja Foobar
    2. Re:This proves it! by bigman2003 · · Score: 2, Insightful

      So what if this amounts to Microsoft saying there is problems with their code. Everyone knows there are problems, so admitting it doesn't hurt them.

      Now they are telling the world they want to clean it up. They have a team on it.

      Corporate buyers want to hear this. They like to know that the dollars they are spending are going into making the product better. Knowing that they software will be better/more secure in the next revision keeps them from making the choice to move to a different platform.

      In business, money talks. They understand the concept that Microsoft NEEDS to do this, to keep making money. It's hard to understand the driving factor that causes people to spend time inproving Linux- in general it isn't dollars.

      That's the marketing portion, and it really does make sense.

      Of course, they will need to deliver the goods too- and Windows users will benefit from that.

      So by announcing to the world that they are working on it- they get a big marketing push. By actually doing the job, their products will get more and more secure. It may take a while, but as long as they are working on it, people will continue to buy.

      Most of the anecdotes on Slashdot have to do with Windows 95, 98 (ME!) and NT. 2000 and XP are not perfect, or even wonderful, but the amount of improvement in stability is amazing. If this trend continues, their efforts will have paid off- and there will be a lot less reason to switch over to a different operating system.

      --
      No reason to lie.
    3. Re:This proves it! by Anonymous Coward · · Score: 0

      And of course it's rated as a 1 because of the bias against Microsoft products. What he is saying makes a lot of sense. Linux has security problems too. So what if Microsoft comes out and admits to their being a problem. And it's true that most viruses are written to attack Windows, but that's because the majority of non-technical people use Windows. If suddenly a huge part of the world began using Linux, there'd be a hell of a lot more viruses written for linux.

    4. Re:This proves it! by zero_offset · · Score: 1
      "Microsoft has decided to _beef_ up their security group by adding a code cleaning group "

      As close to their admitting the code is full of bullshit! I wonder, is it even worth the effort to point out that the quote which has you hopping with glee was merely the interpretation of "the pooh experience" who submitted the /. article?

      --

      Slashdot quality declines as the number of hot grits posts decreases. - Provolt's Law, Apr-09-2005

  5. Fat Chance by OmniVector · · Score: 5, Interesting

    If you've learned anything by now, it's not important that Microsoft fix the majority of their security flaws, but that they imply they will.

    The OSS model of peer review on a large scale is the sole reason for such reliable security.

    Proprietary companies still have an edge. If people programmed according to a planned set of pre/post conditions, and tested their modules with black box testing, then a large portion of the controllable errors can be caught. Whether or not Microsoft does this is questionable since we can't see their code.

    Oh, and BOUNDS CHECK EVERYTHING. Buffer overflow errors should have been non-existant for a half a decade by now.

    --
    - tristan
    1. Re:Fat Chance by jkrise · · Score: 4, Interesting

      "it's not important that Microsoft fix the majority of their security flaws, but that they imply they will."

      Let's have a debate at Ask Slashdot. Is it EVER possible to make Windows secure? Not maybe in the same league as Linux or Unix, but even marginally better than what entails now?

      The challenges:
      1. An integrated all-in-one tightly coupled design - anything breaks, everything compromised.
      2. Proprietary standards (if that isn't an oxmoron)
      3. Newer OS releases atleast once a year, to break competing code.
      4. Newer releases to support existing apps (3 and 4 directly contradict)
      5. Code size and complexity - I doubt anyone, even at MS has access, let alone modification rights to the variuos code bases.

      Put simply, Mission Impossible.

      --
      If you keep throwing chairs, one day you'll break windows....
    2. Re:Fat Chance by PhxBlue · · Score: 1

      I agree - and that's why Microsoft would be best off, for their long-term interests, with a team of software engineers who would redesign the Windows codebase from scratch. I'd bet a lot of the "millions of lines" of code in Windows XP is legacy Windows NT code--in which case MS should take a fresh look at what the code does, if it could be designed more efficiently and securely, and (more importantly) if any other parts of the Windows code actually use it. Of course, such measures would take years and wouldn't reflect on quarterly profit reports, so I'm not holding my breath.

      --
      !#@%*)anks for hanging up the phone, dear.
    3. Re:Fat Chance by Anonymous Coward · · Score: 0

      The OSS model of peer review on a large scale is the sole reason for such reliable security.

      Oh yeah... good thing there are so many eyes looking at Apache, SSH, SSL, Sendmail, Snort, etc, because those open source applications NEVER have security problems!

      Seriously, when will you people understand that OSS software is just as buggy as closed source software? Just because there are 5 or 6 eyes auditing the code, it doesn't mean they are skilled enough to find exploitable flaws. OSS software doesn't get peer reviewed as much as you think by people who are as skilled as you think. Bugs stay undisclosed until a hacker decides to disclose them.

      Also, buffer overflows were a secuity problem of the 90s. No piece of software should have a buffer overflow. Most recent "big" security flaws discovered have been much more complex than that. Auditing code means more than converting strcpy()'s to strncpy()'s.

    4. Re: Fat Chance by Black+Parrot · · Score: 0


      > If you've learned anything by now, it's not important that Microsoft fix the majority of their security flaws, but that they imply they will.

      Yeah, like last year's month-long binge that was supposed to make their products really secure, but hasn't actually had any discernable effect.

      And perhaps more to the point, no amount of code cleanup is going to fix the most visible problems, which are based on scripting and automation rather than on exploits of bugs. They need to design for security before they try to program for security.

      --
      Sheesh, evil *and* a jerk. -- Jade
    5. Re:Fat Chance by clary · · Score: 4, Informative

      What you suggest would be the end of Windows (maybe not a bad thing). An ex-Microsoftie says it well here: Why you should never rewrite from scratch.

      --

      "Rub her feet." -- L.L.

    6. Re:Fat Chance by Daniel+Phillips · · Score: 1

      The OSS model of peer review on a large scale is the sole reason for such reliable security.

      Right. At Microsoft, the code cleaning group will succumb to the temptation to make structural changes, the development groups will take issue with that, open war will errupt, and the whole flaming mess will spiral down to hell.

      --
      Have you got your LWN subscription yet?
    7. Re:Fat Chance by Daniel+Phillips · · Score: 4, Interesting

      ...that's why Microsoft would be best off, for their long-term interests, with a team of software engineers who would redesign the Windows codebase from scratch.

      They already tried that, it's called "NT". Things got better for a while, then the application mafia got their fingers in and it degenerated back to the current mess.

      So they could start that process over again, and be finished in 5 years, just in time to see their stock make the final dive into the subbasements. Or they could learn from Apple once again, and switch to BSD, it's free :-)

      --
      Have you got your LWN subscription yet?
    8. Re:Fat Chance by Junta · · Score: 2, Insightful

      I think his first point is valid. Even if the implementation is well partitioned and easy to apply updates to segments of the OS atomically, the problem remains that the *architecture* is designed to be too tight-knit. They are forced to honor this as earlier programs utilized this interconnectedness to do what they did (just as a lot of programs that *should* be usable by a common user only work for Administrator class users). Having to work around their backwards compatibility is biting them in the ass.

      As to your statement that the same thing happens among Linux vendors in the 3/4 points, that is just totally off base. It is true that some vendors (*cough* redhat *cough*) have a history of adopting totally new, uncompatible versions of major packages before those versions reach 'stable' (glibc, gcc for example), but it is not meant to break compatibility. Especially with gcc, the promise of the new x86 backend was so great and it was thought at the time the final gcc 3.0 would be ABI/API compatible, and that the codebase was extremely close to release and very stable. They found out that neither was the case and got stuck with a bastardized gcc '2.96', but it was hardly a strategy to push other vendors out. The ultimate point is that all these technologies that are used that break inter-distro compatibility are open, well documented technologies, and thus by definition cannot be used to secretly push out competition and make compatiblity impossible. Also, in each case, there were real, compelling reasons for the changes.

      Meanwhile, MS has a proven history of making trivial changes for the express purpose of breaking competitor products (Windows being changed to not run on DR-DOS for example). With a closed codebase, this becomes a real possiblity.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    9. Re:Fat Chance by Junks+Jerzey · · Score: 1

      The OSS model of peer review on a large scale is the sole reason for such reliable security.

      No, sorry. Linux has such reliable security because it is based on a long established operating system model with reliable security. UNIX is over 30 years old now, and there's a good underanding of the security issues. Windows NT/2000/XP started from scratch using a different model. It may be that the model isn't as good as that of UNIX, but it's also true that it's a much younger one as well.

    10. Re:Fat Chance by samael · · Score: 1

      If you wrote to the Win32 API under windows 95 and were writing a standard application (not something doing complex under-the-hood stuff like anti-virus) then chances are it will still run on XP, 8 years later.

      I frequently read about Linux programs that require such and such version of Linux.

      Now, I understand that there are unusual cases in both directions, but by and large I don't think that either system breaks most of its applications with most of it's updates.

    11. Re:Fat Chance by Anonymous Coward · · Score: 0

      Yes, such reliable security:

      http://www.debian.org/security/2003/

      Peer review obviously isn't preventing the problems. Debian has reported 4 times the number of security vulnerabilities this year than Microsoft has. We've even had within the past year people sneaking trojans into build scripts for official releases of OSS projects. Peer review? Where?

    12. Re:Fat Chance by Oligonicella · · Score: 1

      Half a decade? Jeezuz. That's been known for what, 35 years?

    13. Re:Fat Chance by 4of12 · · Score: 1

      Windows NT/2000/XP started from scratch using a different model.

      Then the NT development group should have incorporated what was known about the advantages and disadvantages of the UNIX security model (eg, the UNIX ACL are showing signs of age).

      And I think it can be reasonably argued that they started out in this direction and have done a reasonable job.

      The problem comes in when the marketing/leveraging/application managers start to to tell the OS group weird crap like IE is part of the OS, Outlook is going to do things automagically, etc.

      A basically sound security model in the OS can be shot to hell by the apps and the default configurations.

      Similarly, within Linux platforms, the majority of the security problems result from the apps and from crappy configurations and rarely from the OS itself.

      --
      "Provided by the management for your protection."
    14. Re:Fat Chance by Anonymous Coward · · Score: 0

      Try counting the total number of unfixed problems in both systems, not just recent reports. And some of the Linux problems are due to ... discovery by peer review. Indeed, there was a burst of them due to systematic review of one package.

    15. Re:Fat Chance by ruiner13 · · Score: 1
      "I doubt anyone, even at MS has access, let alone modification rights to the variuos code bases."

      I dunno, I bet that egomaniacle BillG has that. He claims he loves to code, and I bet he at least has access to it all. Or at least has a back door in there somewhere. Heck, I wouldn't put it past him to have a personal back door into every computer running windows.

      --

      today is spelling optional day.

    16. Re:Fat Chance by IWantMoreSpamPlease · · Score: 2, Insightful

      Bullshit. Writing code from scratch is the *only* way to go if your existing code base is too hosed. Look at, for example, the Be Operating System. Written from scratch, from the ground up, and it shows just how much a computer can really accomplish if you start with a clean slate.

      --
      So rise up, all ye lost ones, as one, we'll claw the clouds.
    17. Re:Fat Chance by walt-sjc · · Score: 4, Interesting

      Just read that drivel, and there ARE some valid points, but it is NOT universally true.

      Case in point, I was on a team that redesigned an entire large-scale system from scratch. The old system was built in lots of little parts using various languages (shell, perl, java, c++, c, python, lisp), multiple databases from various vendors, had virtually no internal documentation on how anything worked, etc. They system was quite unstable crashing multiple times a day, and very difficult to enhance without breaking shit. Kinda like Windows...

      We re-built the entire system in about a year (about 750K lines of code which was about half the size of the original code.) The result was amazing. After the initial deployment period where the bugs were worked out, the system was rock solid being able to stay up for months at a time, was Very easy to enhance, had tones more features and flexability. We had a great team, and a solid commitment from senior management providing the needed resources.

      Netscape's biggest problem was not starting over from scratch, but poor project management (not keeping people within original design constraints) and a lack serious commitment from senior managment. Rather than having a very tight set of requirements and design goals, things were very nebulous and got out of control very quickly. No longer were they building a new browser, but a cross-platform framework for any kind of application they could think of. When you look at projects such as Galeon, most of that bloat is ripped out.

      Rather than folling a bad example of how to run a re-design project (mozilla) MS could EASILY afford a new team to start Windows from scratch, leaving the existing team in place to continue to enhance / maintain the existing code base. This is the step that Netscape missed. They only used a small fraction of their people to maintain (and NOT enhance) the old code.

      Joel is making his claim by using the worst case example. Kinda like if I claimed that you should never put the gas tank in the back of a car pointing to the Pinto as my evidence, ignoring the thousands of other car designs that worked.

    18. Re:Fat Chance by Shimbo · · Score: 1

      Bullshit. Writing code from scratch is the *only* way to go if your existing code base is too hosed. Look at, for example, the Be Operating System. Written from scratch, from the ground up, and it shows just how much a computer can really accomplish if you start with a clean slate.

      There is a *big* difference from writing from scratch for a new project, and rewriting from scratch when you have a large installed base. The point isn't that the code won't benefit from it but that your shipping code will stagnate, annoying your existing customers.

    19. Re:Fat Chance by walt-sjc · · Score: 1

      Your code will only stagnate if you LET it stagnate. See my post below.

    20. Re:Fat Chance by clary · · Score: 1
      walt-sjc wrote:
      MS could EASILY afford a new team to start Windows from scratch, leaving the existing team in place to continue to enhance / maintain the existing code base.

      Point taken. I really wasn't considering the effectively limitless cash resources of MS. They could probably pull it off if they chose. There is an exception to every rule.

      However, the two most striking points for me from Joel's article still apply:

      Old code has been used. It has been tested. Lots of bugs have been found, and they've been fixed.

      ...and...

      It's important to remember that when you start from scratch there is absolutely no reason to believe that you are going to do a better job than you did the first time.

      For example, probably the most useful thing about any given version of a Windows system is the huge pile of tested device drivers it contains. If you wanted to rewrite windows, you should at least retain enough of the original so that you could re-use those. (Possibly the original author meant that all Windows API definitions would remain, but I took him to mean that he wanted to throw away all the bits that come on the Windows install CD.)

      By the way, I didn't mean to come off as a Joel-Spolsky-groupie. Separate the wheat from the chaff and all that.

      --

      "Rub her feet." -- L.L.

    21. Re:Fat Chance by clary · · Score: 1
      Writing code from scratch is the *only* way to go if your existing code base is too hosed.
      That would fall under the category of the "exception that proves the rule" I mention in a post below. Then the question becomes is Windows too hosed? I don't know the answer to that question. But every developer I have ever worked with has a natural tendency to answer "yes" when it has to do with old crufty code he is having to support.
      --

      "Rub her feet." -- L.L.

    22. Re:Fat Chance by cpeterso · · Score: 1


      MS could EASILY afford a new team to start Windows from scratch, leaving the existing team in place to continue to enhance / maintain the existing code base.

      You mean like when Microsoft brought in Dave Cutler and friends to create Windows NT while the Windows group continued to extend Windows 3.1 and 9x?

    23. Re:Fat Chance by cpeterso · · Score: 1


      Look at, for example, the Be Operating System. Written from scratch, from the ground up, and it shows just how much a computer can really accomplish if you start with a clean slate.


      You mean like how BeOS supported very few hardware devices? Or how BeOS had totally new APIs and few applications?

    24. Re:Fat Chance by cpeterso · · Score: 1


      they could start that process over again, and be finished in 5 years, just in time to see their stock make the final dive into the subbasements.

      Microsoft has already been doing this for the past five years. You just have not been paying attention. .NET/CLR is the new Microsoft OS.

      With Java and the browser wars, there was just too much userspace competition above the Windows OS. Microsoft needed to usurp them all with a higher-level, more encompassing "operating system". The line between programming languages and the OS has always been fuzzy.

    25. Re:Fat Chance by Daniel+Phillips · · Score: 1

      Microsoft has already been doing this for the past five years. You just have not been paying attention. .NET/CLR is the new Microsoft OS.

      Ooh, that's going to fix the IIS security holes for sure. Tee hee.

      My question: what are they going to do for an OS? Are you saying they're getting out of that market?

      --
      Have you got your LWN subscription yet?
    26. Re:Fat Chance by cpeterso · · Score: 1


      Ooh, that's going to fix the IIS security holes for sure. Tee hee.


      If IIS was written in managed .NET code running in an isolated .NET VM, then many of its current security problems would disappear.

    27. Re:Fat Chance by IWantMoreSpamPlease · · Score: 1

      3rd party support has nothing to do with what the BeOS could do with said clean slate design.

      --
      So rise up, all ye lost ones, as one, we'll claw the clouds.
    28. Re:Fat Chance by Daniel+Phillips · · Score: 1

      If IIS was written in managed .NET code running in an isolated .NET VM, then many of its current security problems would disappear.

      And new ones would appear. Meanwhile, Microsoft would tell everybody it's perfectly secure because the old bugs are gone. Then the fun starts :)

      --
      Have you got your LWN subscription yet?
    29. Re:Fat Chance by Kashif+Shaikh · · Score: 1

      I've read that article, and while it mentions good points(like the bug fixes that made functions look uglier and complex) it lacks one essential fact of inheriting code: not everyone *needs* to reuse 100% of the codebase. And this is the case when company X decides to use an open source project which has X,Y, and Z features, but you need X and Z only.

      So what happens to the code base? You don't need to re-write it, but(as the previous poster mentioned) remove all the fucking complex crap that you don't need. In my case, I have some high availability software that is complex -- to do the simplest things requires so many fucking states and so many points where things go wrong. There's approx. 8 daemons trying to communicate properly, and when the top-most daemon can't talk to one of the 7 other daemons -- all hell breaks loose.

      Do whatever you can to simplify the design, reduce the number of states, and handle errors at any level safely(integration-wise). If you have to re-write some code because of a bad design - do it.

    30. Re:Fat Chance by walt-sjc · · Score: 1

      On this comment:
      It's important to remember that when you start from scratch there is absolutely no reason to believe that you are going to do a better job than you did the first time.

      The biggest problem I have with this statement is that it assumes that you can't learn from your mistakes. True, many people don't, but good professional project managers, designers, programmers, etc. usually do. It's pretty clear from all the issues MS has with patches, security, etc. that there are lots of mistakes to learn from.

      In response to the driver issue, I would think that this is a HUGE area for improvement. Driver bugs can easily bring down the whole system (both Windows and Linux.) I have found however that user-space drivers can usually crash and burn without killing the entire OS. Big example of that is XFree86. X (and the video card driver) can die yet the OS underneath still lives. I don't know if I have actually seen a really good driver model on any OS that I have used however. Can anyone comment on other OS's like BeOS? Drivers are a sticky wicket due to hardware level access needed, and the absolutely huge variety of devices.
      The best ideas I have seen so far is a minimal kernel space core with a user-land helper but it has other performance issues (context switches and such.)

  6. About damned time by rgoer · · Score: 5, Insightful

    Now, if only they would incorporate a business ethics cleaning group, maybe we'll see some progress.

    And, yes, please somebody respond to the oxymoronic notion of "business ethics," I'm just begging for it.

    1. Re:About damned time by Anonymous Coward · · Score: 0
      please somebody respond to the oxymoronic notion of "business ethics

      I fail to understand your cynical attitude towards business ethics. Business ethics have been well established in this country, and indeed, the world. Microsoft has been a leading example of business ethics, which its leadership can take pride in.

      Simply put, one may sum up business ethics as "what is yours is mine and what is mine is mine and I need a tax break or I'll move the factory to Mexico."

    2. Re:About damned time by Anonymous Coward · · Score: 0

      Would you be satisfied with a simple pun involving "business ethics" and "ethnic cleansing"?

    3. Re:About damned time by Anonymous Coward · · Score: 0

      I believe mortars are the proper tool for fixing both their security and business ethics problems.

    4. Re:About damned time by freeweed · · Score: 1

      ethics (used with a sing. or pl. verb) The rules or standards governing the conduct of a person or the members of a profession: medical ethics.

      I'd say business ethics encompasses the rules and/or standards governing the conduct of persons who conduct business.

      I don't see the oxymoron here. Just because you may think someone is doing something wrong, does not make it unethical. It could perhaps be immoral, although then you're getting into personal beliefs, which don't necessarily apply to everyone else out there.

      --
      Endless arguments over trivial contradictions in books written by ignorant savages to explain thunder in the dark.
    5. Re:About damned time by Gonzoman · · Score: 1

      So in other words, Saddam was ethical because he followed the standard of behavior for fascist dictators. Microsort is ethical because they follow the standards of behavior for unethical corporations. Please, give me a break!

  7. I'm suprised... by DJPenguin · · Score: 4, Interesting

    ... that this group didn't exist before. Surely a company the size of MSFT would already have a team or group just doing code auditing?

    Oh well. as they said - it's a step in the right direction.

    1. Re:I'm suprised... by Lord_Slepnir · · Score: 4, Funny

      They do, but some times a clean compile just isn't enough of a code audit.

    2. Re:I'm suprised... by Anonymous Coward · · Score: 0

      My roommate has a book on his shelf: "Writing secure code" and it sports the following quote on the cover: ``"Required reading at Microsoft" -- Bill Gates. I guess "read this" doesn't mean "understand this" and don't even consider "think about this" nor "do this".

    3. Re:I'm suprised... by Anonymous Coward · · Score: 0

      ... anyone still buys into this malarchy.

    4. Re:I'm suprised... by Telastyn · · Score: 1

      QA is always the first group to be hit by timeline and resource cuts in order to 'maximize the bottom line'. Having QA staff capable of doing code auditing is $$$. Wasting programmers' time to do audits is (to suits) silly, as that's time that they could be using to create something else that can be boxed and sold.

      In my experience this problem is even worse in larger companies where employees are looked upon as black box resources (to a greater degree).

  8. Incorrect by The-Bus · · Score: 5, Insightful

    If you RTFA, it shows that this is entirely security-oriented, not performance oriented. It seems that "cleaning the code" means "patching makeshift holes over problems" not "making code athletic, slim, and fit"...

    Pity.

    --

    Small potatoes make the steak look bigger.

    1. Re:Incorrect by gbjbaanb · · Score: 4, Insightful

      not necessarily - 'cleaning the code' IMHO means going though looking for bits written by less-competant programmers, or written in a hurry to meet the deadline, or just hacked as no-one thought it'd be shipped as product.

    2. Re:Incorrect by rastos1 · · Score: 1
      Is any of your source code accompanied with comment: /* written in hurry, this should be rewritten from the ground up! : */

      ??

    3. Re:Incorrect by Anonymous Coward · · Score: 0
      Is any of your source code accompanied with comment: /* written in hurry, this should be rewritten from the ground up! : */

      Not those exact words. But the occasional:

      • Why does this work?
      • XXX: HACK
      • Drunk -- fix later
      • DON'T TOUCH!!!
      • XXX: sheesh!
    4. Re:Incorrect by Enonu · · Score: 1

      I personally use: "Can't understand. Brain on fire?"

  9. sceptic by Ashish+Kulkarni · · Score: 4, Insightful

    I'm highly sceptical of this. In my experience, security and features are always on two opposites sides of the spectrum, and Microsoft is too much on the features and ease-of-use mindset to have something really significant coming from this effort.

    1. Re:sceptic by ickoonite · · Score: 1

      This is kinda getting off the pointm, but Apple has shown that you can have both: OS X is blissfully easy to use and at the same time is a remarkably secure operating system, which also has unparalleled backward compatibility with legacy stuff - I can still play games written for the Mac 68k processor on my cutting edge iBook or PowerBook. M$ just tells you DOS is passé so move on and leave your old shit behind.

      As regards the ease-of-use factor, few would argue that Macs are hard to use. I am a recent Mac convert after rather too many years of PC use and there is just something lacking about the whole PC experience - it really does just work on the Mac.

      The most important thing of course is the underlying security. Yes, it's a BSD so all the M$ bashers can say UNIX rules therefore OS X must rule, but there's more to it than that. It's all very well having an über-secure core, but at the end of the day, it's what the user can do with the computer that matters. I found on Windows that you would have certain programs that you couldn't use if you weren't admin - what's the use in that? - and that Linux, although progressing greatly, still has too much dependence on the root user for certain things, which leads to situations like Lindows which run as root the whole time without telling the user that this is a Bad Thing.

      On the Mac, I have to give a password to install software, but that's about it. It just works and at the same time, it's pretty secure too. And of course, as a Slashdot-reading geek, I have the luxury of that UNIX core which I can tweak to my heart's content.

      In short, Apple are actually doing what people would like from Windows and PCs. When the PowerPC 970s come out, I can't see why anyone - certainly any geek - would bother with PCs any more, but then I suppose I'm biased. ;)

      iqu

    2. Re:sceptic by cyclops3590 · · Score: 1

      Yah, but you need to remember that Apple has it a little easier than Microsoft too. With FreeBSD and a Mac interface and a very controlled (proprietary) hardware base they can more easily make their operating system both system and security orientated.

      But, again Microsoft has it tougher. Remember, for over half of their existance they bought and stole the code for their products. So writing their own *quality* (whether performance or security) code is a little tougher.

      Good Moral: Cheaters never prosper (oops, that's right they do)

    3. Re:sceptic by Shalda · · Score: 4, Interesting

      Perhaps you haven't looked too closely at Windows Server 2003. I've been kicking it around for about 2 weeks now and let me give you some highlights.

      1. Stuff works. It's the easiest time I've ever had configuring a server. It's like flipping a switch.
      2. Stuff is locked down. Everything out of the box is turned off. When you do turn it on, it's locked down by default. Everything runs with the lowest privelege possible to get the job done.
      3. Reliable. Nearly anything can be done without restarting the machine. The only exception I've had so far is making it a domain controller.

      Frankly, I'm looking forward to working with it in a production environment.

    4. Re:sceptic by Wolfier · · Score: 1

      Cannot agree more.

      If one of your product's main selling point is to make as many "convenient" features as possible to a non-technically alert population, you cannot escape from security problems.

      If I were in charge I'd stop the practice of feature-bloating the products and dumbing down the user interface.

    5. Re:sceptic by estes_grover · · Score: 1

      I'm highly sceptical of this. In my experience, security and features are always on two opposites sides of the spectrum...

      Agreed 100% - the more secure system are the less convenient (and potentially more frustrating) they are to use. Maybe a bad analogy - but - commercial airlines are way more secure now than they were 20 years ago. And there's no place today grimmer than an airport; possible exception being an ICU.

    6. Re:sceptic by Anonymous Coward · · Score: 0

      And some of that "locked down stuff" can even be unlocked by you, the owner of the software!

    7. Re:sceptic by freeweed · · Score: 1

      Perhaps you can answer this question for me:

      What ports are open on a default Win2003 install?

      I keep seeing posts to the effect of 'everything is turned off', but in Microsoft parlance, turning something off doesn't necessarily do that. I can turn off file and printer sharing, for example, but still see several ports related to it being open on my machine. In fact, I've yet to see an NT-based Windows install that has no ports open, and I've played with some seriously intense hardening guides.

      If the services are turned off, why are these ports still open? If there are still services being offered, WHY?? XP home has no business accepting incoming connections from the outside world, unles the user explictly asks for them.

      And no, 'use a firewall' is not sufficient an answer :)

      --
      Endless arguments over trivial contradictions in books written by ignorant savages to explain thunder in the dark.
  10. in a nutshell by nounderscores · · Score: 4, Funny

    Microsoft is going to hire testing programmers?

    1. Re:in a nutshell by PotPieMan · · Score: 1

      Yes, instead of having their summer interns do the work. No word on what the summer interns will do. :-)

    2. Re:in a nutshell by Anonymous Coward · · Score: 0

      fetch cola and make coffee, duh.

    3. Re:in a nutshell by override11 · · Score: 1

      No word on what the summer interns will do. :-)

      But we do know it will involve cigars....

      --
      No I didnt spell check this post...
    4. Re:in a nutshell by walt-sjc · · Score: 3, Funny

      You're thinking of the OTHER Bill.

  11. It could work.. by Mr2cents · · Score: 2, Funny

    .. but only if they clean up the bugs, and not the patches.. (Hey? what's this if-clause doing here? There is no such thing as a negative packet size!)

    --
    "It's too bad that stupidity isn't painful." - Anton LaVey
  12. job security by eternal · · Score: 1, Funny

    thats a job that will never go away

  13. Re:Port to Java! by DShard · · Score: 5, Funny

    They have. It's called J#. It's microsofts answer to a question nobody asked.

  14. Re:Port to Java! by Anonymous Coward · · Score: 0

    Oh yeah! Brilliant idea!

  15. Hiring Somebody to Do the Dirty Work by Davak · · Score: 5, Insightful

    Seems like that a "code cleaning group" would be the most poorly efficient way of accomplishing this.

    Now I do not write the cleanest code in the world... but when writing with a group, I can take the time and effort to make ultra clean code--especially if my paycheck depended on it!

    Why hire somebody else to do _your_ job?

    I've never programmed in a huge group before... so maybe I missing the experience to understand.

    Davak

    1. Re:Hiring Somebody to Do the Dirty Work by archeopterix · · Score: 1
      Now I do not write the cleanest code in the world... but when writing with a group, I can take the time and effort to make ultra clean code--especially if my paycheck depended on it!
      Heh, heh.

      "Hey, why waste time on those sanity checks, let's use gets(), the security monkeys will clean it up anyway!"

    2. Re:Hiring Somebody to Do the Dirty Work by gbjbaanb · · Score: 1

      "Hey, why waste time on those sanity checks, let's use gets(), the security monkeys will clean it up anyway!" ... and then publish your name as producing the worst, security-poor code in the company and everyone can laugh at you, and the bosses can cancel your bonus.

    3. Re:Hiring Somebody to Do the Dirty Work by Jasin+Natael · · Score: 2, Insightful

      It's notoriously difficult to read other people's code. It would take more programmers to fix a project than it took to write it in the first place. Shouldn't there be a "Clean Code" peering/mentoring group instead, or a "Clean Code" review body? I'd be much more confident if someone was keeping up with the code as it was written, and going back to the programmers before the program ships, asking "What exactly does this do for the program?", or "You do realize that you should decrement this length counter before you use it, right?". And even that pales in comparison to training all the project managers/project analysts to do this with their own teams' code.

      I mean, really. A "Clean Code" group is good and all, but it's not a very efficient or effective way to make new products hassle-free, and it certainly doesn't resolve the problems caused by frequent patching. Plus, knowing the scale of large corporations (read: NOT just MSFT), the "Clean Code" group will probably be in the Canadian wilderness, hundreds of miles from the application developers. Be prepared for bogus patches that break more than they fix. I do suppose, though, since Microsoft will never rewrite code from scratch, this is the only way to get older projects up to speed.

      Here's hoping the "Clean Code" group at least includes some of the original developers, to move things along. Windows is so incredibly bloated that I doubt we'll see them finish debugging it inside this decade. I guess that's Open Source's biggest strength -- anybody can be a "Clean Code" reviewer, and you don't need an NDA or a fancy degree to do it. You don't even need to ask for permission!

      Jasin Natael

      --
      True science means that when you re-evaluate the evidence, you re-evaluate your faith.
    4. Re:Hiring Somebody to Do the Dirty Work by Reziac · · Score: 1

      I just had this weird vision of janitors going around cleaning up the nasty crufty kludges that programmers slop off their desks and onto the floor...

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  16. Where have I seen this before... by geesus · · Score: 5, Interesting

    OpenBSD have done this. They set up a team of dev's who went through the entire code fixing up buffer overflows\underflows, and all that jazz. I hope for the worlds sake (because it seems that the whole world is using Microsoft products) that they do a good job, but in my mind it wont make me feel like Windows or IIS or any other networkable piece of Microsoft written software is secure.

    --
    Gnome wasnt built in a day.
    1. Re:Where have I seen this before... by Anonymous Coward · · Score: 0

      well yes. But didn't they (the beast, not any *bsd) also have "security month" or some such nonsense over a year ago? And this is just off the top of my head. I'm sure there has been, like, several iterations of this marketroid drivel before.

      Yup, nothing like a press release from a clown in a suit with nice smile and an award winning haircut (or is it award winning smile and nice haircut, I can't remember) to substitue for actually accomplishing something.

    2. Re:Where have I seen this before... by Anonymous Coward · · Score: 0

      Microsoft ripped off OpenBSD's mantra of "Secure By Default" in Win2003. Install it, and everything is OFF and needs to be enabled manually. Pretty soon, MS will be able to claim "Zero Remote Root Holes in N Years", just like OBSD.

      In fact, Win2003 may even be more secure than OpenBSD out of box, because OBSD still has SSHD and maybe another service running.

  17. More Innovation from MS! PeerReview.Net++(R)TM by HighOrbit · · Score: 1

    In it's newest patented process, MS has just invented PeerReview.Net++.

  18. security with ignorance by Anonymous Coward · · Score: 0

    "Microsoft is a long way from its ultimate goal where users can take security for granted in its products"

    Strong security policies cannot be enforced when the end user takes security measures for granted. This is a PR campaign.

  19. Yeah, I can clean it too: by Skweetis · · Score: 4, Funny

    # dd if=/dev/zero of=/dev/hda bs=512

    Seriously, though, this is a good step for them, and I hope other software companies follow their good example.

    1. Re:Yeah, I can clean it too: by Anonymous Coward · · Score: 0

      # dd if=/dev/zero of=/dev/hda bs=512

      Nice job. You just wiped out GRUB and Linux too. Next time, try:

      # dd if=/dev/zero of=/dev/hda1 bs=512

    2. Re:Yeah, I can clean it too: by TCM · · Score: 1

      # dd if=/dev/zero of=/dev/hda bs=512

      bs=512 is woefully inefficient. For modern hard disks try 32768 or 65536.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    3. Re:Yeah, I can clean it too: by jetmarc · · Score: 1

      > # dd if=/dev/zero of=/dev/hda bs=512

      Careful... Given Windows' bad security record, /dev/zero might have
      accidently been written to by an unrelated application, thanks to
      a missing file-attribute check. You might just install the latest
      boot virus to your harddrive on Windows machines, instead of
      cleaning it up!

  20. This must be a joke by El+Cubano · · Score: 5, Insightful

    Microsoft is a long way from its ultimate goal where users can take security for granted in its products

    This is precisely the problem we have now. People already take security for granted (they don't think about it). Their goal should be to beef up security and to educate everyone about the features so that they become more security concious, rather than just take it for granted.

    1. Re:This must be a joke by martingunnarsson · · Score: 1

      I totally agree with you. MS releases lot's of patches, but people doesn't install them, because they don't know they have to.

      --
      Martin
    2. Re:This must be a joke by Lord+Kholdan · · Score: 2, Insightful

      And what do you think is easier, to write secure code or educate people in security AND make them interested in maintaining security even when it is inconvenient?

    3. Re:This must be a joke by Agent+00p · · Score: 1

      I dunno, you can't expect people to buy a car and install the airbag themselves?
      You can't sell a non-secure pc and tell john doe he has to secure it himself ...

      --
      when the shit hits the fan, it is not equally spread
    4. Re:This must be a joke by Wolfier · · Score: 2, Insightful

      Problem is, Open any magazine and you'll learn that Microsoft is on a rampage advertising campaign to preach that its products are secure.

      When in fact it is far from the truth.

      This false sense of security is exactly what makes their product very vulnerable.

      MS needs to admit the security flaws publicly, loudly, and stop preaching bullshit.

  21. hope this works... by feepcreature · · Score: 1
    I hope this works better than trustworthy computing has done so far. It's going to need real commitment from the company to allow it to make a difference. It could even mean delays to product launches (or service packs), which some parts of M$ may not be so keen on (though after recent debacles, other parts of the company would probably like fewer, better, security fixes).

    And I can't imaging their top coders rushing to join this team.

    Still, it could work...

    --
    Paul "Say no to feeping creaturism"
    1. Re:hope this works... by Anonymous Coward · · Score: 0

      I find it odd how people say the "trustworthy computing" initiative is nonsense when it's far far too early to tell.

      People seem to judge whether it is sucessful based on how many security holes there are in old MS software, surely they should only be looking at newly-released stuff (like Server 2003, IIS6, .NET Framework and the like), which haven't been out long enough to be thouroughly tested?

      Going "trustworthy computing is crap because " is nonsensical. The only way to judge with older products is how many security holes MS are finding and fixing by themselves.

      After all, how can a security initive have a magical effect of securing old software?

  22. In Soviet Redmond... by Anonymous Coward · · Score: 0

    the code fix YOU!

    1. Re:In Soviet Redmond... by Anonymous Coward · · Score: 0

      from what I've heard, Microsoft is a pretty tyranical/hierachical/fascist sort of place....like most big corporations i guess...so if it was run with true soviets, that is, a non-hierachical worker controlled software house, then maybe we would see some secure products.

      I guess allot of OSS project teams are like soviets- as I said, non-fascist horizontally organised collections of workers (coder/testers/documenters/etc) operating on the basis of free association not profit driven slavery.

    2. Re:In Soviet Redmond... by Anonymous Coward · · Score: 0

      at both extremes of the political spectrum, dictatorships behave the same way.

  23. Taking security for granted by Neophytus · · Score: 4, Insightful

    I would never want to take my security for granted, in any product. Not windows, not open source, not even goddamn openbsd that proclaims proudly 'only one remote hole in the default install, in more than 7 years' on its front page. Only one hole that has been found. The chances are that, somewhere, there is an obscure security hole that nobody has discovered. It would become the second.

    1. Re:Taking security for granted by Sentry21 · · Score: 4, Insightful

      not even goddamn openbsd that proclaims proudly 'only one remote hole in the default install, in more than 7 years' on its front page. Only one hole that has been found. The chances are that, somewhere, there is an obscure security hole that nobody has discovered. It would become the second.

      I dunno, two remote holes in 7 years is pretty good. If you want to use slashdot as a forum for anti-OpenBSD trolling, point out that the default install does pretty much nothing, and it's the services that people install anyway that are usually abused (telnet, ftp, etc.). That's more of a point than 'Only one? They probably have two!' which is just blatant trolling.

      --Dan

    2. Re:Taking security for granted by revery · · Score: 1

      So what's the solution?

      Do you mean that you look over the code for security exploits or hire someone to?

      Just wondering.

    3. Re:Taking security for granted by Tony-A · · Score: 1

      I dunno, two remote holes in 7 years is pretty good.
      Actually methinks that would be more impressive than no remote holes in 5 years (or whatever it was). Security is hard and even with a lot of effort is not completely realizable. OpenBSD is Uber-secure. They do not claim to be secure. Oh, and the default installs seem intended for immediate remote administration as opposed to local setup and only then connect to the internet.

    4. Re:Taking security for granted by Anonymous Coward · · Score: 0

      and what percentage of holes/exploits in windows (either found or not) is this? Is there a point you are trying to make?

    5. Re:Taking security for granted by Anonymous Coward · · Score: 0

      I think a negative amount of security holes would be much more impressive.

    6. Re:Taking security for granted by MrWa · · Score: 1
      That's more of a point than 'Only one? They probably have two!' which is just blatant trolling.

      I don't think that was trolling. His point was that no matter how secure the product appears to be, there is most likely an exploit or hole that hasn't been found. I OpenBSD's case that would double the number of holes in the default install.

      Of course, the whole thing could be a joke that slipped through since "If you want to use slashdot as a forum for anti-OpenBSD trolling, point out that the default install does pretty much nothing" sounds more like a troll.

  24. Re:Port to Java! by Anonymous Coward · · Score: 0
    still don't understand why anyone would waste their time with an intepreted language.

    you say it's not intepreted? you're wrong and full of Sun(tm) propaganda.

  25. Insightful? by Anonymous Coward · · Score: 2, Funny

    Try (-1, Tinfoil).

  26. Blimey, they gotta be careful... by Boss,+Pointy+Haired · · Score: 5, Insightful

    Especially if the clean-up group are not working closely with the original developers.

    Fix 1 security hole.

    Introduce 100 bugs.

    Hmmm.

    1. Re:Blimey, they gotta be careful... by schwatoo · · Score: 1

      Oh please. There's a lot they can do to improve the quality of the code without access to the original devs. Think of it as a very delayed code review. For example they could hunt down all uninitialized variables, resource leaks, possible buffer overflows, etc. Not exactly rocket science.

      --
      I have trouble with passwords among other things.
    2. Re:Blimey, they gotta be careful... by sporty · · Score: 1

      PBH, you are absolutely right. But to add on...

      It should be taken in general, regardless of fixing security holes, documentation in the code etc etc... Anything that changes in a system can introduce 100 bugs. After all, something that was relied on, that has a bug and works fine, may break after fixing said bug.

      Heh, I remember a single comma breaking a system in a vital way, for 6 months. That as fun.

      --

      -
      ping -f 255.255.255.255 # if only

    3. Re:Blimey, they gotta be careful... by El+Cubano · · Score: 1

      Fix 1 security hole.

      Introduce 100 bugs.

      Some good, rigorous regression testing would esnure this doesn't happen. Oh, wait...

    4. Re:Blimey, they gotta be careful... by halo8 · · Score: 1

      Sung to the tune of 100 bottles of beer in the wall.

      10,000 bugs and glitches in the code
      10,000 bugs and glitches
      release a service-pack, smack 1 down
      10,500 bugs in the code

      add nauseum...

      --
      The More Knowledge you have the Luckier you Get- J.R. Ewing
  27. Slashdot's Microsoft Obsession by Pave+Low · · Score: 3, Interesting
    Recently it seems not a day goes by on slashdot without a few Microsoft stories. This supposedly linux, open-source focused site seems awfully preoccupied with Microsoft for some reason, and it's not good.

    The trolling editors seem desperate to generate pageviews and posting a Microsoft piece almost guarantees to inflame and troll enough users to accomplish this.

    Look at this story...what's really that new or interesting here? This looks like just another opportunity for slashbots and "M$" haters to get their kicks.

    The more reasonable readers don't get off on that kind of stuff. Please editors, this is getting old and boring.

    --
    SIG:Slashdot: indymedia for nerds.
    1. Re:Slashdot's Microsoft Obsession by Anonymous Coward · · Score: 2, Insightful

      > Recently it seems not a day goes by on slashdot without a few Microsoft stories.
      You must be new around here...

      Here's a tip for you: go to your Preferences and filter out what you don't want to see.

    2. Re:Slashdot's Microsoft Obsession by krystal_blade · · Score: 4, Funny

      Look at this story...what's really that new or interesting here? This looks like just another opportunity for slashbots and "M$" haters to get their kicks.

      You're new here, aren't you?

      krystal_blade

      --
      It will be easy to motivate our fellow man; there is hardly anything people treasure more than not being annihilated.
    3. Re:Slashdot's Microsoft Obsession by Mr_Dyqik · · Score: 1

      I like way I saw this story with a big advert under the story for Visual Studio .Net.

      Hmm.
      1. Get adverts from Microsoft,
      2. Run lots of Microsoft stories,
      3. Get more adverts from Microsoft
      4. Profit
      5. Switch Slashdot to IIS
      6. Lose profit.

    4. Re:Slashdot's Microsoft Obsession by gseidman · · Score: 1
      It's "News for Nerds, Stuff that Matters" not "Linux, Open Source, and All That Jazz." "The more reasonable readers" to whom you refer are not the target audience. The stuff about astronomy and astrophysics has nothing to do with OS or Linux either, but it's of interest to us nerds. Furthermore, Microsoft's status as the 500 pound gorilla means that most of its moves fall under "stuff that matters" to the world at large and nerds in particular.

      Finally, I will point out two things:

      1. There is no such thing as a news feed that contains only content any individual person cares about. (Well, no news at all means no objectionable content, but that's a trivial solution.)
      2. It is a good thing that there is no such news feed. It's bad enough how easy it is to avoid opinions with which one disagrees. Exposure information and opinions that do not fit your world view improves you as a person.
    5. Re:Slashdot's Microsoft Obsession by Anonymous Coward · · Score: 0

      'recently'? Are you on crack or have you been hiding under a rock for the past 5 years?

    6. Re:Slashdot's Microsoft Obsession by Anonymous Coward · · Score: 0

      You obviously have no clue about Slashdot readers. I come to this board because I am looking for reasons to cut down Microsoft every opportunity that I get. Think of Slashdot as a great resource for supporting arguments against a flawed company. It's nice to see Pro-Linux/Unix stuff here too, but that's not the main reason most of us come here. Just to be perfectly clear... I *DO* use Microsoft products, but that doesn't mean that I should want to or have to. If there is a reasonable argument against using their products and I can levy that against my employees, then I will do so. That's the point of Slashdot. Besides, chances are that a troll like yourself would complain thusly:

      "What's with Slashdot's obsession with Linux? It seems that every article linked to here is a paean to Linux. The more reasonable readers here don't get off on that. Please cut it out."

      How you got modded to +5 I'll never know. You are a most obvious troll. Or... you're a clueless suit.

    7. Re:Slashdot's Microsoft Obsession by Daniel+Phillips · · Score: 1

      Recently it seems not a day goes by on slashdot without a few Microsoft stories. This supposedly linux, open-source focused site seems awfully preoccupied with Microsoft for some reason, and it's not good.

      Sure it's good, it keeps us entertained, never mind pumping up Slashdot revenues. Besides, there is no shortage of Linux people that ignore Microsoft completely. It all balances out.

      --
      Have you got your LWN subscription yet?
    8. Re:Slashdot's Microsoft Obsession by the_machine · · Score: 1
      Recently it seems not a day goes by on slashdot without a few Microsoft stories. This supposedly linux, open-source focused site seems awfully preoccupied with Microsoft for some reason, and it's not good.

      What is it about "News for Nerds" that means we can only talk about Linux?

    9. Re:Slashdot's Microsoft Obsession by Spez · · Score: 1

      Okay, first, have you ever read slashdot "slogan"? No? Well look slightly up... upper a bit, there : News for Nerd. Stuff that matters. News!! Must I take a dictionnary and give you the definition of this word? If /. wasn't giving info about MS and only giving info regarding Linux, it wouldn't be news! It would be publicity, or propaganda! And as much as I am concerned, MS hiring a tactical force to clean its code IS "Stuff that matters"

      --
      I wouldn't mind you in my head, if you weren't so clearly mad -Lews Therin Telamon
    10. Re:Slashdot's Microsoft Obsession by J3M · · Score: 1

      Keep your friends close and your enemies closer. In order to compete effectively, you must know what your competition is doing.

      --
      Aych tea tea pea colon slash slash slash dot dot org slash
    11. Re:Slashdot's Microsoft Obsession by Tony-A · · Score: 1

      Look at this story...what's really that new or interesting here? This looks like just another opportunity for slashbots and "M$" haters to get their kicks.

      You're right. "what's really that new or interesting here?" Microsoft is making yet another attempt to improve security. Nothing new or interesting. (Now if Microsoft were to do something that would make a difference, that would be new and interesting.

      Yes I use Microsoft, and yes this is how I get my kicks. When we finally get rid of all the Microsoft stuff, I will no longer be interested in Microsoft bashing. I will admit to being unreasonable. I expect computer systems to work. Whenever they do not, they should be ridiculed.

    12. Re:Slashdot's Microsoft Obsession by Anonymous Coward · · Score: 0

      You might think of this site as "Slashdot" but to me it is still "Rob Malda's Afterstep Modification Page."

    13. Re:Slashdot's Microsoft Obsession by Gonzoman · · Score: 1

      Look up ... look way up ... and I'll call Rusty.

      Appologies to those who didn't grow up with CBC in the sixties.

    14. Re:Slashdot's Microsoft Obsession by miu · · Score: 1
      This supposedly linux, open-source focused site seems awfully preoccupied with Microsoft for some reason

      Because Microsoft declared Linux to be their number #1 threat. When a company with a history of destroying competitors declares war then you should probably pay attention.

      and it's not good.

      It can get old, especialy the uninformed bashing, but stories about Microsoft are legitimate and often interesting.

      --

      [Set Cain on fire and steal his lute.]
  28. Code audits will help, but... by Zigg · · Score: 5, Insightful

    What is really needed from Microsoft is flat-out redesign, and that means breaking a few eggshells.

    The most telling bit from this article: "...the majority of viruses written attack Microsoft products..." Yes, it is certainly true that some of them exploit real bugs, but the majority of viruses target Microsoft software design, not buffer overflows.

    I'm willing to bet the code audit team members don't have redesign authority; nor should they. Hopefully, they do have easy access to people who can make the design decisions and can raise issues quickly. Necessary design changes are going to break things.

    You can audit the code all day and all night and you will end up with a more secure product in the end. But to solve the real problems with Microsoft security, the product needs to be designed with that security in mind.

    1. Re: Code audits will help, but... by teemu.s · · Score: 1

      the funny thing about design issues and mcrosoft is, that they MS Press brought out a book called "Writing secure code", where theyre talking about exactly the issues you posted .. so I think they are aware of this but not able doing stuff in that way.

      They tell you how important it is to design carefully, but what chance of survival does the best written application have, if it has to run on a bad written basis (a.k.a. IIS, Windows)?

    2. Re:Code audits will help, but... by KAMiKAZOW · · Score: 1

      Necessary design changes are going to break things.

      Believe it or not, but MS already did that with Windows Server 2003 (at least partially).
      That's the reason why the backward compatibility of Win2003 is quite bad by Windows standards. New Windows versions usually have a backward compatibility of >90% for normal applications. A MS guy said a while ago that "only" ~60% of WinNT4 apps will still run on Win2003.

  29. Some name suggestions.. by jkrise · · Score: 3, Funny

    "The new group is called Security Engineering Strategy"

    A weak name, I suppose. Some suggestions:

    1. Next Generation Secure Computing Strategy.
    2. Social Engineering Strategy.
    3. Brainwashing Services (BS, for short).
    4. Severe Acute Repair Services Group (SARS group)
    5. Purity Enhancing Networked Information Services. (figure it out)

    --
    If you keep throwing chairs, one day you'll break windows....
    1. Re:Some name suggestions.. by m1chael · · Score: 1

      i personally like the "Thinking about doing the thing but it costs too much money to do the thing" thing.

      --
      I know you are psychotic, but please make an effort.
    2. Re:Some name suggestions.. by Bostik · · Score: 1

      Upon seeing the article, I got an instant mental image. The group is supposed to oversee, in one form or other, the development and design of secure platform.

      Security Oversight Strategy, or S.O.S. for short?

      --
      There is no such thing as good luck. There is only misfortune and its occasional absence.
    3. Re:Some name suggestions.. by Anonymous Coward · · Score: 0

      I've never heard of a Purity Enhancing Networked Information Service, but apparently I can get a monster one by clicking on this wonderful email I recieved this morning

  30. You Cannot Clean The Code.. by Gaggme · · Score: 4, Funny

    ..you can only realize the truth, that the Windows codes is the virus.

    --
    My ignorance is a perfect shield against your logic.
    1. Re:You Cannot Clean The Code.. by thebreathalyzer · · Score: 1

      No joke. I upgraded from 98 to XP a couple of weeks ago (no sympathy please- I should have known better). All of a sudden my AV detected a virus infecting my system (mbr). Now I know why you're supposed to turn your AV off before you upgrade...

  31. does that mean less RAM required? by illumina+us · · Score: 1

    So does that mean I won't have to use 128MB of RAM just for Windows?

    --
    -illumina+us "I put on my robe and wizard hat..."
    1. Re:does that mean less RAM required? by m1chael · · Score: 1

      you are lucky, your ram isnt affected at all.

      --
      I know you are psychotic, but please make an effort.
    2. Re:does that mean less RAM required? by illumina+us · · Score: 1

      Actually, my 256MB module just died, my 128 MB module is dying, and that would leave me with a whopping 10 MB of onboard RAM left. Suffice it to say, I need more RAM, I shall get enough to dump Windows into RAM so I don't have to use a page file.

      --
      -illumina+us "I put on my robe and wizard hat..."
    3. Re:does that mean less RAM required? by Anonymous Coward · · Score: 0

      Sounds like you need the KDE desktop environment, as well as the Gnome libraries simultaneiously loaded into memory, and maybe a Motif app and Mozilla to bring a little extra memory usage to the table. Your anger at how slow your computer will have become will only fuel your trolling fires, and help ensure Slashdot remains the festing pile of whiny losers complaining about M$. HTH

    4. Re:does that mean less RAM required? by illumina+us · · Score: 1

      One thing thought, I've never been able to boot any distro of Linux in 20s flat nor have it run any of my favorite games without massive re-coding. Then again, I've never had any distro of Linux crash on me either.

      --
      -illumina+us "I put on my robe and wizard hat..."
  32. The only thing that will save MSFT's code.. by xtermz · · Score: 4, Insightful

    ...is peer review by knowledgable people within the security community. And how do they have peer review of their code?..... open the source, of course.

    ok, i did not mean for that to rhyme, but you get my point. Microsoft is a big self reliant entity that hires like minded people. Thats not who they need reviewing their code. They need objective 3rd parties with real world experience in security and systems. I'm not saying they need to put the code to WinNT on an FTP server for all to see, but loosening their grip a little.

    Once MSFT realizes that they dont have to be nazi-esque with their firm grips around their code base, and they can succeed by opening up a little, they will do great things, imho. They havent quite learned that yet..

    --


    I lost my concept of community when my community lost all concept of me.
    1. Re:The only thing that will save MSFT's code.. by _Swank · · Score: 5, Insightful

      open source is certainly one way to potentially increase code quality with respect to security. but there are others, including introducing a group within the company to audit exactly that.

      there are obvious drawbacks to microsoft opening their source, including a large collapse of their main revenue streams and huge impact on their existence as a company. at least, as microsoft is structured now, opening their source is not a good business decision (no matter your feelings on microsoft as a company).

      open source is not the software savior it's often made out to be. all software will not be open source. ever. demanding that every software company do just that is both unreasonable and generally unhelpful. we should be demanding that software companies produce more secure, stable, and user-centered software. however each company chooses to do that shouldn't matter, as long as that end goal is reached.

    2. Re:The only thing that will save MSFT's code.. by bmj · · Score: 1

      amen. too bad your post will be modded down since it's not rah-rah for open source.

      if microsoft was serious, they would bring in security folks as consultants, have them sign NDAs, and let them look at the code. that sounds a lot like peer review to me.

      --
      Whereof we cannot speak, thereof we must be silent. --Ludwig Wittgenstein
    3. Re:The only thing that will save MSFT's code.. by Anonymous Coward · · Score: 0

      Joe programmer would check windows code for free more efficiently then he'd do for salary? Doesn't sound logical.

    4. Re:The only thing that will save MSFT's code.. by Tsu+Dho+Nimh · · Score: 1
      He was not advocating that MS convert their source code to OSS ... he was merely advocating that they get some persons who have not grown up in the Microsoftian culture to vet the code for security and recommend changes.

      As it is, they are "code-blind", because everyone has spent so much time working the Microsoftian way, getting the code to work, that they can't see the holes that will let it work in unexpected ways. You need a fresh pair of eyes that is looking for ways the code might be coaxed to work in a way the programmer did not intend.

    5. Re:The only thing that will save MSFT's code.. by maxpublic · · Score: 1

      I agree that opening MS code would be a mistake for the company. Exposing spaghetti code, bad programming practices, bloat, and legacy chunks included because no one left at the company has a clue what they do (other than break things if they're removed) would bring ridicule down on MS that makes the typical Slashdot flurry look kind by comparison. It would, in fact, simply prove that the code is badly hacked and virtually incapable of being properly secured.

      Opening the source would be an incredibly bad business move, especially given the growing suspicion and distrust of MS products. It's certainly something you wouldn't want to do when Linux is making slow, sure inroads in areas you want to dominate - and the Linux code is already 100% open for anyone to review. If you know your own code looks like hell in comparison to the Linux kernel, you'd have to be a complete idiot to invite that comparison on a world-wide level by opening your code to inspection.

      In any event, there's little need for every app to be open source. The OS, sure; I can't imagine trusting a black box OS to run my computer, never knowing what's *really* going on behind the curtain. Even if I myself only review a small fraction of the code (and this is a true statement, in my case) I'm secure in the knowledge that I can review it any time I want, and that others have done so for the areas that I haven't gone over, others that I trust.

      But as for apps...I use Opera as my browser. I have no access to the code. I do not care about access to the code. Opera does one thing - gives me web access - and I don't see this as a terribly critical activity. I have no reason to suspect the folks at Opera of including anything malicious or inanely stupid in their black box; and if I did, I can always fire up an OSS alternative like konqueror or mozilla. So there isn't any need whatsoever for something like Opera to be open source; Opera seems trustworthy (no lawsuits, much less convictions) and should it ever become a question I can use a different browser that is OSS at any time.

      Open source is certainly not required for every product, or even most products. Like I said, I wouldn't dream of trusting a non-open OS, but I can, have, and will trust proprietary software for certain activities. Especially those I consider to be relatively unimportant - like web browsing - or that are meant purely for entertainment purposes (e.g., any computer game). Insisting that *everything* be open source is rather ridiculous - there isn't a need for such a sweeping demand, *especially if there are open source alternatives to proprietary products*. If there are, then you can satisfy everyone, including me (i.e., using Opera because it's the best browser out there, even if it isn't open).

      Max

      --
      My god carries a hammer. Your god died nailed to a tree. Any questions?
    6. Re:The only thing that will save MSFT's code.. by Anonymous Coward · · Score: 0

      Microsoft will not open their code. They would never survive the ridicule.

    7. Re:The only thing that will save MSFT's code.. by Gonzoman · · Score: 1

      Programmers will fix problems to make their own system work better. If they then release these fixes to the community we all are better off. This is the basis of open source.

  33. Doesn't look like they'll fix existing code by shayborg · · Score: 5, Informative

    First, this isn't a code cleaning initiative, as someone above noted -- the article says that the new group will "establish new software development processes and create tools for its programmers so that future Microsoft products will have fewer security flaws." So it looks like their job is to just improve the programming methodology at our favorite software company.

    Second, there are only ten people on this task force. Will they have enough time to fix the programming methodology for all Microsoft software? Somehow, I doubt it -- and it doesn't take much imagination to guess that the Mac products, for example, aren't likely to be the primary targets, as well as any spyware that Microsoft finds convenient (*cough*WMP ;-)*cough*).

    So it's a step in the right direction but I think they need to use more manpower to solve this problem. God knows they have plenty of it. Until they do, across the board, I don't think many of us will ever trust Microsoft's security. (I'll leave the question of trusting Microsoft itself to another discussion.)

    -- shayborg

    1. Re:Doesn't look like they'll fix existing code by Winterblink · · Score: 1

      Of course the task force is small now. I've never worked on a project where a gigantic team of hundreds was allocated the task of the initial analysis. I can guarantee that tomorrow these ten people will not be sitting down and writing code. Come back to this in six months or a year and see how big the team is.

      --
      "I'm a leaf on the wind. Watch how I soar."
      -Hoban Washburn
    2. Re:Doesn't look like they'll fix existing code by jafac · · Score: 1

      business process? You mean like this?

      http://www.sei.cmu.edu/cmm/cmm.html

      There's a right way, and a wrong way to do this stuff. If it's done incorrectly, the next version of Windows we'll see will be Windows 2020.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  34. That's pretty funny by krystal_blade · · Score: 3, Insightful

    'Microsoft is a long way from its ultimate goal where users can take security for granted in its products...

    The way I hear it, most people already take security for granted with MS products.

    And are proven idiots.

    krystal_blade

    --
    It will be easy to motivate our fellow man; there is hardly anything people treasure more than not being annihilated.
  35. they previously did not have such engineer team? by despistao · · Score: 1, Insightful


    what a company!

  36. Re:Port to Java! by dimer0 · · Score: 2, Interesting

    Yea, it really sucks that I can develop and test code on my Windows laptop and just copy the compiled files over to an AIX box, or Intel/Linux box, and everything works perfectly.

    Methinks you're a disgruntled C programmer feeling the world's leaving you behind.

    Get with it - there's tools for every job - pick the one that works best.

    My original point was made in humor partly - but the main point was that normal security exploits attacking buffer overflows, for example, are a non-issue in my 'interpereted language'.

  37. Open it up by Midajo · · Score: 2, Interesting

    Nobody in their right mind is going to simply take it for granted that any given operating system is secure. Considering Microsoft's track record of programming, they are the last people anyone should blindly trust. The only way to deliver security on a project of this magnitude is to open the source to peer review.

  38. not surprised by the majority by Anonymous Coward · · Score: 1

    The majority of software viruses are written for Microsoft products...this probably has something to do with the fact that they're on the majority of computers world wide.

    Please, like OSS software is so clean and bug free. At least with MS software, I know there's a division of people working on producing software fixes. With OSS software you get the fix whenever the person feels like it...I welcome the fact that they are admitting their code is buggy and are trying to fix it. When's the last time you heard OSS people say their code is buggy, because honestly they both are.

    1. Re:not surprised by the majority by m1chael · · Score: 1

      but with oss you dont necessarily have to depend on one company to fix them.

      --
      I know you are psychotic, but please make an effort.
    2. Re:not surprised by the majority by Anonymous Coward · · Score: 0

      As has been brought up by a lot of other posters here, a large majority of MS's problems are ones of design, not implementation!

      Nobody ever said OSS software doesn't have bugs, but the bugs, in general, do not bring the entire system crashing down around you. Until the past few revisions, the KDE GUI wasn't any better than Windows', BUT a crash in KDE simply forced me to kill the KDE process(es) and restart them. The OS did NOT go away. Windows, with it's GUI so tightly integrated into the OS (hell, everything is integrated into the OS) invariably brings the entire OS down with it.

      Security issues in IIS, Outlook and the myriad other vulnerabilities in MS software that are used by hackers and virus writers usually take advantage of DESIGNED-IN features that most people in their right mind wouldn't dream of adding. In fact, many many people asked MS to at least consider the ramifications of features they announced they were adding long before they became security issues. In every case, their pleas fell on deaf ears.

      Until this basic philosophy changes, no amount of review will fix MS security problems.

    3. Re:not surprised by the majority by Anonymous Coward · · Score: 0

      Yes, you depend on someone who has only personal pride as their motivation to fix it.

  39. Code Review ? by jalilv · · Score: 1

    Are they saying that they will start doing the code review from now on ? Does it mean that they were not doing it before and not following the procedure that is standard in most of the software development firms ?

    - Jalil Vaidya

  40. Re:Port to Java! by dimer0 · · Score: 1

    I have still refused all projects that call for Java programming.

    Did you stomp your feet when doing so?

    If it cannot be programmed with a real language, I don't wanna do it.

    Oh, that's brilliant. Do you tell your management that? .. Or, hmm, maybe you're a school-boy.

  41. The fearless leader by nob · · Score: 1

    The article failed to mention the individual who will be heading the group. I wish Mr. Pen and the rest of his team the best of luck for this endeavor. They'll need it.

    --
    daed si luap
  42. In other news, by Sevn · · Score: 1, Funny

    Farmer John has decided to close the gate after all
    the horses have run away.

    --
    For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
  43. Is that a new mission statement I hear? by krystal_blade · · Score: 1

    its ultimate goal where users can take security

    And here I always thought Microsoft's "ultimate" goal was world domination...

    I mean, that's what I've read here on slashdot...
    (cognitive dissonance takes over...)

    They must have gotten that statement screwed up...

    krystal_blade

    --
    It will be easy to motivate our fellow man; there is hardly anything people treasure more than not being annihilated.
  44. Don't be dismissive by pchown · · Score: 5, Insightful

    It's tempting to dismiss this sort of announcement as "more of the same", "PR spin", and so on. Perhaps it is, but I don't want to get caught when the security spending starts to produce real fruit.

    Think about the success of OpenBSD. In terms of security holes it's probably an order of magnitude better than other free operating systems, and Windows. This result was largely obtained through code auditing. If we aren't careful, in a few years, Microsoft will turn the tables on us. The code auditing they've done will have paid off, and we'll have it all still to do (for the typical Linux distribution, OpenBSD is different).

    Laughing at your competitors is a risky strategy.

    1. Re:Don't be dismissive by Ashish+Kulkarni · · Score: 4, Insightful

      Yeah, but OpenBSD tries to avoid adding too many features during its code audits ... and OpenBSD already has gone through multiple, LONG audits (recall that Theo did a year-plus audit soon after forking from NetBSD). Also, OpenBSD tends to be very conservative and behind the cutting edge for this very reason (not that it's a bad strategy, mind you). However, this does not sit very well with Microsoft's strategy of adding more and more features in every new product release....

      Security is not a methodology which you can apply like any other tool -- it is a mindset which has to be cultivated in the original coders AND carried over to the ones who bugfix/test the code.

    2. Re:Don't be dismissive by Anonymous Coward · · Score: 0

      The fact is that Microsoft has been turning the tables on you for a while and most /.ers don't even know it because they are so busy being 133t Linux hackers that they can't be bothered to back up their MS bullshit with some actual hands-on knowledge.

      We all should know by now that Windows 2000 was a big improvement over previous Microsoft operating systems in stability and security, even though there were still plenty of valid criticisms.

      Now Windows Server 2003 is out. I ordered an evaluation copy of it and have been playing around with it for a few days. I haven't been able to get too deep into it yet but some some of the things I have noticed right off are:

      1. Nothing extra is installed by default. Nothing. If you want RAS, IIS, or even file and printer sharing services then you have to manually install it after the OS is loaded. No more insecure services being installed and enabled by default. Not only that, but of the services that are installed there are more stopped than started with many being disabled by default.

      2. Default permissions are more stringent. One of the obvious problems with Windows 2000 was that default permission on the root drive was full control to Everybody. That is no longer the case. Default permissions for normal users are read and execute only.

      3. IE is configured to start in an enhanced security configuration. If you are familiar with IE security zones then what this basically means is that the default security level for the Internet zone is now the same as that of the Restricted zone, which is high. ActiveX and scripting is disabled by default along with several other features.

      4. The default security policy seems to be locked down tighter, although I haven't had a chance to look at all of the options yet.

      These are just a few things I have noticed so far but I have read reviews that indicate much more has been done. The biggest change is probably the complete rewrite of IIS. It will be interesting to see if it is any better but I expect it will be.

      If /. posters don't wake and quit basing their opinions of Windows on the 95/98/NT4 days, they are going to be in for a big surprise when MS puts up a good fight against their precious Linux. It has become obvious to me that they are listening to criticism and are serious about correcting the issues.

    3. Re:Don't be dismissive by eastshores · · Score: 2, Insightful

      "Thinking About Security: Secure by Design, Secure by Default, Secure in Deployment and Communications"

      http://msdn.microsoft.com/msdntv/episode.aspx?xm l= episodes/en/20030513SecurityMH/manifest.xml

      Take a look at this video, it is from one of their security groups. Listen to the changes made in Windows 2003 Server. The box is closed by default, does nothing until you enable services.

      They've hardened IE on servers, games can't be installed, Services are now being re-worked so they don't require elevated privilages.

      People can criticize all they want for the past sins, but I think it's important to keep an open mind about reality.

  45. Credit Where Due by k0de · · Score: 5, Interesting

    If the 3r33t community hated other software/platforms as much as they hated Microsoft I'm sure the level of bugs exposed/viruses would be equally as high. I'm not saying Microsoft throws all beautiful software around, but if you devote time to finding holes in software, you'll find it no matter who the maker. As a fair example, look at what happens Larry Ellison tries to make grand claims about the stability of Oracle software. Many of you have valid opinions, and that's respectable, but how so many people can blindly hate Microsoft because of the hate trend makes me want them to succeed.

    --
    I'm wrong and so are you.
    1. Re:Credit Where Due by BadDoggie · · Score: 5, Informative
      Larry Ellison begged the world to break Oracle. They spent millions buying up the backs of every business magazine and full pages in serious and financial newspapers claiming it was "unbreakable". They specifically said that no hacker could get into it. Real hackers and crackers have always said they do it for the challenge. What better way to provide a challenge than to spend tens of millions in order to yell, "C'mon, you weenies! I dare you!"

      Microsoft also got hit a lot harder every time they claimed some semblance of security. They've learned their lesson, albeit slowly. Now they only claim to be working on improving security, considerably different than Larry's claims.

      woof.

    2. Re:Credit Where Due by k0de · · Score: 2, Insightful

      Now they only claim to be working on improving security, considerably different than Larry's claims

      Yes, considerably more humble. At least Microsoft knows better. That's a lesson Larry hasn't been able to learn from Microsoft's mistakes, so now he's learning the hard way.

      The bottom line is that staying under the radar doesn't mean your software is stable. Any company with Microsoft's faithful hate troop would be humiliated by their own software. Oracle is just one example.

      --
      I'm wrong and so are you.
    3. Re:Credit Where Due by Anonymous Coward · · Score: 1, Interesting

      DJ Bernstein has made claims about the stability of qmail, even rewards for anyone who finds a security exploit. I don't think anyone has ever found exploitable code in qmail, and it's open source.

      The amazing thing about Oracle and MS-ware is that it's closed source and exploits are still popping up all the time.

    4. Re:Credit Where Due by cjjjer · · Score: 2, Informative

      To bad Larry's claims of being Unbreakable? were squashed. As the article says:

      "Some security experts have said that the discovery of these vulnerabilities changes the claim of "unbreakable" from marketing hype to a false sense of security."

    5. Re:Credit Where Due by ReTay · · Score: 1

      Ok credit where it is due and as soon as MS puts out some secure product I will give them full credit. I am not talking something like the speed or response from open source when it comes to bugs but personally until I see things like Shatter fixed it is just PR. Nothing more I don't hate MS actually. Hate would include WAY to much emotion. They have had several ideas that had merit. Take the security hole ridden (!) front page. Now someone who doesn't have the time or interest to learn html can make a web page for their family or what ever. The basic idea is a good one, and then they have to go and break the standards to try to embrace and extend it and basically render it useless. No one will use the extensions now because not even MS claims it can be secured. MS can come up with a original idea now and again but by the time it makes it to the consumer it has been twisted by the embrace and extend idea that is has been reduced to an abortion.
      That mentality pervades the companies products to such a great degree that anything that they put out becomes a liability instead of something to be proud of.
      I hope the new team will improve things however I don't think I have to guess what will happen if there needs to be a choice made between embrace and extend and software quality.

    6. Re:Credit Where Due by 10am-bedtime · · Score: 0, Offtopic

      hehe, you answer your own question. hate of usloth is not blind in a vacuum; usloth encourages both blindness and so-called "trust". when that trust is ultimately betrayed (as it always is), it is no surprise the result is blind hate. duh.

      better to have informed hate, because at least there is a root cause that can be examined and the hate eventually channelled into productive action (like fixing the root cause), presuming the hate is not so off-putting to the recipient. w/ free software, there is much passionate (anti-)advocacy but at the end of the day, code is there to use, improve, and pass around. informed hate as found in the free software community is not so bad, and can even be ludicrously entertaining even when unproductive.

      anyway, as for the other two combinations, blind love and informed love, the former leads to betrayal (see above) and the latter has its own dangers but is still much preferable to the grinding drag that is having to deal w/ any kind of hate. but in all cases, those who deal keep it real.

    7. Re:Credit Where Due by acebone · · Score: 1

      Frontpage wasn't Microsofts idea - they bought the company who made Frontpage in the first place...

      Any truly original M$ ideas ?

      --
      Check out my PHP Url Validator
    8. Re:Credit Where Due by ichimunki · · Score: 1

      Good god, shut up! First of all, the level of security flaws found is generally the same. The problem with the bugs/holes found in MS' software are often much more severe or easily exploited. The problem is that no thought was given to security at any point in the process. I mean, what kind of idiot do you have to be to write an email program that automatically opens an email from an unknown/untrusted source, finds a "script" therein, and runs it... all without any sort of action on the part of the user, who doesn't even have to "open" the email thanks to the preview feature?

      Second, I don't think anyone likes Larry Ellison any more than they like Bill Gates. At least Bill Gates still seems like a bit of a nerd. Larry Ellison, OTOH, is an arrogant rich a-hole.

      Third, if MS had any sort of real security, it wouldn't matter how much black hats and script kiddies hated them... in fact, you'd think the black hats and kiddies would be big fans. People looking to exploit systems are looking for easy targets... How can they not see MS software as a giant bullseye? It's everywhere, so any crack is likely to be massively successful in terms of exposure... and it's like swiss cheese, so why work your tail off trying to get into some ubersecure VMS mainframe when you can impress your buddies by tweaking the output of an Outlook Virus Construction kit or exploiting some other brain dead "feature" in an MS product?

      Oh shoot. I just fell for some pro-MS troll didn't I?

      --
      I do not have a signature
    9. Re:Credit Where Due by deranged+unix+nut · · Score: 4, Interesting

      Check out Windows Server 2003 - Microsoft was really trying to focus on security, and even got bashed by customers because they made it so secure that some of the applications wouldn't work anymore.

      You don't "fix" 50 million lines of code overnight, especially not when it has taken 10 years (or more) to write. However, all of the developers really did take a few days to go through a set of classes on how to write secure code, and then spent the next month reviewing their code for security problems. All of the program managers really did go to classes to learn about security vulerabilities and how to find security weaknesses in their designs, and then went back and updated designs where needed. All of the testers really did go to classes to learn how to find security bugs and then created security test plans and spent a month doing nothing but looking for security bugs.

      It probably isn't perfect, if Microsoft went for perfect you would be paying ten to twenty times more for the software, but for the first stab at really fixing the server operating system so that it is secure out of the box, I would say that 6 months of effort went into making Windows Server 2003 secure that wasn't in the plan prior to the trustworthy computing initiative.

    10. Re:Credit Where Due by Black+Copter+Control · · Score: 1
      If the 3r33t community hated other software/platforms as much as they hated Microsoft I'm sure the level of bugs exposed/viruses would be equally as high.

      Intruders and script kiddies like Windows because it's so badly designed and written. Remember when XP was in pre-release and a security expert started screaming about how XP had desin problems that were going to dreate big security holes? MS sent in their big honchos to convince this guy that it was OK, but they didn't even bother arguing that XP was secure. Their argument was that there were so many other security problems, that adding in this design flaw was just a bucked in the ocean. It's that sort of thinking that has made MS software such a fertile ground for script kiddies.

      The code is far from modular and well designed. Nobody (or almost nobody) can wrap their heads around it. The constant holes being punched in it are a symptom of years of marketing-driven building... Marketing thinks that some new doodad would look good, so engineering was forced to impliment it... whether or not they thought it was a good idea.

      For that reason, you got things like 'login' security where you could just provide a new login (win95), a "journaling filesystem" that needs to be FSCKed after every crash and software that blue-screened when Bill Gates himself is showing it off.

      Up to now, MS code releases have rarely been up to what the Open Source community would call 'alpha', nuch less final release quality. From what I can see, MS is driven by the marketing division. Up until now the Marketing group has gotten away with forcing the release of sub-standard products that looked good on the showroom floor and so they've done so. Now MS is getting shown up in terms of software quality and security by an open-source community that they've been bad-mouthing as a bunch of amateurs with no centralized control and it's been back-firing on them. It turns out that, when given a reasonable choice, people prefer stable and secure code and MS does not have a history of supplying that. Unfortunately for microsoft, they're now being bitten on the ass by a corporate culture which considers bugs and security holes the cost of doing business.

      I don't dislike MS-Windows just for the fun of it. I dislike MS-Windows because it's bad software, and I don't want bad software as m onlychoice.

      --
      OS Software is like love: The best way to make it grow is to give it away.
    11. Re:Credit Where Due by essdodson · · Score: 1

      MS has tried this once or twice. I think the last one I'm aware of was putting up a 2k server prior to release and inviting people to give it's security the run around. Sadly it received mostly packets from kiddies so that program was terminated.

      --
      scott
    12. Re:Credit Where Due by Anonymous Coward · · Score: 1, Informative

      Dude, that "security expert" was none other than Steve Gibson and his Nanoprobes. Nobody took that seriously except for non-technical AOLers (such as yourself, apparently).

    13. Re:Credit Where Due by jafac · · Score: 1

      There are PLENTY of Microsoft enthusiasts out there who would kill or die for a chance to peek at the source code, to attempt to address, or at least understand observed buggy behavior.

      That's the whole POINT of Open Source.

      Last year, I spent 4 weeks working with Microsoft Developer support trying to figure out why Win2k was behaving the way it was. And if I or any of my co workers could just have looked at the source code, we would have at least had a shot at fixing it. In the end, Microsoft admitted that they could not find a developer who understood how this particular component worked (WFP), nor could they commit the resources to look at the code to figure it out. Bottom line was - we were given free reign to define the Official Documented Microsoft Behavior as, what we observed. As opposed to what Microsoft had Documented.

      In other words, BAH!

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    14. Re:Credit Where Due by Anonymous Coward · · Score: 0
      Check out Windows Server 2003 - Microsoft was really trying to focus on security, and even got bashed by customers because they made it so secure that some of the applications wouldn't work anymore.

      That's such bullshit. Pure PR. So MS releases a new version of their software which breaks other applications (no surprise there) and they get to claim it's because it's more SECURE?!? And you BUY this?

    15. Re:Credit Where Due by Gonzoman · · Score: 1

      Remember that even Windows 95/98 were never designed to be networked operating systems except as a sort or add on. They were single user operating systems in the legacy of MSDOS and the previous Windows addons to DOS. Remember that Bill Gates thought the Internet was just a fad.

      I don't hate Microsoft. Fixing the inevitable results of people running their software has given me a good living. You will forgive me if I don't use their products myself?

    16. Re:Credit Where Due by Anonymous Coward · · Score: 0

      Yes we buy it because some of us have actually used it enough to know what we are talking about you fucking stupid ass fungus.

      Some of the things different about Windows Server 2003 are 1) no extra services installed by default, 2) more stringent file permissions for users by default, 3) default security settings for IE set to high (ie. no ActiveX and scripting enabled), 4) default security template locks down more "features", 5) IIS completely rewritten.

      This is not PR bullshit. It is obvious to anyone that has tested Win2k3 that it is much more secure out of the box than previous MS operating systems, and is more secure by default than some Linux distros.

      And it was the IIS rewrite that broke some existing applications because they relied on insecure "features" of the previous version of IIS. Even some of Microsoft's own applications won't work with the new version of IIS and will need to be rewritten. This is a good thing. This is exactly what many knowledgeable posters here have been saying that MS needs to do if they are serious about fixing their problems. Now we have to listen to a small minded, small dicked little peckerhead like you who decided to come out his cage just to get in on the obligatory MS bashing.

      Why don't you go back to playing with your dinky little computer in your parent's basement and leave the posting to the more knowledgeable users.

    17. Re:Credit Where Due by Black+Copter+Control · · Score: 1
      Remember that even Windows 95/98 were never designed to be networked operating systems except as a sort or add on. They were single user operating systems in the legacy of MSDOS and the previous Windows addons to DOS. Remember that Bill Gates thought the Internet was just a fad.

      95 may not have been designed for the world wide web, but it was definitely designed to handle networking. It was pretty clear by then that networking was catching on. It had started with 3.1wfw and 95 had networking built in.

      It was only the World Wide Web that seemed like it was going to be a fad (having only been about 2-3 years old, by then)

      I don't hate Microsoft. Fixing the inevitable results of people running their software has given me a good living. You will forgive me if I don't use their products myself?

      Yeah. that's part of my theory about why DOS/Windows caught on instead of Mac. MS required more people to support it per user than the MAC did (by about a factor of 5 according to some surveys). This meant that -- even if the market was 50/50 there'd be about 5 times as many DOS consultants as MAC consultants. As a result, joe blow coming off the street and looking for a consultant (any consultant) to get him/her into the computing world was far more likely to find a DOS/Windows consultant than a MAC consultant.

      In other words (if my theory is accurate) Microsoft beat out Apple in part because they had shitty software -- not in spite of it.

      --
      OS Software is like love: The best way to make it grow is to give it away.
    18. Re:Credit Where Due by rifter · · Score: 1

      To bad Larry's claims of being Unbreakable? were squashed.

      erm.. that was the poster's point...

    19. Re:Credit Where Due by rifter · · Score: 1

      That's such bullshit. Pure PR. So MS releases a new version of their software which breaks other applications (no surprise there) and they get to claim it's because it's more SECURE?!? And you BUY this?

      Why not? If applications rely on lax security to work, they will be broken when security is made tighter. That is a simple fact. Likewise, users can do less things in more secure environments specifically because making the environment more secure requires telling the user no sometimes.

      In the MS world, programming to rely on bugs, undocumented features, and security flaws has always been rampant. MS did a good job of getting everybody and their brother to develop for their platform, but that also meant getting a lot of bad programmers. Unfortunately, rather than design the OS to prevent bad programs from compromising security, they have continually allowed bugs and security flaws to remain where application developers relied on them. If they do otherwise, they get the problem of being told they are "breaking compatability with competitors."

      Theo and Linus do not have this problem. They can break compatability anytime they feel like and say "tough noogies, you were writing it wrong anyway" or "well we had to change this to end up with a better kernel. rewrite your code like the rest of us are having to." Personally, I think Microsoft should have stopped this practice back in the bad old days when it started. They also should have learned themselves to write better code and used some of the pull they gained with universities to see that future coders learned the right way as well. They claim to be learning this at last; we shall see if that is true.

    20. Re:Credit Where Due by d3faultus3r · · Score: 1

      Wait so we're paying 100's of $ for buggy software and you expect us to pay 1000's for actually working software when we can get Linux for next to nothing. Microsoft won't change its ways until it sees that it is absolutely necessary for the companies survival

      --
      read my blog
      musings on politics and technol
  46. Re:Port to Java! by DShard · · Score: 1

    Java came out of it's shell a few years back and decided it wanted to be an enterprise platform. J2EE has the enviable position of being a cohesive framework that is highly portable and covers large swaths of business computing. This is a Good Thing.

    Microsoft liked this idea and saw the benifits of an abstracted enterprise vm and came out .NET. To compete with java, they released the specifications for the vm and additionaly a c++/java hybrid called c#.

    Now, I don't know everything about your programming situation, but I can tell you that regardless of what you think, some of the largest software capitalists in the world believe in all the above technologies. The all plan on make large dollars off it. Perl cannot do this. PHP can't do this. C can't do this. (actually all of them could but they won't)

  47. Linux by tmark · · Score: 1, Flamebait

    Microsoft is a long way from its ultimate goal where users can take security for granted in its products

    For that matter, Linux is far away from this goal as well. It just doesn't give people as much chauvinistic pleasure to trumpet it. From the glee and sarcasm in the early replies, you'd think Linux is unexploitable.

    And many people have pointed out that while the majority of exploits have been directed at Windows machines, there are a lot more Windows users than anything else.

    1. Re:Linux by Anonymous Coward · · Score: 0

      I recall an article a year or so back where it showed the number of attacks targetting linux was rising much faster than the number against Windows - the explanation was that Linux was becoming more mainstream, and so more prominent in the minds of hackers.

      Also, don't forget 7 out of the top 10 internet security holes are unix based.

      Criticise MS all you want, but the more Linux becomes popular, the more it'll be tarred with the same brush.

    2. Re:Linux by arvindn · · Score: 1
      And many people have pointed out that while the majority of exploits have been directed at Windows machines, there are a lot more Windows users than anything else.

      Oh c'mon. This is one horse that's been flogged on /. a million times already. Most attacks aren't directed at desktop users (though those are the ones that get the most publicity) but at servers. And that's one market which MS certainly doesn't dominate. Why are there still far more attacks directed at MS products? Do you really think the frequency and severity of exploits of (say) IIS and apache are comparable? (Note that apache has more than twice the market share as IIS.)

      If you're claiming that most attackers are on windows machines, that's not true either. If you have the technical sophistication to author buffer overflow exploits, it's pretty likely that you've played with linux at some point. Go read phrack , for instance, and see for yourself.

      The reason OSS is more secure is that (if it needs any repeating):

      • Since everyone can look at the source the good guys are far likelier to find any given bug before the bad guys and a patch is usually out before there's an exploit
      • The Unix design is simply a lot cleaner and security conscious, period.
    3. Re:Linux by PhxBlue · · Score: 1

      On the other hand, most servers on the 'Net run Apache; but most servers that are compromised via software bugs are Microsoft IIS servers. Go figure.

      --
      !#@%*)anks for hanging up the phone, dear.
  48. None of this matters... by bargonzo · · Score: 1

    because it's the fox guarding the hen house. When I use Microsoft Software, the group that I most need security protection against is Microsoft Software!

    Until Microsoft establishes a fiduciary relationship with the user instead of corporate america, nothing will change.

    It's Microsoft that is recording what videos I watch, embedding undisclosed personal information in my word documents and allowing anyone and everyone to track me through their media player, etc. It's a full time career just trying to protect onself from these intrusions.

  49. Oh so this is the by Anonymous Coward · · Score: 0

    backdoor installation and upgrading team.
    Great! There was a real mess with all the backdoors introduced with every new Windows Update, and the exploiters would spend an awful amount of time and money each time to log in and at the same time use the most user-friendly backdoor.

    Great work. Thanks.

  50. Re:Port to Java! by GigsVT · · Score: 2, Interesting

    I think you forgot to add this:

    and everything works perfectly*.

    *Perfectly is taken to mean "Works about right as long as that system has the same brand and minor revision of the JRE"

    Seriously though, every Java based piece of software we have looked at has been total crap. Many of them require a certain runtime, such as one web service from a major company we looked at, that only works with Apple's runtime. Other's only work with MS Java runtimes. The list goes on.

    --
    I've had enough abrasive sigs. Kittens are cute and fuzzy.
  51. Bill to guy with mop... by Sfing_ter · · Score: 1

    Ya wanna raise?

    Most likely they are renameing another group, or creating a new "Standard" on their own, by making oh lets say the Janitorial department the new "Code Cleaning" group.

    I feel PsyCops scanning my mind. :)

    --
    A computer once beat me at chess, but it was no match for me at kick boxing. Emo Philips
  52. I am part of this group.. by cOdEgUru · · Score: 1

    But my Project Manager wasnt amused when I sent him empty source files after cleaning up!

    1. Re:I am part of this group.. by Anonymous Coward · · Score: 0

      you = teh slashdot funny.

  53. *looks out window* by Luveno · · Score: 1

    *sees pigs flying*

  54. hmmm... by stinky+wizzleteats · · Score: 1

    Microsoft is a long way from its ultimate goal where users can take security for granted in its products

    Oh, yeah - that dude is so fired. This is sort of like that moment during the 98 demo that the scanner blue screened the computer while Bill Gates himself was doing a presentation. He had the gall to say "I guess that's why it hasn't been released yet."

    I couldn't get over the feeling of how surreal it was to imagine Bill Gates having a single thought about product quality, much less expressing that thought in words.

  55. No kidding! by ackthpt · · Score: 5, Funny
    more of the same lip service from our friends at Redmond. is this the 3rd, or 4th 'security' initiative?

    NEWSFLASH!: Microsoft invents quality control! source code reveiw measures, internal cooperation among units, standardized enterprise wide security measures! Patents soon to follow!

    It certainly makes me wonder what the hell they've been doing all these years, besides making gigantic amounts of profit...

    Oh... right, less money on development costs == more profits. Now I see why Steve Ballmer and Bill have been selling off so much stock.

    --

    A feeling of having made the same mistake before: Deja Foobar
    1. Re:No kidding! by dthable · · Score: 3, Insightful

      I don't think it's as simple as the amount of money on development costs. Microsoft is going through the transformation from a programming shop (with loose standards and shoot from the hip developers) to a true software engineering shop (many standards, well thought out ideas and calculated coding). It's a tough transformation, but the code will be better in the end.

    2. Re:No kidding! by ackthpt · · Score: 2, Insightful
      I don't think it's as simple as the amount of money on development costs. Microsoft is going through the transformation from a programming shop (with loose standards and shoot from the hip developers) to a true software engineering shop (many standards, well thought out ideas and calculated coding). It's a tough transformation, but the code will be better in the end.

      Perhaps, but I have this nagging feeling that a company that does software should have been more focused on quality and security from the beginning. What they're doing now is expending the effort that should have been there all along. It's like all their code was written with some starry-eyed optimism that noone would ever think to misuse it or exploit lax security. Kinda like an automaker who builds a cars that can go 100 mph but has not seatbelts, no airbags and brakes that ask if you're sure you really want to hit them, under the knowledge that it runs and the assumptions that you'd never speed or drive recklessly.

      It really is the R&D cost they're talking about putting in over the next 10-15 years before , by their own admission, the code should be totally secure and trustworthy. What other industry, besides perhaps tobacco, could get away with something as audacious as that? Last, the staggeringly amazing thing is, people seem fine with that. Cripes!

      --

      A feeling of having made the same mistake before: Deja Foobar
    3. Re:No kidding! by dthable · · Score: 4, Insightful

      What other industry, besides perhaps tobacco, could get away with something as audacious as that?

      Not to mention the frequent crashing, loss of data, forced upgrade cycles, etc.

      Last, the staggeringly amazing thing is, people seem fine with that. Cripes!

      Exactly. No one wants a single thing to go wrong with their car or telephone, but the software we use is acceptable. It's funny/scary to see how many people actually accept and think it's fine to reboot their PC every hour.

    4. Re:No kidding! by Pfhreakaz0id · · Score: 1

      ... you mean all that stuff no one does, but everyone says you should? I've been a programmer 9 years and never had a code review.

    5. Re:No kidding! by jafac · · Score: 1

      Apparently, the guys who invented CMM weren't privy to the awful realities of running an actual Software Development business.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    6. Re:No kidding! by Anonymous Coward · · Score: 0

      CMM is about development methods that produce good software. Software vendors have mostly found that their customers don't actually demand good software--they've ignored things like CMM because producing bad software is much cheaper and thus more profitable.

  56. Yeah, right. by vadim_t · · Score: 1

    Security can't be just added like that to a product. Security is not a state, it's a process, and has to be had in mind right from the beginning. Closing a few buffer overruns won't magically make Windows safe. There are other kinds of security problems, and I'm pretty sure there's a good number of them that exist due to the design of the API itself.

  57. I'm telling you again - Hire Theo. by TerryAtWork · · Score: 5, Interesting

    What Bill should do is contract Theo de Raadt of OpenBSD. He has to be one of the lord high masters of code cleanup in the whole world.

    Pay boffo bucks, send a Gulfstream to get him and give him some Bill face time.

    He'll give you a seminar on code cleaning you'll never forget.

    --
    It's Christmas everyday with BitTorrent.
    1. Re:I'm telling you again - Hire Theo. by Daniel+Phillips · · Score: 3, Funny

      What Bill should do is contract Theo de Raadt of OpenBSD. He has to be one of the lord high masters of code cleanup in the whole world. Pay boffo bucks, send a Gulfstream to get him and give him some Bill face time.

      Knowing Theo, he'd tell billg to get stuffed.

      --
      Have you got your LWN subscription yet?
  58. Suddenly it all makes sense now by TheConfusedOne · · Score: 2, Funny

    1) UNIX IP License.
    2) Plan to clean up code.

    All they have to do is start swapping files. :-D

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
  59. Observation... by killermal · · Score: 1

    Shouldnt the most extensive security possible come as standard?

  60. Mod Parent Up - 5: Right On! by goldspider · · Score: 1
    I thought this site is supposed to be about the promotion of open source software, and educating the public on its benefits over closed source commercial software. I thought I would come to this site finding compelling information that would convince me to switch to open source software.

    Instead, we rarely see anything but attacks on the competition, and hypocritical attacks at that. Microsoft and Intel are bad, but Apple and AMD are good.

    Seldom have I read anything here that suggests why I should consider using open source software. All I hear is why select blacklisted companies are bad. I am dubious of anyone who favors relentless attacks on the competition over honest self-promotion.

    --
    "Ask not what your country can do for you." --John F. Kennedy
    1. Re:Mod Parent Up - 5: Right On! by stinky+wizzleteats · · Score: 1

      I thought this site is supposed to be about the promotion of open source software, and educating the public on its benefits over closed source commercial software.

      Uh, no. It's news for nerds. RTFWS

      I thought I would come to this site finding compelling information that would convince me to switch to open source software.

      Oh, I am aquiver at the very thought of proselytizing you!

      Instead, we rarely see anything but attacks on the competition, and hypocritical attacks at that.

      Dude, I see everything around here. Including some stuff I wish I hadn't seen.

      Seldom have I read anything here that suggests why I should consider using open source software.

      Would you like some tea?

      I am dubious of anyone who favors relentless attacks on the competition over honest self-promotion.

      I am a changed man. Here i was, all this time, dubious of Microsoft for all the wrong reasons. But if their honest self-promotion was enough to win you over, then certainly, it is enough to change my life. Do I get to fly around now?
    2. Re:Mod Parent Up - 5: Right On! by goldspider · · Score: 1
      "Dude, I see everything around here. Including some stuff I wish I hadn't seen."

      Point WELL taken, but I have yet to see michael drop a goatse landmine in an article summary... yet.

      "But if their honest self-promotion was enough to win you over, then certainly, it is enough to change my life."

      I never suggested Microsoft was an honest company, but just about anything is better than "Use Linux, because it's not Windows, and as we ALL KNOW, Windows and anything else Microsoft makes is bad!"

      --
      "Ask not what your country can do for you." --John F. Kennedy
  61. Have they not realised... by Benjim · · Score: 1

    ...that you use an open-source alternative, and not have to take "security for granted"!!

  62. Do you think they might reduce bloat... by djeaux · · Score: 1

    ... at the same time they make their products more "secure"? Well, I guess the 2nd part of my question answered the first -- ain't neither one gonna happen...

    --
    "Obviously, I'm not an IBM computer any more than I'm an ashtray" (Bob Dylan)
  63. Manpower? More MS myth tossing by djupedal · · Score: 3, Interesting

    MS employs a staff that roughly equals 20% of GE. And the bulk is either in marketing or legal. Factor out these yocals, mid-level managers doing nothing but CYA and all the air-head interns and there's not much left. There's your 'task force,' working on this whitewashing.

    What is Microsoft's full-time worldwide headcount? Current employment headcount as of 6/30/02: Worldwide: 50, 030

    GE operates in more than 100 countries and employs 313,000 people worldwide. Now, that's manpower. Anything under 250,000 is just an excuse to have vending machines in the lobby.

    1. Re:Manpower? More MS myth tossing by zero_offset · · Score: 1

      The bulk of their headcount is in programming, and always has been. MS currently employs roughly 13,000 programmers. Furthermore, very, very few companies employ your magic figure of 250K+ people -- not that the number appears to be relevant to anything. You don't appear to make any point very clearly in your post, but you seem to believe that merely having a lot of employees means something good will happen. I fail to see the connection.

      --

      Slashdot quality declines as the number of hot grits posts decreases. - Provolt's Law, Apr-09-2005

  64. April Fools? by allism · · Score: 1

    This is a delayed April Fools joke, right? Someone forgot to check a date on a submission or something? When would the director of MS security actually admit something like "Microsoft has bunches of bugs"?

    1. Re:April Fools? by Anonymous Coward · · Score: 0

      Because he didn't. The article has been misquoted.

      It was Litchfield, not Lipner, who is attributed as saying that "Microsoft is a long way from its ultimate goal where users can take security for granted in its products".

  65. Re:Brainwave at Microsoft.. by jkrise · · Score: 0, Funny

    The Code Cleaning group has come up with a brillinat idea! Instead of releasing buggy code and fixing it with Service Packs later, the new technique is to release Service Packs first... typically in the form of leaks. Once this is done, then the 'previous' versions are leaked. After a while, the code reaches the users.

    This way, users are sure to get fully patched OSes from day one. Similar strategies are being adopted by anti-virus s/w writers as well.

    --
    If you keep throwing chairs, one day you'll break windows....
  66. And in other news... by Grell · · Score: 1

    Sisyphus to push rock up Hill.

    "Job needs to be done, and I project an early strong effort should complete this onerous but necessary task" states Sisyphus.

    G.
    OH I feel for the progress report writer for that group...

    --
    ...when it gets down to fundamentals, do what you have to do and shed no tears. Dr. Matson in Tunnel in the Sky
  67. Re:Port to Java! by Anonymous Coward · · Score: 0
    every Java based piece of software we have looked at has been total crap
    Why don't you look at some decent Java software, then? Start with the greatest IDE known to Man, IntelliJ IDEA.
  68. Of course you know.... by interactive_civilian · · Score: 1
    The name of the game is simply Duke Nukem and is just an upgrade to the previous game w/ the same title (they will change the version number and include new maps).

    Forever is the release date.

    ;-)

    --
    "Empathise with stupidity, and you're halfway to thinking like an idiot." - Iain M. Banks
  69. Re:Port to Java! by Anonymous Coward · · Score: 2, Insightful

    some of the largest software capitalists in the world believe in all the above technologies

    Coorporations believe in a lot of things, and miss a lot of other things in doing so.

    In the early 90's, everyone expected Unix to collapse and NT to take over the server market. A decade later, Unix market share has grown via. Linux and NT is in the minority on the web.

    Microsoft believed in MSN and almost completely missed the Internet revolution.

    Sun believed in NeWs and X stomped it into the ground.

    Sun also believed in JINI. Remember that? I doubt you do.

    Microsoft believed in Passport & Hailstrom, then scaled back their plans, then buried most of it.

    Now Sun believed in Java and Microsoft believes in .NET Big whoop. Call me back in three years and we'll see who believes what then.

    By the way, do you remember what .NET was originally supposed to do? Microsoft took a very long time before even they could decide what .NET actually was. They manged to be believe in something that didn't even exist..

  70. But it IS important by Obiwan+Kenobi · · Score: 4, Insightful

    Firstly, filter it if you don't like it.

    Secondly, I believe it's very important to keep track of any and all movments of the biggest, richest, most powerful company in the world.

    Of the company that controls 95% of the desktop market that Linux might, hopefully, break into.

    If they're looking into new strategies, even ones that are years behind their time, we should know about it. When you only look at yourself, you'll sometimes see innovation or monopolism take over while you're busy staring at your shoes.

    A company with such terrible operating practices should be watched closer than any other company, and I'm all for it.

    Despite your obvious trolling, I will agree that it might seem a bit much, but I'll tell you, I'm glad we're looking too hard, than not looking hard enough.

    I wait for these same comments about the SCO case in a few days.

    1. Re:But it IS important by Pave+Low · · Score: 1

      Firstly, filter it if you don't like it.

      I love how the same people decrying internet filters and censorship would suggest that I apply it to myself simply because I don't agree with their viewpoints.

      Secondly, I believe it's very important to keep track of any and all movments of the biggest, richest, most powerful company in the world.

      Seriously..get over yourself. It sounds like you're the same psycho nerd who stalked and hated the hot girl in school simply because you couldn't get her.

      Despite your obvious trolling, ...

      On slashdot, anybody who doesn't toe the party line MUST a troll.

      --
      SIG:Slashdot: indymedia for nerds.
    2. Re:But it IS important by Anonymous Coward · · Score: 0
      "Seriously..get over yourself. It sounds like you're the same psycho nerd who stalked and hated the hot girl in school simply because you couldn't get her."

      For the record, ad hominem attacks are not a respected debate technique. Let's try again, but this time with logic, mkay?

    3. Re:But it IS important by hellfire · · Score: 1

      Firstly, filter it if you don't like it.

      Hear, hear. I second this whole-heartedly.

      If you would like a testimonial, my enjoyment of Slashdot skyrocketed when I filtered out all articles written by JonKatz. :)

      --

      "All great wisdom is contained in .signature files"

    4. Re:But it IS important by bier · · Score: 2, Interesting
      I agree, it IS important. Not the bashing, although it is fun sometimes, but rather the fact that this OS non-corporation called Linux is managed, marketed, funded, researched and developed by people like us.

      The mucky-mucks at MS, or Apple, or any other software company work long days worrying about and getting all the info they can about other companies.

      Since linux is non-corporate it is up to people like us to discuss, argue, trash-talk, and otherwise beat to death information and news about the competition.

      To me its just good business.

    5. Re:But it IS important by Anonymous Coward · · Score: 0

      the biggest, richest, most powerful company in the world.

      Biggest, richest, maybe, I don't know, but "most powerful"... only to a geek. For an ordinary person, your local TV station (or any of the local advertising agencies) is infinitely more powerful.

      (Discounting MS XBOX and PC games, where MS gets to put content, not just the medium.)

    6. Re:But it IS important by Anonymous Coward · · Score: 0

      I love how the same people decrying internet filters and censorship would suggest that I apply it to myself simply because I don't agree with their viewpoints.

      I thought you were complaining about the frequency of MS stories posted here. If you feel that not reading stories about MS is somehow censorship, I give you two years before your head explodes.

    7. Re:But it IS important by Trolling4Dollars · · Score: 1
      On slashdot, anybody who doesn't toe the party line MUST a troll.

      Is that a new sexual practice? ;P

      Seriously. A troll is someone who says something because they want a specific response. Typically it's calculated to agitate the largest number of people possible into a negative response. Given that MOST Slashdot readers are fans of *nix, your comments certainly will get a negative response. Assuming you are a regular reader of Slashdot, you would know this. Given those two assumptions, you willingly wrote something that you knew would agitate a negative response. Based on the definition of trolling, you WERE trolling. Welcome to the club dude. Troll on... :) BTW, I am not a troll despite what my Slashdot username might lead you to think.

  71. Can you spell political? by borkus · · Score: 1

    Let's see - You're a code reviewer for the M$ Code Cleanup crew. Windows 2005 is rolling through developement and you find a security issue that'll add a man-month to the project. What kind of pressure will you encounter from Microsoft's marketing department?

    1. Re:Can you spell political? by Anonymous Coward · · Score: 1, Insightful

      I have worked for Microsoft for several years.
      The marketing department is never decides when a product is to be shipped.

      What Microsoft needs is a overhaul of its testing procedures.
      Testing compatability with MS' own and partner products takes a huge amount of hardware and manpower resources.
      Its a tough problem to solve.
      This new group will be one additional layer on top of 3 or 4 layers of testing/reviewing which some groups already have.

    2. Re:Can you spell political? by maxume · · Score: 1

      So that man month would ammount to what, ~2 hours?

      Or would it be even less than that?

      --
      Nerd rage is the funniest rage.
  72. what does MS mean by "security" by walterbyrd · · Score: 1

    Don't forget, when MS speaks of security, they often mean their own security. For example, users not being able to transfer the OS from one PC to another.

  73. MS might get better than open source by mandreiana · · Score: 1
    What many people forget (and still think that MS sucks at programming) are the huge resources they have. They could always hire people not only to implement features, but to do auditing, code cleanup, API documentation, testing, things which are missing from a lot of OSS development.

    Instead, OSS developers do what they like and don't cooperate. I can't blaim them for this, I'm very gratefull for the libre software they write for free, but without cooperation MS will win.

    See the Too Much Free Software article (and it's comments). There are a lot of examples of programming hours which could be better used ( latest one: ephiphany vs. galeon )

    1. Re:MS might get better than open source by Tsu+Dho+Nimh · · Score: 1
      "They could always hire people not only to implement features, but to do auditing, code cleanup, API documentation, testing, things which are missing from a lot of OSS development."

      They DO have such people. The problem is that the company is driven by marketing-oriented management, with one eye on the stock price and the other on the market share. Marketing (short-term ones at that)can overrule any other department. When security or bug fixing gets in the way of release dates and sales it's like a Yugo in the way of a freight train.

  74. Target: Microsoft by christurkel · · Score: 1

    I hate M$ as much as the next guy but being the biggest software company and a monopoly makes you a juicy target for hackers. Yes, they have security problems, but also remember, they are under assault constantly from wannabes and script kiddies.

    --

    CDE open sourced! https://sourceforge.net/projects/cdesktopenv/
  75. Re:GROW UP!!! by Anonymous Coward · · Score: 1, Insightful
    Sorry, but the "the image of professionals" bullshit is why people bang on with such hatred against Large Multinationals - eg Microsoft. It's all the perception that Flash Image = Good. It's BOLLOCKS and it makes me seethe. Roll on the next wave of PCism, when Imagism is a crime. And don't send me any more "Engineers" in suits who won't crawl around under floors to fix faults!!

    /rant

  76. Is it any suprise? by ClubStew · · Score: 1

    They're a company with probably the most products and services in the world that also integrate with each other and other products more than any other, and are far more extensible! So, whoopty-f'in-do to your little 1000-line, "bug-free" linux script that does something that 100 scripts already do and doesn't integrate with anything!

  77. Just another day, the Microsoft way! by Anonymous Coward · · Score: 0

    Yup, and what about these here!

  78. Virus on windows? Yes because it is dominant!! by Anonymous Coward · · Score: 0

    the majority of viruses written attack Microsoft products.

    That is because it is the predominant format, there would be a lot more virus's for unix if it was adopted more. You can write a virus for any OS. Personally if I was going to write a virus, wouldn't I want to distribute it to the masses? You won't find me doing that with BeOS for instance, relatively few people use it in the grand scheme of things.

  79. All together now... by Anonymous Coward · · Score: 0

    "Microsoft code... so fresh and so clean!"

  80. Late breaking story... by Qui-Gon · · Score: 1

    This just in... Microsoft is attempting to catch up to the rest of the world. Full story at 11.

    --

    We are blind to the Worlds within us
    waiting to be born...
  81. A good thing by DrTentacle · · Score: 5, Insightful

    Obviously, MS bashing abounds, but I view this as a good thing.

    Working in an environment that is purely MS based on the desktop, with significant MS server infrastructure, I can only applaud any efforts they are making to clear up the mess that is obviously present. No, it's not going to happen overnight - Just as the company I work for is not going to replace all it's investment in MS tech overnight.

    Unfortunately, being a developer does not make you a security expert. Some are, others will continue to allow simple flaws, such as buffer overruns, into their code. Having a group of people who focus on security review that code is without a doubt a good thing. While this may not be the potentially rigorous code review that OSS gets, it's better what presently happens at MS.

    As for the issue of scapegoats...from an external point of view, getting MS to recognise bugs can be a difficult job at the best of times. Internally, if a group of security "experts" fail to recognise security flaws in a piece of code...then surely they are failing at their job?

    Finally, there's been a lot of flaming about the fact that this is yet-another-initiative from MS in the security field. I welcome all of them, in parallel, as moving towards sorting out some of the many issues they have. The less time I have to spend working on patching buggy MS software, the happier I will be.

    1. Re:A good thing by Anonymous Coward · · Score: 1, Interesting

      If true, than M$ has internalized, or is attempting to, another OSS development process feature into it's corporate structure.

      Even if it was just a flapping of the lips, it's a good thing, especially for all the shops in the IT world who take hints from the large players, which, like it or not, M$ is. I got a copy of "Code Complete" from M$ Press my first day on the job here. People do pay attention.

    2. Re:A good thing by dthable · · Score: 3, Interesting

      The concept pre-dates open source development. They did have peer reviews in the days of the mainframe.

    3. Re:A good thing by DrTentacle · · Score: 2, Interesting

      Sure, the concept of peer review is an old one. This is a slightly different slant, however - The security review is not to check that the code performs it's task correctly, rather that it does not compromise the security of the application.

      In the OSS community, code (potentially) gets reviewed by people with expertise in a number of fields, something that is not guaranteed in a closed-shop development team. Hence, my observation that this is a watered down version of that process, with it's focus solely on security.

    4. Re:A good thing by jpmorgan · · Score: 4, Insightful
      Potentially is such a weasler. Let's face it, how many projects actually get any sort of in depth review from a lot of people?

      The small projects aren't usually popular enough to attract sufficient attention. The big ones are too large an undertaking for anything but a cursory inspection which will only reveal the most blatant of security flaws; consider how long it's taken to find all the ptrace flaws in the linux kernel.

    5. Re:A good thing by Anonymous Coward · · Score: 0

      You're right. They should just not even try.

    6. Re:A good thing by maxpublic · · Score: 0

      And yet linux is still far more secure than Windows. Go figure.

      Max

      --
      My god carries a hammer. Your god died nailed to a tree. Any questions?
    7. Re:A good thing by DuctTape · · Score: 1
      Um, did you just put in your job application to Redmond? When's the interview?

      DT

      --
      Is this thing on? Hello?
    8. Re:A good thing by GreenBugsBunny · · Score: 1, Interesting

      That's because (for the most part, anyway) the developers are writing the software because they want to, so they're going to do it right. Closed-source shops have deadlines & developers will often take shortcuts to meet them.

    9. Re:A good thing by mystran · · Score: 2, Interesting
      Actually, this sound like a good idea to me. I think that it's actually better than any of their old Security Initiatives.

      Having some people to actually just fix security issues is good, since then those people can concentrate on security topics.

      Even if all their developers where aware of security issues, there actually has to be some group that concentrates on KNOWING about the issues, so that not only is code looked after, but actual developers have someone to ask when they think "there is potential pitfall here" but don't know the exact problem/solution.

      I think Open Source security works because there is always someone that can show the actual problem with the code.

      There's also the problem of big picture. While you COULD check buffers at every stage of code, you actually only need to check data that is coming INTO your code, as long as you trust your own code. Problem here is that there is often functions that SHOULD get data only after it's validated, but for some reason get it without validation. If there's someone who knows the actual validation process and data flow, and whose job is to check that all is fine, then security can be built as the first layer, not just small checks in 11001 places.

      Ofcourse everyone still needs to check return values of functions that can fail (or catch exceptions when programming with a sane language).

      --
      Software should be free as in speech, but if we also get some free beer, all the better.
    10. Re:A good thing by Alsee · · Score: 4, Insightful

      Obviously, MS bashing abounds, but I view this as a good thing.

      The problem is that as far as Microsoft is concerned "security" is a synonym for "DRM".

      Whenever Microsoft talks about security, one always has to wonder how much of what they are doing actually means securing the machine against outside attackers (a good thing), and how much of it means securing the machine against it's owner (a bad thing).

      The article makes refferences to things like "Trustworthy Computing" and "Next Generation Security". Both of which actually mean "DRM enforcment".

      "Normal" computers cannot be adaquately secured against their owners. As far as Microsoft is concerned this is a "security flaw". Microsoft intends to "fix" this "flaw" by introducing new and crippled computers.

      The article says Microsoft's "ultimate goal being that customers will take security for granted". Do you really think they mean that people will take it for granted that Microsoft software is bug free?? Or do they mean that their DRM mechanisms will be an "invisible", integrated, and omni-present part of using a computer?

      They want you to take it for granted that the computer is invisibly and seamlessly enforcing DRM restrictions when you read your E-mail or surf the web. People are not supposed to notice that the option to "save image" has dissapeared from the menu when you right-click an image in the browser. Not only is that option gone, but the computer is phyically incapable of saving that image. The image is copyrighted of course, and wrapped in DRM. If people never see the DRM, they will just take it for granted when various options vanish, or other things become mandatory.

      If Microsoft is cleaning up their code, then yes, this is a good thing. But a careful reading of the article suggest that this is at best a mixed project. And that is not a good thing.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    11. Re:A good thing by afidel · · Score: 1

      The entire core of the openbsd system gets reviewed for security, and consequently the only remote exploit in years was a flaw in openssh. I'd say that's a large project that gets more than a cursory review!

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    12. Re:A good thing by spongman · · Score: 1

      Indeed, but be careful not to extend this argument to imply that the number of bugs that exist in a system is proportional to the number of bugs that are found in a system over a given time. There are many other factors, not least of which is the number of people looking for those bugs.

    13. Re:A good thing by Anonymous Coward · · Score: 0
      What about KDE? They've recently had a security audit. And it has nearly as many lines of code (2.6 million) as the linux kernel (3.1 million). Look at the bottom of the KDE Project Overview Page for more information.

      Granted there weren't tons of developers reviewing KDE, but it was the core developers. The people who know the code the best. How is that not a security audit on a large open source project?

    14. Re:A good thing by hetairoi · · Score: 1

      Obviously, MS bashing abounds, but I view this as a good thing.

      I think most /.er's would agree that MS bashing is a good thing ;)

      --
      you're all figments of my deranged imagination
    15. Re:A good thing by Anonymous Coward · · Score: 0
      In the OSS community, code (potentially) gets reviewed by people with expertise in a...

      'Potentially'... 'Potentially' I can get laid today, but that's rather unlikely. Same with random OSS code reviews. Potentially you have many eyes looking for bugs, but in reality only select few projects get the treatment.

    16. Re:A good thing by Anonymous Coward · · Score: 0

      just because a system is used by less people overall doesnt mean that the system is just as flawed as a high circulation system and that this isnt apparent because less people use it.

      this is a typical rant of microsoft zealots. but things from defense systems to flight control computers to many other things put in mission crticial roles typically have far less bugs - particularly catastophic ones, per unit of population.

      just because more people use it doesnt excuse bad programming. sorry.

      if my life was on the line, i would rest far easier knowing that microsoft or linux WASNT involved in a system where my safety would be a stake.

    17. Re:A good thing by spongman · · Score: 1

      I said nothing about the number of people using the system. I only mentioned the number of people looking for bugs. So, once again, what you said has absolutely no relevance to the discussion.

    18. Re:A good thing by rifter · · Score: 1

      The concept pre-dates open source development. They did have peer reviews in the days of the mainframe.

      This was before my time, but I had understood that during the mainframe days people did share code with one another. There are some who would claim code was always shared until the day Microsoft invented "piracy" (starting with the nasty letter Bill Gates wrote the Home Brew Computer Club for copying the paper tape of the MS Basic Interpreter for Altair), though I would imagine it is not so cut and dried as all that. Still old timers have claimed on the net that mainframe programmers regularly shared code back in the day. Isn't that what open source development is about? Is this story apocryphal?

    19. Re:A good thing by Anonymous Coward · · Score: 0
      The security review is not to check that the code performs it's task correctly, rather that it does not compromise the security of the application.

      I always assume not compromising security is part of performing a task correctly. That danger is from people who they are different.

    20. Re:A good thing by Anonymous Coward · · Score: 0

      Once again, you try and re-invent reality and effectivly come up with reasons for justyfying your evil acts.

      You whole vicarious life here is effectivly a drool cup for Microsoft rhetoric. You are a brainwashed halfwit with no job. You live at home and are dependant for autoeroticism for any sexual outlet.

      Nothing you say is technically relavent. You always simply regurgitate "sources." Links simply prove you browse the web, or know how to google. But you are not an implementer. You have never implemented or delivered.

  82. Re:Port to Java! by buckinm · · Score: 3, Informative

    *Perfectly is taken to mean "Works about right as long as that system has the same brand and minor revision of the JRE"

    Nope, don't think so... I develop on 1.4.1, and my stuff runs fine on 1.2.2 and up.

    --
    This isn't any ordinary darkness. It's advanced darkness.
  83. Code clean-up could spell trouble by tundog · · Score: 1

    If you really want to make your code secure, you have to do it before the Geni is out of the bottle. This means longer coding cycles, development times and QA processes. How many of us have written some code that worked, thought about it over night and decided that we would like to refactor it but just didn't have the time due to development cycles?

    Clean-up is a real tricky thing. The main problem is that every time you 'clean-up' a line of code, you are potentially throwing out a bug fix. Clean up too much code (throw out a single bug fix) and you open yourself up to more security problems (majority of all 'attacks' result from buffer over/under-runs)

    --
    All your base are belong to us!
  84. Gotta do a LOTR thang.... by Himring · · Score: 0

    "SCO: The hour is later than you think - Microsoft's forces are already moving. The nine have left Redmond.

    OSS: The Nine?

    SCO: They crossed the River Columbia on Midsummer's Eve, disguised as Riders in Black.

    OSS: They've reached the Shire!

    SCO: They will find the source code, and KILL the one who carries it!

    OSS: Linux!

    SCO: You did not seriously think that free software could contend with the will of Microsoft. There are none who can. Against the power of Redmond, there can be no victory.

    We must join with him, OSS. We must join with Microsoft. It would be wise, my friend...

    OSS: Tell me, 'friend', when did SCO the Wise abandon reason for MADNESS!"

    --
    "All great things are simple & expressed in a single word: freedom, justice, honor, duty, mercy, hope." --Churchill
  85. This is good news. by Capt_Troy · · Score: 1

    Like it or not, Windows is improving all the time, just look at the leap in quality between Windows 98 and 2000 alone. This is a company that is doing some good stuff and getting their act together.

    I still use Linux for development, because it's a better platform for what I need to do. But I think it's a good thing that there may be difficult decisions in the future about what platform to use. If there is only one hands down winner, then who's driving the innovation. OSX, Linux, MS. All these have become very viable platofrms and users of each one are benifiting from the competition.

    Now if we could just get MS to compete on software quality and features alone instead of legal rangeling to rid itself of it's competitors. That whole SCO thing scares me a bit.

    Troy

    1. Re:This is good news. by Lochin+Rabbar · · Score: 1

      Like it or not, Windows is improving all the time, just look at the leap in quality between Windows 98 and 2000 alone. This is a company that is doing some good stuff and getting their act together.

      Don't you mean the huge leap in quality between Windows 98 and Windows ME, as if anyone could call ME a quality product. Windows 2000 replaced NT4 a derivitive of VMS, not DOS. 2000 may be reliable in Microsoft terms, but does it yet reach the standards that VMS users were used to? It's certainly not as secure.

    2. Re:This is good news. by Capt_Troy · · Score: 1


      Don't you mean the huge leap in quality between Windows 98 and Windows ME, as if anyone could call ME a quality product.


      No, I mean the huge leap in quality of all their products over time. ME sucked, but other than that I think there is a steady increase in quality in each product line. And I consider 2000 and XP to be in the same line as 98/ME since they are considered replacements.

    3. Re:This is good news. by Lochin+Rabbar · · Score: 1

      Fair enough, you take the marketing view of OS succession and I take the technical one. Though I would still argue that 2000 is not the successor to the DOS based windows. That accolade belongs to XP home edition which, although it is a big improvement on 98/ME, still sucks. However if you look at the improvement between NT4 and XP professional you would have to say the difference is not that huge, and I would suggest that is progression you should look at if you want to estimate the likely progress in the next version of windows.

    4. Re:This is good news. by Capt_Troy · · Score: 1

      Good point.

      I think the interesting comparison between OSs in the future is going to be how much freedom they allow you. With all the hype about the DRM in Longhorn, and incklings of it in OSX, and absolute freedom in Linux, it will be interesting to see if quality/stability becomes less importiant than the freedom to do what you want.

      Anyway, thanks!

  86. Just on paper by Tighe_L · · Score: 1

    When push comes to shove, Microsoft always chooses new features (interoperability) over security.

    This new group is just for properganda, to make it seem like they are working on the problem

    IF you tell a lie enough it becomes truth.

  87. Isn't it obvious? by Anonymous Coward · · Score: 0

    Windows need cleaning.

  88. That's just not possible by andr0meda · · Score: 1


    Last time I checked, they went baosting on the millions of lines of code that the OS and related products comprises. Code cleaning means spotting POSSIBLE semantic errors, refactoring classes, refactoring organisation, and quite possibly, totaly rewrite whole parts just because it was all wrong from the start. That's gonna be some long hours for a handfull of programmers if they have to do everything again, with the added danger to introduce new bugs or alternative behavior. Unless they have the behavior of every little teensy bit of code clearly documented, with exceptions, timing issues, every damn possible pre and post condition, this is barely something you can oversee (and even if you had that kind of information you'd probably drown in it).

    Most of all, additional security means additional cycles souped up. And introducing alternative code paths can potentially break an API.

    The fact that they even try this approach means that their top execs have no understanding what it is to write software. It is often times better to throw everything away (well, at close hand range anyway) and restart from scratch with all the new ideas and designs. But I guess good old 'backwards compatibility' has allways been the haunting ghost in SF-bay & Redmond.

    Cheers & eurocents,

    --
    With great power comes great electricity bills.
  89. Lost Backward Compatibility? by 4of12 · · Score: 1

    Code clean-up is always a great idea, just like programming with security in mind, programming with memory and CPU efficiency, with simplicity, etc.

    What I wonder is what will happen practically.

    Crufty code crawls in and out of so many wormholes that major clean-up is likely to result in big changes in functionality. I'd expect backward compatibility is likely to suffer.

    --
    "Provided by the management for your protection."
  90. The S.E.S.? by aaaurgh · · Score: 1

    Here in Oz the S.E.S. is the State Emergency Service - the people who tidy up the mess and damage after disasters occur.

    Hmm... sounds like they have similar agendas, except that ours tackle natural disasters which were not our own fault!

    --

    Go permanent? In your dreams and my worst nightmares.
  91. if this reduces the number of compromised machines by Anonymous Coward · · Score: 0

    I'll put up with their stupid PR stunts. Until then, I'm not holding my breath.

  92. sky outside is weird today.. by NeoCode · · Score: 1

    as I look outside my window this morning, I see something in the sky. Is it a bird? A plane?
    oh wait..
    its a flying pig.

  93. Don't Stow Thrones in Grass Houses by Detritus · · Score: 1

    The security record of most operating systems is pathetic, including both the commercial and open source categories. Even OpenBSD relies on auditing after the fact, not on designing with security in mind at the beginning. Have we learned nothing since the introduction of Multics in 1965? Multics had a higher security evaluation than whatever POS is currently running on your desktop.

    --
    Mea navis aericumbens anguillis abundat
    1. Re:Don't Stow Thrones in Grass Houses by ctid · · Score: 2, Insightful

      Multics didn't operate in today's environment, however. How would it have done if it was attached to the Internet? This isn't to knock Multics, about which I know precisely nothing. But a large part of the security landscape these days is the fact that J Random Hacker has the means to access your computer from a remote location all the time. Of course universities and the military were on the forerunner of the Internet in those days, but the number of people with access to a connection was miniscule compared to today.

      --
      Reality is defined by the maddest person in the room
  94. Taking for Granted... by somethinghollow · · Score: 1, Insightful

    Wasn't taking security for granted the problem in the first place? We see where that got Microsoft...

    I'd also like to point out (love 'em or hate 'em) what Bob X said about cleaning up code...

  95. Coming soon... by Anonymous Coward · · Score: 0

    M$oft has announced plans to push Longhorn back to 2006 . The company has decided to start from scratch and their latest OS will be based on the Linux kernel...

    1. Re:Coming soon... by Anonymous Coward · · Score: 0

      The 2.6 series kernel has been cancelled due to rampant code thievery. Apparently, tons of SCO/Caldera code was stolen by several dirty GNU hippies.

      Current plans for the Linux kernel are to replace the tainted Linux kernel with a more modular Windows CE kernel. XFree86 advocates insist that performance will "continue to be blazingly fast" on the new kernel.

  96. Not a Troll! by samael · · Score: 0

    How on earth is this a troll?

    The poster asked for debate - I responded with a point by point response to his post.

    And I get labelled a troll for not being anti-MS!

  97. No way... by twoslice · · Score: 1

    Microsoft has code cleaners mucking about with great regularity for some time now. Every MS security update introduces a slew of em...

    --

    From excellent karma to terible karma with a single +5 funny post...
  98. question: by DougMackensie · · Score: 1

    how do you clean up a pile of shit, without first dirty-ing your hands?

  99. And in other news... by ILuvUAmiga · · Score: 0

    Microsoft does no good by doing right, they dont do anything right, they are shit and evil.

    More later on Linux Daily.

  100. not think, DO by zogger · · Score: 2

    Saying they are going to do it and pulling it off are two completely different undertakings. Even throwing x-amount warm bodies and money at it is still quite the iffy proposition. If it was really that simple, they could pull a truckload of cash out of the bank and sprinkle it all over redmond from aeroplanes.

    It's gotten so bad with microsoft and "normal" joe users I have started to refuse all microsoft tech related "help me please" requests from people I know. One, is most of the time I really can't help them, fixes and problems are way beyond my interest or expertise any more, I just plain stopped even trying to use it. The second is--what's the point? Really, what's the point? Even if it was completely 100% "fixed"(I doubt at this time they can do it really) it would still be...just plain wrong, from my viewpoint on what software should be now and what it is for and what is the best for people and what legitimate business should be. I do not seperate money from ethics in my life. Note, that is merely my personal opinion on it, anyone on the planet can choose to still use and "support" them, I just choose not to, similar to a few other large corporations that I consider to have "crossed the line" into sophisticated international thuggery and criminality. I REALLY DO consider them to be an unethical and immoral company, and their products reflect that, again, IMO. I am sorry for the people who work there and aren't crooks or bad people, I am sure most of them are just fine regular old folks just trying to make a buck,and I am not trying to put them down or anything, but at this time that company and managerial and directorial mindset needs to be scattered to the winds of business history. At one time, and for many years, they were more or less fine, I didn't consider them the way I do now, but what has been revealed with them, and watching the evolution of their products and influence on all of our technological society has changed my opinion of them, and shows me it's just a big bully criminal gang now who happen to be in the software business. Same as any other gang out there, I am not concerned with "reforming or fixing" the mafia or it's "products" for example, even if a large part of the mafia now has morphed and is considered "legitimate business", they got there in the first place by being crooks and thugs whenever they could get away with it.

    It's sort of sad in a way, too, there is no joy or gloating over it from my viewpoint, it just is reality.

  101. Remember, Security is Job 1! by croftj · · Score: 2, Informative

    We've heard this before. Didn't they take a year and clean up all of thier code before? Are they going to take another year and do it again? How many years will this take any ways?

    In all reality, if they want to fix their security, they need to fix the way they view data and process. They blur the lines between the the two way too much. They also encourage the users to blur the line between the two as well.

    If they truely want to make a more secure OS, they need to remove the ability to run code from every form of document you cvan make with their code. Macros are nice but when they let you have full access to the system and it's resources they are deadly and the biggest security hole you can ask for!

    I should not be able to run full blown basic apps just by opening a word doc, email, spread sheet or whatever.

    --
    -- Many men would appreciate a woman's mind more if they could fondle it
  102. Taking Secuirty for Granted. by Inverarity · · Score: 3, Insightful

    As the director of MS security engineering says: 'Microsoft is a long way from its ultimate goal where users can take security for granted in its products...the majority of viruses written attack Microsoft products.'"

    Personally, I do not think that security should ever be taken for granted. I think it has been proven that this lax security awareness leads to problems independent of the software (e.g. stolen credit card numbers and identity theft from insecure websites and to a lesser extent the proliferation of spam). Most people do not take the locks on their front dor for granted, why should the computer be any different. Especially now that many individuals use the computer as the primary portal to the outside world.

  103. Re:Brainwave at Microsoft.. by smittyoneeach · · Score: 1

    However, the lower limit of this service pack/previous version approach will be Windows95.
    Ballmer says that the regression will stop short of reverting to 16 bit code, or his name is Adam Osbourne

    --
    Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
  104. BAHAHAHAHAAHAHAH!!! by rulethirty · · Score: 0

    LOL! :'D

  105. A code-cleaning group? by ihummel · · Score: 0, Flamebait

    I had no idea that Microsoft was prepared to completely rewrite their entire operating system from scratch. But since it says that they have instituted a group to clean up their code, that must be the case.

    1. Re:A code-cleaning group? by Anonymous Coward · · Score: 0

      Dudes, why would the above message get modded as flame-bait? M$ bashing is a way of life on /.

  106. Re:Port to Java! by b17bmbr · · Score: 1

    then ship the JRE with the app. geez, the JRE is redistributable. i might be wrong, but it is my understanding that a majority of java apps are written for internal consumption.

    --
    My problem? I was perfectly gruntled, until some numbnuts came by and dissed me.
  107. Nothing to see here. by Anonymous Coward · · Score: 0

    Move along.

  108. What was that name again? by janda · · Score: 2, Insightful

    According to the article, the new group will be called outa'sync (um, no, wrong article. Hang on. Ok). The new group will called the (drum roll, please):

    Security Engineering Strategy Team

    Anything group that has the word "strategy" in it will spend their time writing memos about how this piece of already written code could be better.

    These memos will then be ignored by everybody so they can meet their deadlines.

    --
    Karma: Food Fight (Mostly affected by Date Plate).
    1. Re:What was that name again? by cant_get_a_good_nick · · Score: 1

      Security Engineering Strategy Team

      I think Bush will lobby for calling it the Security Engineering Strategery Team, you know, kinda a payment for defanging the prosecution in the Antitrust Trial.

  109. Yeah, and they're... by Anonymous Coward · · Score: 0

    ...being shot out of an air cannon straight towards your face.

  110. odd timing. by s4m7 · · Score: 5, Insightful

    Here's something to worry about. Does the timing, that the U.S. Gov just instituted a new position for this (the cyber-security chief) which I have already commented on here, seem odd to anyone else?

    This looks remarkably like the same type of handwaving smoke and mirror show that the government is trying to put on. "look at us, we're doing something(tm) about security!

    makes me wonder if this is microsoft's way of making sure it has a chance to influence what the gov. considers secure.

    --
    This comment is fully compliant with RFC 527.
  111. Sad ... by AftanGustur · · Score: 1


    Lip service or not, these developers have in their job description to be scapegoats. That is not an enviable position.

    Absolutely, as everybody, with even the slightest sense of how software security works, knows, you can't just *add* security afterwards as Microsoft seems to be proposing with this "code review".

    It just doesn't work that way !

    --
    echo '[q]sa[ln0=aln80~Psnlbx]16isb572CCB9AE9DB03273snlbxq' |dc
  112. Product placement by SgtChaireBourne · · Score: 1
    MS was to computers what Big Tobacco was to sports. If you didn't get in the pyramid by now, it's too late, forget it. It's over - especially now that Greenspan has said his. Too much attention is being spent on the antics of a dead company.

    Slashdot's product placement and trolling stepped up while European legislators were discussing software patents. Picayune articles, many of which consisted of rehashed softer versions of old FUD and misinformation, covered topics which have already been dealt with, again and again.

    Since most novices do not understand the scope and severity of MS's problems and since any critique of MS, no matter the merit, gets written off as "MS-Bashing", it would be best to focus on the more successful areas of the IT sector. Here are a few examples:

    Check the forums for tools that work - *BSD, Linux, QNX, Netware, eDirectory, LDAP, Kerberos, KDE, Gnome, Apache, MySQL, Postgresql, and so on ...

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  113. maybe using a windows emulator on something else? by wadiwood · · Score: 1

    Do you suppose you could secure windows by putting it inside a windows emulator?

    For example: is a Mac running OSX and windows emulator (eg virtual PC) more secure than windows by itself

    or how about linux running win for lin ?

    Can you really stuff things up by running a mac X emulator or unix emulator on windows?

    --

    -- it must be true, it's on the internet.
  114. problem is... by Anonymous Coward · · Score: 0

    It's still an after-the-fact cleanup, patching in security after the code is written is not very reassuring.

  115. antivirus by jtilak · · Score: 1

    If microsoft was serious about computer security, they would bundle antivirus with windows for free, like they did with IE, and we wouldn't need third party antivirus programs.

    1. Re:antivirus by Anonymous Coward · · Score: 0

      they did that with dos 5 or 6(i forget which) and it sucked. I'd imagine that if they did it again, it would suck. See, MS likes to build things but they blow at keeping them up-to-date. AV software requires you to be on top of your sht all the time.

      If they were serious about security, they'd fix what holes remain in IE and tear out ActiveX. They're not serious.

    2. Re:antivirus by Gonzoman · · Score: 1

      It was DOS 6 and your right, it sucked, as did almost everything about DOS 6.

  116. Microsoft will get it right one day... by ayjay29 · · Score: 4, Insightful

    ... bad news for Linux etc. when it does.

    Windows 3 was crap. ...95 was a big improvement.

    Windows 95 is unstable. ...Windows 2000 was a huge improvement.

    Windows 2000 Server is insecure. ...The 2003 servers ARE a big step in the right direction.

    If they progress as far in the next decade as in the past decade, they will be delivering stable, relyable and secure servers. If that happens I dont see Linux based systems able to offer too much competition.

    --
    Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated up.
    1. Re:Microsoft will get it right one day... by Anonymous Coward · · Score: 0

      Sure. And I'll just stand around with my thumb in my ass for the next 10 years waiting for that to happen.

    2. Re:Microsoft will get it right one day... by Anonymous Coward · · Score: 0

      I've had discussions with people who think similarly to the way you do. "Just you wait! In five years WindowsNT will have all the features and stability of UNIX!"

      What you seem to fail to understand is that Linux and UNIX aren't exactly going to be standing around twiddling their thumbs during that five or ten years.

      Where was Linux ten years ago compared to NT and where are they now? Compared to the improvements made to NT, I would say that Linux has made _huge_ leaps and bounds. As well, it has only been the last few years or so that big business has been allocating resources to help improve Linux and, as far as I can see, it still hasn't reached its peak. Yet, you think that in ten years MS will surpass Linux?

  117. The first paragraph says it all by NickFortune · · Score: 2, Insightful
    The new Security Engineering Strategy team will look at security across all Microsoft product lines, with the ultimate goal being that customers will take security for granted in Microsoft products

    Not "to sell secure software" you'll notice, but to make customers "take security for granted".

    So presumably if the security stinks but everyone assumes the system is secure, they will be satisfied.

    Everything I dislike about the company in a nutshell

    --
    Don't let THEM immanentize the Eschaton!
  118. It's a Very Easy Task by cardoso · · Score: 1

    Step 1: CD C:\data\sources\

    Step 2: erase *.c

    Step 3: erase *.h

    Step 4: notepad.exe newrelease.txt

    Step 5: Start typing... /* Microsoft codebase V2.0...

    --

    []'s Carlos Cardoso - Becoming a brazilian ProBlogger, typo by typo
  119. How to fix bugs in your code base (The old way) by Felinoid · · Score: 1

    Have a team of debuggers on staff.
    When something breaks stick an open debugger on the task.

    I knew a profesional debugger when I was a kid.
    He called my computer a toy... I didn't appreceate that.

    --
    I don't actually exist.
  120. Code Clean Up - remove Blue Screen Of Death? by Bu+Na+Dan · · Score: 1

    so windows will crash without any blue screen - that cleans the code by some fifty lines ...

  121. Re:More Innovation from MS! PeerReview.Net++(R)TM by comet_11 · · Score: 1

    Pardon, I think you mean PeerReview.Net#

    --
    By reading this comment, you immediately waive any and all rights regarding it.
  122. not vi by Anonymous Coward · · Score: 0

    actually, it is Emacs/readline.

  123. MS Code Reviews... by glenstar · · Score: 1
    are torturous. Honestly. You print out your code, in some cases hundreds of pages, and sit with 3 or 4 people and go through it *line by line*. Painful. I remember being asked questions such as "Why did you name this function that?" and "Tell me your thought process behind having the code flow this way" and, my favorite, "Why didn't you use the MFC CString class?". Icky icky icky.

    Security holes at MS come from one of two sources:

    • Code reviewers with ADD
    • Developers trying to balance the idiotic amount of "user friendliness" demanded by the PM and good, clean, secure code.

    There was one case where I had gone through a farily lenghty piece of code (ok, maybe not *that* large, but it was a good 25 pages of print-out). The next day I received a new print-out of the code with nearly each line annotated with a comment like "This should be like this" etc...

    I do have to say that they were very thourough in their review, but that once the review was done nobody went back through the code to make sure that I had actually made the changes.

  124. more indirection, yes please by DrSkwid · · Score: 1

    I think it was Butler Lampson who said "all problems in Computer Science can be solved by another level of indirection."

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  125. For the world's sake by truthsearch · · Score: 2, Interesting

    I hope for the world's sake they do a terrible job and most people realize it. If their software remains marginally good enough in most people's minds, as it is now, it'll continue to be used. Their walking a thin line right now. If their software is seen as more expensive, buggier, or more insecure than it is now, even by just a little, they'll hurt. Anything that keeps them above that line keeps them in business. I'd much rather see them fail so there's a much quicker transition to FOSS.

    1. Re:For the world's sake by Anonymous Coward · · Score: 0

      Of course you want Windows to fail. Windows has a ton of advantages over Linux, and just about all Linux has going for it is that is free. Yet, still, no one will use it on their desktop. And by no one, I mean 1%.

  126. innovation at work by Anonymous Coward · · Score: 0

    nice way to hide in a constructive way the 750M fine to AOL, that team will probably cost around 750M overall so the earning / share will not suffer much :P

  127. What is the future? by UnknowingFool · · Score: 1
    Intentions aside, if MS actually is serious about fixing their code, what kind of problems will they find? Will we get 2 patches daily instead of one? Or will they find that some parts cannot be fixed as with the Endpoint Mapper issue earlier this year where they admitted NT was too flawed to fix.

    No matter what they do, they'll spin it like the other deficiencies in the past as if stability and security were features and innovation as opposed to standards every other OS has had for years. I don't think that they will ever become as stable and secure as Linux and Unix, but they'll get most people to believe that they are.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  128. patching holes by butane_bob2003 · · Score: 1

    is not the same as building without holes. This is a waste of resources if you ask me, it wont improve the situation at all. I pity the members of this team.

    --


    TallGreen CMS hosting
  129. OH come on now by bobKali · · Score: 0

    You mean you actually take them at their word????? This is nothing more than marketingspeak, insincere, good-time rock-n-roll garbage spewing forth from Redmond. I have not seen any of their previous efforts resulting in a relatively error-free environment for me.

    You're right in that it's not going to happen overnight. But then again, it's not happened in the past several years (since they launched the whole "trustworthy computing" thing - however long that's been) or even the past decade. I still have computer crashed triggered by cutting and pasting plain text between applications. Now it's not happening daily anymore, but once or twice a week now...then again, this is still completely unacceptable to me.

    I'm sorry to rant, but they've had their chances to unf*ck their software, and they've consistantly blown it, and they've been rewarded for it. I see no real incentive for them to change. I DO see an incentive for them to make noise about how they're changing, but all the window dressing in the world won't make my MS Windows workstation any more stable. They have a long history as a pack of unrepentant, unpunished liars, and I just don't believe them.

    Besides, their paperclip mascot is nowhere near as cool as our penguin.

    1. Re:OH come on now by DrTentacle · · Score: 5, Insightful
      I see no real incentive for them to change


      Security is one of the main areas that MS gets blasted for. While the security in their server products has some merits, it's undermined by the bugs that continuously appear and the total lack of lockdown in out-of-the-box config. Their push on security would have to address all these issues - Removing issues from the code prior to shipping, improving their response to the bugs that still appear, locking down products and educating users to unlock them as appropriate, and most importantly of all, concentrating on designing their systems to incorporate security from the start, rather than trying to tack it on later. There's been some movement in some of these areas...but nowhere near enough yet.

      So will they do it? You're right in that there is little evidence so far. Given the constant slating they receive in this area, there is certainly a motive to improve it. But given the apparent lifetime of legacy code in Windows, it's not going to show significant results any time soon in that arena. I would suspect it would be more evident in "new" products such as .NET, etc.

      Trustworthy computing was launched in Jan 2002, there's some info on what they claim to have achieved on their site.

      I do agree with you about Clippy tho :)
    2. Re:OH come on now by Daniel+Phillips · · Score: 1

      So will they do it? You're right in that there is little evidence so far. Given the constant slating they receive in this area, there is certainly a motive to improve it. But given the apparent lifetime of legacy code in Windows, it's not going to show significant results any time soon in that arena. I would suspect it would be more evident in "new" products such as .NET, etc.

      How many times do you have to get burned before you become shy of the fire?

      --
      Have you got your LWN subscription yet?
    3. Re:OH come on now by Anonymous Coward · · Score: 0

      We asked them what was the most important security issue for us to address first, and their consistent answer was that we needed to do a better job on patch management -- on delivering high-quality patches for vulnerabilities and communicating their availability more effectively.

      Considering that I just applied thr latest critical patch to the critical patch to the critical patch for IE6, I can only presume that MS is going to continue putting turds into fancy, expensive boxes labeled "fine Belgian chocolate" for some years to come.

  130. Microsoft to clean up code by iceT · · Score: 1

    What, AGAIN!?!?

    --
    -- You can't idiot-proof anything, because they're always coming out with better idiots.
  131. Can't fix up bad code by xRelisH · · Score: 2

    I personally think that ms should start a all over again from the ground up. The problem is that fixing up bad code is annoying and you ultimately get something that's mangled.
    The best thing to do would be to start over but make things appear the same at the upper layers so some existing apps work. However I do understand that this would leave a bunch of non working apps, but I think it might give M$ new life.
    They could even rip off linux and call it their own. But don't get me wrong, I hate M$.

  132. its easy by azoidx · · Score: 3, Funny

    cat bad_code.c |grep -v getchar > good_code.c

  133. Again, more myth by djupedal · · Score: 1

    Just go right on believing. The cool-aid makes it all real.....

    1. Re:Again, more myth by Anonymous Coward · · Score: 0

      Hmm, and how many employees did Enron have :) ?

  134. Doesn't seem fair by michaelhood · · Score: 1

    Microsoft is a long way from its ultimate goal where users can take security for granted in its products

    How come Microsoft gets to take security for granted in its products, but the users don't?!

  135. Is it really? by juuri · · Score: 1

    If they're looking into new strategies, even ones that are years behind their time, we should know about it. When you only look at yourself, you'll sometimes see innovation or monopolism take over while you're busy staring at your shoes.

    I had no idea this was a competition.

    --
    --- I do not moderate.
  136. Multiple interpretations by The+Man · · Score: 1
    the majority of viruses written attack Microsoft products

    Why is it that when I read this, my first thought is "oh, so now Microsoft is going to be writing lots of viruses for other platforms...how nice"? There's more than one way to skin cats, and Microsoft always seems to pick the way that does harm to its competition. Benefits to its own customers are seldom a serious consideration.

    Maybe I'm just overly cynical this morning...but tell me you didn't think the same thing...

  137. The Linux community should prepare to do the same by ThinkTiM · · Score: 1

    Maybe there's already groups doing this - but it would be interesting to set up a group of OSS people who are willing to be pulled into to perform security reviews of open source software. It would basically be a service to OSS projects.

  138. Pardon my cynicism but ... by Tsu+Dho+Nimh · · Score: 2, Interesting
    haven't we seen a security initiative before, the one that was supposed make Windows more secure than ever?

    Will this group have the authority to hold up a release if there are security holes? If not, they are just window dressing.

    Is this group REALLY going to be able to get Microsoft to create secure code, or just avoid goofs so large they provoke those embarassing industry articles about lack of security?

  139. Help with security hunting! by RoadkillBunny · · Score: 1

    Microsoft would be much more sucesful if they accually read the bug-reports send by people, nnot just deleted them.

    --
    Cheers,
    RoadkillBunny
  140. This is a PR move, nothing more by jhylkema · · Score: 1

    Sorry Bill, I have to call bullshit on this one.

    Astute /.'ers will recall His Billness having to withdraw an ad that claims his wares "makes hackers obsolete". Even more astute /.'ers will remember the day when Microsoft's own code was compromised. They can't even protect their own IP with their own products! If M$ can't keep its own IP secure with Windows, who can?

  141. Duh, of course there are more MS virii by jagilbertvt · · Score: 1

    Is it just me, or does it seem that the main reason most virii are written for MS products is because MS products are installed on 90+% of PCs? It would be rather silly to write a virus for BeOS or other similarly underappreciated OSes. If Linux was installed on 90+% of PCs I'm sure we'd see fewer MS virii and more Linux virii. Doesn't take a mathematician to figure that out.

    -Jagged

  142. They Can Try... by Generic_SuperHero · · Score: 1

    the only microsoft os ive seen that is secure is win. 3.1 despite its lack of functioning, remember, 3.1 didn't need a serial , good times... i mean how many operating systems to you have to put out to get it right? i think if they make the end-all do-all os they would all be out of a job

    1. Re:They Can Try... by originalLackey · · Score: 1

      "i mean how many operating systems to you have to put out to get it right?" If anyone should know it would be the *nix community.

  143. Oh, you want to have one of those arguments? by truthsearch · · Score: 1

    So you want to have one of those arguments? Check the news about all of the countries whose governments are switching desktops to linux. Take a look at the largest country in the world having their government promote their own flavor of desktop linux. And how about yesterday's news of a country with more people than the US having a president recommending linux. Let's not forget IBM with over 250,000 employees switching. And then there's Merryl Lynch and Morgan Stanley. How about 640,000 TiVo users? See my list for a few more.

  144. Yeah right... by 3seas · · Score: 1

    Microsoft is a federal criminal that wasn't punished.

    they have no motive to do anything in honesty. It is more likely that updates and patches only provide MS with more hooks into your system.

    The only way to verify in the publics eyes what MS is doing is to open their source up.

    And we all know that is not going to happen.

    Who want's to bet that if there is SCO code in Linux it was either SCO or MS that put it there?

  145. Take Action Against the FCC (OT) by syrupMatt · · Score: 1

    This Monday, FCC Chair Michael Powell will hold his vote on media
    consolidation. There's nothing special about that date -- it's totally
    arbitrary. The vote will conclude a process which has shown deliberate
    disregard for the views and opinions of the American
    people. Powell has refused to even release the actual language of
    the rule change -- it won't be known until after the vote. And he's
    only held a single meeting to hear the views of the public. Even when a
    bipartisan group of Senators requested that he give Congress some time
    to discuss the impact of this change, Powell brushed them off.

    Chairman Powell still has the power to delay the rule change and allow
    time to have a democratic debate about its consequences. Please call
    him today and ask him to allow a real public debate on an issue of such
    massive importance.

    You can reach Powell's office at:
    (202) 418-1000

    Once you've made your call, please let us know at:
    http://moveon.org/fcccall.html

    --
    "Moving through the masses like a fish through water." syrup
  146. Re:Entrenchment by symbolic · · Score: 1


    Don't forget this most important issue...many people *started* using M$ products, but now, like a bad crack habit, they can't stop - the cost is just too great. I'd argue that they might like to look at alternatives, but M$' proprietary document formats, ever-changing APIs, etc, is making it next to impossible to implement a compatible alternative.

  147. Re:GROW UP!!! by Trolling4Dollars · · Score: 1

    Here here! What you have said perfectly illustrates how it is that "middle-men" infect every sector of human society. These middle men have nothing to offer of any real worth. They simply repackage (ie. dress up the image) other people's work and claim to have something new, different or good for you. SOme examples:

    The "Knowledge Manager" - This curious occupation *DID* at one point have validity. These were people who were charged with the task of taking the vast amounts of information that our digital culture has created and organizing that data. They SHOULD be a perfect blend between librarian and DB admin. In reality, most knowledge managers know nothing about technology, but argue vehemently that they should control the direction of its use in a company. Most of the KM trade journals I've looked at usually put the knowledge manager in the position of "knowing" more than the programmer or engineer about technology. Many illustrations in the articles show you a stylish, "professional" who is "leading" the lowly tech/admin/coder to building the next "great thing". Most of the KM journals themselves are extremely light on any disucssion of technology and put more emphasis on management. The mistaken assumption when it comes to KM today is that the "M" means managing people. It doesn not mean that at all... it means managing information. The middle men have worked their way into yet another promising field and "ponzied" it.

    The "Employment Agency" - Today, employment agencies are one of the biggest businesses in the United States (and possible the rest of the capitalist world). They purport to connect a promising employee with an employer for a temporary period of time. This service takes money from both the employer and the employee. When the employment agency is actually competent with IT candidates, this can be somewhat beneficial. But look at the big picture. Take a ten mile step back and look at what's happening. These companies are making incredible amount of money by connecting people with jobs. Most of the jobs are temporary and both parties pay for the service. What's wrong with this picture? In reality, these companies aren't doing anything really productive and are getting a disproprtionately large amount of money for it. Again... the middle men make a grab for it.

    When it comes to REAL IT folks, it's all about what you know in relation to technology and getting your hands dirty. Even if you are management.

  148. Well... by Anonymous Coward · · Score: 0

    you have to admit, they have more people freely helping them research security than anyone else.

  149. NSA by Detritus · · Score: 1

    For many years, the NSA used a Multics system, dockmaster, for Internet email and networked forums.

    --
    Mea navis aericumbens anguillis abundat
    1. Re:NSA by ctid · · Score: 1

      I didn't know that. I think the fact that it was running until 1998 is also significant, as it will have "experienced" something like the modern Internet during its life. I still wonder whether the fact that there were very few Multics systems would not have helped its security record; after all, what hacker would target that OS?

      Either way, I've learned something new today, for which thanks.

      --
      Reality is defined by the maddest person in the room
  150. OpenBSD + Windows by revividus · · Score: 2, Funny
    OpenWindows?

    Doesn't sound too secure...

  151. Factual data needed by fmedio · · Score: 1

    More seriously, did anybody here ever have the occasion to take a look at bits of windows code ? What did it look like ?

  152. Re:Virus on windows? Yes because it is dominant!! by anderm7 · · Score: 1

    Actually, it's because every program that runs on Windows can do (almost) whatever it wants. I'd bet you'd see a lot more Linux viruses if we all ran as root.

  153. Code Cleaning by Anonymous Coward · · Score: 0

    Microsoft has decided to beef up their security group by adding a code cleaning group according to Infoworld.

    Maybe they can slip some "SCO code" in there while they're at it.

  154. what 'code cleanup' means by poot_rootbeer · · Score: 1


    All the Windows source files will now be properly formatted and indented!

  155. Re:More Innovation from MS! PeerReview.Net++(R)TM by HighOrbit · · Score: 1

    Make that "Visual PeerReview.Net#"

  156. marketing, marketing, marketing by DuctTape · · Score: 1
    Okay, yet another marketing ploy to make people thing that Redmond's serious about cleaning up. The last one didn't do any good. This one won't do any good, either. Second (or third or fourth) verse, same as the first: "Oh, hey, everybody, look at us. We care!. So buy more Microsoft ... Oops, how'd that break?"

    Thing is, they have no business reason to do so. The only reason they'd do this would be if security and quality issues lowered their market share and/or their stock price. And I haven't heard that it has. Well, perhaps announcing this will raise both?

    I've proposed cleaning up code before in previous lives (um, not with Microsoft), but my project manager / CTO would look at me and say, "Does it make business sense to do this? Will we see tangible savings by cleaning up the code? Can you prove that by spending X hours refactoring or redesigning our foundation that we can recover X+ hours of productivity?" Of course I couldn't, or at least I didn't want to spend the time doing the analysis while getting futher behind in the project. Yeah, you can say that this is dangerous thinking, but this guy had to cover his ass, and if his boss found out that we were making the code "prettier", he'd get his butt chewed.

    In this regard, there not being a business reason for Microsoft to clean up their code, my preference would be that Microsoft would just keep quiet, sit back, and let the bucks roll in as usual. Money's not a totally bad thing, you know. Especially when you own the world.

    DT

    --
    Is this thing on? Hello?
  157. Design and Security Microsoft's Greatest Flaw. by hackus · · Score: 1

    There is no way on earth Windows is going to get anymore secure. In fact, it will only get LESS secure as time goes on.

    Why is that you say?

    Simple. Windows is a monolithic piece of software.

    You say so what and what does that have to do with it?

    Plenty.

    For starters, anyone who knows anything about Software Engineering, and what came out of the DARPA and TRW research agencies in the 80's/90's, building some of the largest edifaces of software ever concieved is: Less software makes more secure software.

    That is, you don't make a software system, more secure, by adding more secure software to it.

    Software by its definition is not a discrete mathematical concept, it is quite open ended. Therefore you can never compute, predict, or make software, by definition secure on a Von Neumann computing device.

    It is a pipe dream.

    (That is why I don't subscribe to the idea that software is patentable, as some say because it is like a physical system, machine. It isn't. Software is a method for producing abstract mathematics. It has no bounds, and all thinking methods in the known universe are employed to make it work. By its definition it is PUBLIC DOMAIN.)

    Furthermore, agencies working in secret, building black projects with the tax base of the entire US trillion dollar economic base at thier disposal, have studied these issues with far more resources than any commercial venture can muster, certainly more than Microsoft has.

    I find it ironic that even the most declassified basic research that comes out of the published reports on the DARPA software engineering/development organization goes unheeded by so called "Microsoft Press" book publishing "experts".

    The only way to make Windows more secure is to start copying the way Unix was concieved of and built, and take a lesson from history.

    That is, Linux/BSD/Unix allows you to CUT OUT large sections of software that need not be loaded or used on a machine for a particular purpose by the kernel or OS.

    If you could for example, cut out the GUI on Windows, all of the COM/DCOM and .Net services, and leave just a IP Stack and a Pop Mail service on the machine, you go much further in protecting the security of the machine.

    But you can't do that. Microsoft is trying to make machines so easy to use that a monkey could operate them.

    That is fine, but the world is composed of bigger problems than the monkey and the machine combined.

    This is of itself is not bad, software should be easy to use, but software must solve a problem, and I am afraid, business/scientific problems cannot be ALL classified in the same genere as Miss Tilken's and her Mail Merge problem that can be solved with a Dialog Box and OK/CANCEL options in a Wizard.

    But this is how Microsoft continues to proceed, building ever more enourmous Operating System Software and applications, taking this philosophy and putting it into thier OS base were it doesn't belong.

    The Monkey Philosophy belongs on the application level, along with Miss Tilken's. Not at the OS level.

    Effectively, Microsoft is attempting to encode every possible "Enterprise" scenario in its products "Wizards", so that the software makes most of the decisions, and the User just pushes buttons.

    Worse, those scenarios not covered in this contrived decision tree, are deemed "enemies of the state". (i.e. products, such as third party tools you load on your XP machine can be viewed by Microsoft as 'something we don't support', call back after you remove the offending software..thank you for your $300 dollars, have a nice day.).

    Then many people on slashdot, and Microsoft, I have seen have said "Well, our products save you a ton of time and make things very easy..."

    I am sorry, but software and computers, and particularly the problems they attempt to solve...ALL CAN'T BE EASY. Undoubtedly SOME can, but not ALL. For things like Word Processing and SpreadSheet work,

    --
    Got Geometrodynamics? Awe, too hard to figure out? Too bad.
  158. Re:More Innovation from MS! PeerReview.Net++(R)TM by comet_11 · · Score: 1

    Is that OEM, upgrade, developer, enterprise, testing, professional or home edition?

    --
    By reading this comment, you immediately waive any and all rights regarding it.
  159. Not the director of MS security by tekman · · Score: 1
    The slashdot summary says:
    As the director of MS security engineering says: 'Microsoft is a long way from its ultimate goal where users can take security for granted in its products...the majority of viruses written attack Microsoft products.'
    The article says:
    Mark Litchfield, a security researcher with Next Generation Security Software (NGSSoftware) of Sutton, England. Litchfield and NGSSoftware have been credited with discovering a number of bugs in Microsoft software. [...] However, Microsoft is a long way from its ultimate goal where users can take security for granted in its products, Litchfield said.
    The quote in the summary is from Litchfield, who isn't even employed by Microsoft; much less is he the "director of MS security engineering". Sheesh.
  160. Code Cleaning = Worst Job Ever? by KalenDarrie · · Score: 1

    I don't know about anyone else, but being assigned to clean Microsoft's code sounds like one of the worst jobs imaginable. Not just from the sheer size, but attempting to find all of those little loopholes amid a mish-mash of cross integration without sacrificing functionality and speed? I hope they're well paid.

    --
    Kalen D'arrie
    1. Re:Code Cleaning = Worst Job Ever? by m1chael · · Score: 1

      code cleaning is the worse approach you can possibly fathom. thats why they 'say' they will 'lay' groundwork for future microsoft 'products' so that they will be inherently 'more' secure.

      if this actually happens it benefits alot of people who use microsoft products which seems to be quite a few people so it good if it happens. it still wont stop people from using oss so this can only be good if it happens and windows is actually written from scratch just like windows 2000 was ;P

      --
      I know you are psychotic, but please make an effort.
  161. Windows source code cleanup by Anonymous Coward · · Score: 0

    I can do it in one line:

    C:> deltree D:\source_code\windows

  162. after the clean up... by Hooya · · Score: 1

    ...all that remains is:

    int main(int argc, char** argv)
    {
    return -1;
    }

  163. Lowering the Percentage of Windows viruses by decapentaplegic · · Score: 1

    "the majority of viruses written attack Microsoft products."

    Well if that's the problem, the solution is simple.

    1) Tell the new team to write viruses to attack non-Microsoft products.
    2) Advertise that 90% of viruses attack non-Microsoft products.
    3) Profit!

    Note, that order might be slightly mixed up.

  164. Not surprised by rsilvergun · · Score: 1

    Seeing as how they're paying Indians $1.25 an hour to do the code, I'm not surprised they're finnally doing this. All the code matainence jobs are moving overseas. Only the high end stuff is being kept. I've got friends lossing tech support job to India, so I'm kinda bitter. A good friend of my just went from $9.25/hr with AOL to $6/hr at Jack in the Box. Sucks

    I like how Microsoft attacks linux for not providing America jobs and taxes then moves the jobs overseas and uses loopholes to avoid taxes.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  165. Their track record on security so far... by snapman · · Score: 1

    ...indicates their security code will open up security holes. Their credit is so bad, people won't take their cash.

    --
    "What luck for the rulers that men do not think." Adolf Hitler
  166. Even if they do... by sean.peters · · Score: 1

    Win 2k+3 costs thousands of USD/processor... Linux - still free.

    Still think Linux can't compete?

    Sean

    1. Re:Even if they do... by aardwolf64 · · Score: 1

      I'll take a dump in your hand for free, but do you prefer that to chocolate ice cream?

    2. Re:Even if they do... by ddriver · · Score: 1

      Are you sure you would take a dump on my hands?
      Re:A friendly reminder from your local safety coun

      --
      I found my inner child, then I got caught abusing it...
  167. Another security group by subzero_ice · · Score: 1

    All M$ does is form more security groups to try and convince the world that it is working on securing its products, and that is why they added IIS to the kernel in Windows 2003 so that when a cracker exploits it he has more control than ever. So much for making the software more secure.

  168. Took 'em 15+ years to figure this out... by Stonan · · Score: 1

    how long is it gonna take 'em to implement it? (So that the general public notices, that is...)

    --
    The GEEK shall inherit the earth...
  169. Another good thing by JW+Troll · · Score: 0

    Obviously, GNU bashing abounds, but only in the world of end-users. I view this as a good thing.

    Working in an environment that is purely Red Hat-based on the desktop, with significant Red Hat server infrastructure, I can only applaud any efforts Open Source guys are making to clear up the mess that is obviously present. No, it's not going to happen overnight - Just as the company I work for is not going to replace all it's investment in tech support talent overnight.

    Unfortunately, being a GNU developer does not make you a usability expert. As usual, Xfree (and anything using it) will continue to allow simple flaws, such as buffer overruns, into their code, allowing root access to idiots - but that's the least of users' worries on an OS as close to UNIX as humanly possible, without infringing on any of SCO's dubious rights. Having a group of people who focus on Open Source usability would be, without a doubt, a VERY good thing. While this may not be the potentially rigorous design/interface review that proprietary software gets, since people *do* pay for proprietary, after all, it's better than what presently happens - ie, absolutely ZERO and intelligent design or consistency in user interface elements. Why don't Open Source zealots just clone OSX? Save some time on the design, and make things nicer for everybody.

    As for the issue of scapegoats...from an external point of view, getting Linux people to admit to Xfree's abysmal GUI latency, AND do anything to fix it, can be a difficult job at the best of times. Internally, if a group of interface "experts" fail to recognise flaws in a piece of code...then surely they are failing at their job? Strangely enough, BeOS had this issue nailed down *years* ago, but still OSS lags behind 1996 technology.

    Finally, there's been a lot of flaming about the fact that there's another window manager coming out daily from the Free Software crowd. I welcome all of them, in parallel, as moving towards sorting out some of the many issues they have. The less time I have to spend working on patching buggy GNU or other free software, the happier I will be.

    --
    just like the humble blood clot... turboporsche@telus.net
  170. Windows Involvement by kmilani2134 · · Score: 1
    There has been a lot of speculation on just how Windows is involved with all of this.

    So I found it interesting that there is a "Windows Services for UNIX 3.0" CD included with the June issue of Sys Admin (the journal for UNIX systems administrators.)

    --
    Those who trade freedom for security will lose both, and deserve neither" -- Ben Franklin
  171. Code Clean Up? by Amazing+Quantum+Man · · Score: 1

    So what happened in Feb 2002?

    --
    Fascism starts when the efficiency of the government becomes more important than the rights of the people.
  172. Re: Fuck Java by Fizzl · · Score: 1

    Oh, that's brilliant. Do you tell your management that? .. Or, hmm, maybe you're a school-boy.

    Yes, I tell my management that. I just turned down a Java component that was supposed to be one of my responsibilities.
    The manager was very cool with that and we just shuffled components with another guy.

    No.. I'm not a school boy. I also know how to program with this piece of crap. I just feel it is not of any use.

    You, on the other hand haven't probably had a touch with a real life. That, or you have got some silly Java project after high school so you don't have to fry hamburgers.

    Oh yeah, almost forgot: My dad can beat up your dad and you must be an immature child because you might have a strong opinion about something.

    Ok, I might hate Java because I have to nowadays deal with so many simpletons who don't understand how the computers work they are supposed to "program".

  173. Re:Poppycock.[way OT] by IndependentVik · · Score: 1

    I do hate being a pendantic asshole . . .

    Yeah, I'm sure it keeps you up at night ;)

    --
    I'd suggest you don't use Slashdot as your only news source, or you will suffer permanent brain damage.
  174. Sugar coated.. by mysterious_mark · · Score: 1

    Sugar coated shit is still shit. MM

  175. FUD and Posing by Anonymous Coward · · Score: 0

    Is it just me, or has Microsoft seriously upped their initiatives now that the SCO vs IBM suit is in the media? Coincidence?

  176. Central planning a nonstarter by Anonymous Coward · · Score: 0

    The Soviets tried it, and it didn't work. Why should it be any different for Microsoft?

  177. Their first recommendation... by ConceptJunkie · · Score: 1

    Word needs skins.

    It's been said before... it's all lip service. How many times is Microsoft going to promise to get its act together before the whole world realizes they're just blowing smoke.

    That VP said it right, security is an afterthought at MS. A company that can't even go a week without discovering a security hole "that allows attackers to completely take over a machine" has no business doing anything but apologizing profusely.

    After all, most of these bugs seem to be from buffer overruns... which is Computer 101 stuff. When you can't get stuff right that they were doing in the 1950's how can we expect software for the 2000's?

    I'm happy to blow a couple karma points to get this off my chest.

    --
    You are in a maze of twisty little passages, all alike.
  178. Windows architecture breeds viruses by nirbasito · · Score: 1

    Most viruses come in the form of .exe and .bat attachments in your outlook mail. As long as Microsoft OS keeps the link between clicking your attachment and executing a program, viruses are going to hang around MS OS's. Unlike MS ...linux or other favours of unix , by default, do not grant any file execute bit permission ... just based on their extensions. This points to a inherently weak architecture design in MS OS's. Fortunately evil Microsoft finds it hard to change this architecture as doing so would evidently men giving up some of the "user-friendly" features like clicking executables from attachments.

  179. In Other News by Unregistered · · Score: 1

    Hell To Freeze Over
    Flying Pigs Spotted Over Boston
    Bush Adopts Islam

    1. Re:In Other News by m1chael · · Score: 1

      aliens visit Raelian embassy.

      --
      I know you are psychotic, but please make an effort.
  180. Supposed to be in the "It's funny! Laugh!" section by MMHere · · Score: 1
    Why wasn't this story categorized under the

    It's funny! Laugh!
    section of slashdot?
  181. Microsoft's problem by John+Bayko · · Score: 1
    The fundamental problem with Microsoft software, as far as bugs (and thus security) go is something that Steve Balmer bragged about, in comparing Windows to open source as far as innovation.

    He pointed out that if Microsoft wants to add a feature, they have control of the whole code from kernel to Excel, and can make all the changed needed for that new feature directly, and quickly, where with open source (or suppliers who don't have a complete software solution), you need to get different project groups/companies together to agree on whether they want this feature, how to implement it, how the components should interact, and so on.

    This, he says, is why Microsoft can "innovate" (add features, whether they're actually innovative or not) more quickly than open source software.

    This is also the weakness, because when a bug appears, there is no easy way to tell where in the entire massive Microsoft code base the problem lies. The entire structure is so interrelated that, while you can add things easily, removing even a small thing may break things massively - so they don't, leading to bloat - and tracing things is like a needle in a haystack, and getting worse.

    You can see the Microsoft way in the .NET vs. Java EE "pet shop" demonstration application. The Java version, created by Sun, was intended to be a "best practices" demonstration of modular, easily modifyable design, and wasn't intended to perform well. Microsoft's .NET version has often been called a living "anti-pattern" - an example of how not to create an enterprise application, although its faster.

    By comparison, open source (and most smaller proprietary software systems) are small modules which interface to each other with simple, well-defined interfaces - largely because defining interfaces is so much trouble that nobody likes to do it, so they're only added with careful forethought and design to make them as general as reasonable, so you don't have to change it later or add another.

    This means that generally, when there's a bug, it's well defined, easily tracable, and more importantly, its damage is limited. It is inherently more secure than an integrated, unstructured approach. It is also much slower to advance.

    One of the reasons that customers in the software industry accept such hideous software as is available now is simply that it's a new industry - computers are still finding new uses, and at this point it's more important to get computers to do these new things at all, than to get them to do them well. Microsoft's success has been partly because it's development model is based on getting computers to do new things first, thus defining the market.

    There is a limit to the new things that can be done with computers. Or at least, certain fields which have become well defined as far as what features are needed and useful. Office applications are an example - Microsoft has not been able to introduce a single genuinely useful feature to Word, Excel, or most of its other desktop software in a long time.

    This will affect the entire computer industry. My guess is that we've figured out about a third of all the things computers are useful for. When that upper limit is finally approached, then competing software will all be able to catch up feature-wise, and all do basically the same thing. At that point, software quality will be the main way of differentiating products, and any company that's not able to switch development models away from feature-expansion to quality improvement will be in big trouble.

    My guess is that will start to happen in about 40 years, but I may be wrong. There are some signs of it happening in some areas already (servers, for example).

  182. Multics by John+Bayko · · Score: 1
    Multics didn't operate in today's environment, however. How would it have done if it was attached to the Internet?

    Probably very well.

    Here's an example of the kind of thinking that went into Multics - stacks went up from 0, not down from the high end of memory. That was so that the return address and important stack information was stored below any local buffers. If some poorly written application overwrote a local buffer, the excess data would flow harmlessly upward into unallocated memory land. It might screw up local variables, but it would not, ever, allow the return address to be overwritten, and could not, ever, be used to execute arbitrary code.

    Solaris and other secure operating systems do things like non-executable stacks, which patch the problem, but don't solve it completely. I don't think Linux does even that.

    There was a lot of OS know-how of the past that seems to have been lost like the mytical Atlantis.

  183. Call in the Cleaner! by One+Louder · · Score: 1

    I suggest Harvey Keitel, not Jean Reno.

  184. not possible.. by qnxdude · · Score: 0

    you simply can't make honey(linux) out of dog shit(windows).

  185. Let me see.......... by Allnighterking · · Score: 1

    ILoo + SCO + Code Cleaning....

    Am I alone here or does this give a whole new meaning to "core-dump"?

    --

    I'm sorry, I'm to tired to be witty at the moment so this message will have to do.

  186. Bounds check everything? by Kashif+Shaikh · · Score: 1

    I don't think so. You can trust your own code(as long as it has not been hacked/tampored with) for not overstepping a buffer.

    Where you have to bound check are inputs: incoming network packets, cli input, file input, web input, etc.

  187. windows2000test.com was +5 Informative by leonbrooks · · Score: 1
    I was there on the day and watched a BackOrifice port open on that box, then the server went away - again - a few seconds later (because of "lightning storms in the Redmond area", but the router immediately in front of it - also labelled Redmond - didn't die, and neither did the transparent router between that and the box proper, this on an "unfirewalled" box, but we're used to Microsoft telling multiple layers of outright lies anyway) and when it came back again a few hours later their log promptly grew an entry from someone who was whining about them intervening to cut him off just as he opened a back connection to pull a keylog. So when I see...

    Sadly it received mostly packets from kiddies so that program was terminated.

    ...I tend to think, "Sadly, it was cancelled because it was up and down like a yoyo for about two weeks and that looked bad."

    OTOH, the Free Software community responded by putting up a PPC Linux box that the cracker got to keep (major incentive, contrast this with the tight-assed billionaire company not awarding the cracker anything) and it took something like six months for a cracker to get that - and even then he didn't get root despite the root password being published, just rewrote the web-page.

    So: +5 Informative, but very bad news for Microsoft.

    My take on this latest flag day is: much too little, much too late, but it will be good if their security does improve - I'll get less constant knocking on my servers' doors from broken Borg boxen. I am still getting CodeRed and Nimda hits!

    --
    Got time? Spend some of it coding or testing
  188. Er... by leonbrooks · · Score: 1
    Why is this considered newsworthy?

    First post? (-:

    --
    Got time? Spend some of it coding or testing
  189. NT started from MICA, a VMS 5 variant... by leonbrooks · · Score: 1
    Windows NT/2000/XP started from scratch using a different model.

    The original version of NT was spelling-error-compatible with MICA, a VMS 5 variant. Microsoft did that by buying the programmers instead of buying DEC. They paid heavily for that in court later. DEC even back-ported NT drivers into VMS for a number of years. Then the usual Microsoft thing happened and they fucked it up completely. VMS could be secured to fairly deep military levels by setting a single system variable, contrast this with any released version of Windows. Microsoft even fucked up OS/2 somewhat by forcing IBM to use a "single message queue" design in it for Windows (at the time) compatibility. There is apparently no end to the reach of Microsoft's "passion fingers".

    It's also noteworthy that Unix (in the form of Xenix) and OS/2 each had their turn in the limelight as the next Great White Hope for Microsoft. That's an implicit admission that what they had at the time sucked. They never seem to learn that it sucked because Microsoft wrote it. They copied as much as they could (too much, it turned out) of the Mac GUI into Windows because Bill knew that the Windows UI sucked and Mac OS =9 didn't (in relative terms). No innovation, just degradation. Every single worthwhile piece of software ever released by Microsoft was stolen or bought from or with another company.

    Perhaps we should call this buy-the-tech process "exnovation"?

    And the process of internally degrading software should be one or more of "infessation" (as in making weary or exhausted), "invetulation" (as in making elderly) or "insenelation" (as in making senile)?

    --
    Got time? Spend some of it coding or testing
  190. Hit and run security fixing by driehuis · · Score: 1

    For example they could hunt down all uninitialized variables, resource leaks, possible buffer overflows, etc.

    I've been on the receiving end of security fixes for an Open Source tool. One day, I woke up to find a patch in the SourceForge tracker that touched roughly half the files. The majority of "fixes" addressed the use of things like strcpy in cases where actually looking at the code showed the usage was safe. What's worse, some complex encoding routines were fixed in a way that is entirely unobvious, with wrapper routines that were not documented to boot.

    And needless to say, the fixes broke the code.

    Now, if these guys had used the developer mailing list, we could have dealt with the security issues in a more constructive fashion.

    It is my observation that lack of communication more than anything is the cause of perpetuating sloppy coding.

    --

    Bert Driehuis -- All I asked was a friggin' rotatin' chair. Throw me a bone here, people.

  191. thats what I hate about database design by wadiwood · · Score: 1

    I like pick style multivalue databases because I find them more intuitive and direct.

    I dislike SQL normalised type "relational" databases where many to many relationships are resolved with annoying link tables removing you ever further from the data you actually want.

    Indirection, is that what we have with MS systems? iforget->Dos->win3.11->Win95->Win98->X P I don't include win2K because thats more of an NT hybrid which is another variety of misdirection altogether - don't let the similar names fool you.

    Now I have to go look up Butler Lampson cos I never heard of him. I like Dorothy Parker quotes...I don't care what they say about me so long as it isn't true.

    --

    -- it must be true, it's on the internet.
  192. Actually, by Anonymous Coward · · Score: 0

    it's closer to 6,000. Another interesting statistic is that 80 percent of those "coders" are openly gay. I'm not even kidding. I guess some of that has made it into their operating systems.