Slashdot Mirror


Microsoft Unveils Open Source Exploit Finder

Houston 2600 sends this excerpt from the Register about an open-source security assessment tool Microsoft presented at CanSecWest: "Microsoft on Friday released an open-source program designed to streamline the labor-intensive process of identifying security vulnerabilities in software while it's still under development. As its name suggests, !exploitable Crash Analyzer (pronounced 'bang exploitable crash analyzer') combs through bugs that cause a program to seize up, and assesses the likelihood of them being exploited by attackers. Dan Kaminsky, a well-known security expert who also provides consulting services to Microsoft, hailed the release a 'game changer' because it provides a reliable way for developers to sort through thousands of bugs to identify the several dozen that pose the greatest risk."

310 comments

  1. Bang exploitable by Anonymous Coward · · Score: 1, Funny

    !exploitable Crash Analyzer (pronounced 'bang exploitable crash analyzer')

    LOL

    Damn you microsoft! For the next few months I won't be able to read the "not" operator without giggling.

    1. Re:Bang exploitable by NeverVotedBush · · Score: 4, Funny

      I think this might explain some of Microsoft's buggy code issues.

      Every time they see "!=" they interpret is as "bang equals". That sounds like definitely equals, doesn't it? Like, dude, those are so equal it's not even funny, equal.

      No wonder they have all those buffer overflow exploits. Their logic checks that include the not modifier are all wrong.

    2. Re:Bang exploitable by Anonymous Coward · · Score: 2, Funny

      Bang Exploitable Crash Analyzer, programmed in C Pound Point Net.

    3. Re:Bang exploitable by Anonymous Coward · · Score: 0

      This is just the first of a series of products released with the prefix !. There're going to be !Pod, !Mac, !Phone, etc.

    4. Re:Bang exploitable by Nerdfest · · Score: 1

      That would be 'C Octothorpe Point Net' you insensitive clod.

    5. Re:Bang exploitable by Cederic · · Score: 1

      Although being from the UK I'm doomed to forever misname yet another MS technology.

      Please tell me Pling-Exploitable wasn't written in C-Hash?

    6. Re:Bang exploitable by CarpetShark · · Score: 1

      Every time they see "!=" they interpret is as "bang equals". That sounds like definitely equals, doesn't it? Like, dude, those are so equal it's not even funny, equal.

      You obviously haven't worked there for a while. Lately, they've recoded many of these bang statements with symbolic names and less confusing operators, to more accurately convey their meaning. All such checks now read:

      if ( state == not_even_funny ) {
              continue;
      }

  2. Open Source?! Wait for it... by Macthorpe · · Score: 2, Funny

    'hellfrozeover' tag in 3... 2... 1...

    --
    "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
    1. Re:Open Source?! Wait for it... by vadim_t · · Score: 2, Insightful

      Definitely not.

      Microsoft doesn't have anything about open source actually. They're perfectly fine with the BSD for instance, which they can incorporate in their products. They're also fine with their own "shared source" deal, which goes from "non commercial" to "you can only look at it".

      What MS really despises is the GPL. They can't use it, and can't buy the source out in many cases. Of course they could technically use it, but they could apply the "embrace and extend" tactics, and would have to give out any improvements.

    2. Re:Open Source?! Wait for it... by Anonymous Coward · · Score: 0

      It's released under the Ms-PL, which is OSI-approved.

      guess that makes you +1 wrong.

    3. Re:Open Source?! Wait for it... by koiransuklaa · · Score: 2, Interesting

      Wrong? Maybe... Note that MS-PL is not compatible with GNU GPL. That may have been just a coincidence from other requirements they had, but it may also have been #1 requirement for all MS-* licenses.

      As far as I can tell MS-PL is exactly like BSD license, except it has a clause that makes it GPL-incompatible. MS-RL is very much like GPL plus a clause that makes it GPL-incompatible. I notice a trend here and it fits parents comment quite well.

      Note that I'm not saying everything needs to be GPL-incompatible, I'm just pointing out an important feature in these license.

    4. Re:Open Source?! Wait for it... by Anonymous Coward · · Score: 0

      So what? The viral GPL license is not the only one that makes your software free.

    5. Re:Open Source?! Wait for it... by Anonymous Coward · · Score: 0

      uh, I meant Note that I'm not saying everything needs to be GPL-compatible of course.

    6. Re:Open Source?! Wait for it... by LingNoi · · Score: 0

      No I think the MS-PL have patent waivers as well which is why they didn't just go with BSD in the first place.

      I say "i think" because I haven't read the license since it was first published.

    7. Re:Open Source?! Wait for it... by causality · · Score: 3, Interesting

      So what? The viral GPL license is not the only one that makes your software free.

      What you say is factually correct yet it misses the point entirely. I like benefit of doubt so I'll assume that you were not being deliberately obtuse. If Microsoft really wanted to release source in a way that is useful for the community, then they would be compatible with the GPL or would simply use the unmodified GPL. They know very well that the vast majority of Free Software, especially that which is available for Unix-like operating systems, is GPL.

      So a developer who maintains GPL software has two choices regarding the code that Microsoft releases. The first choice is to ignore it and avoid using it, because I would certainly expect Microsoft to vigorously pursue anyone who violates their license. The second choice is to abandon the GPL and release the software under the Microsoft license so that Microsoft's code could be incorporated into the project. This has two benefits for Microsoft. At the very least, they can talk a good game about how "open" they are becoming while actually doing very little for the community. At the most, they can tempt people to stop using the GPL.

      The GPL and Free Software in general is perhaps Microsoft's first experience with a potential competitor that they cannot buy out and cannot embrace-and-extend, so their huge resources and preferred tactics are rendered useless. Either they just give up or they realize that they cannot use the "direct approach". I would not expect them to just give up. The saying that comes to mind is "if you get into bed with Microsoft, you're going to get fucked." Anyone who really believes that Microsoft has had a change of heart and is now a trustworthy ally of Free Software is frankly rather naive. You're dealing with an entity that became so dominant in its industry by means of shrewd business decisions and Machiavellian strategy. I would expect a close-source software company with even half of their willingness and ability to dominate to see Free Software as an implacable enemy that requires new tactics. If anyone believes it could possibly be otherwise, the evidence against you is strong but I'd like to know why you feel that way.

      --
      It is a miracle that curiosity survives formal education. - Einstein
    8. Re:Open Source?! Wait for it... by Anonymous Coward · · Score: 0

      Non-sequitur much? The person you responded to didn't say a thing that related to anything that you posted. You just wanted to slam Microsoft for no reason.

      The GPL is not open source since it isn't truly free like BSD license is, btw.

    9. Re:Open Source?! Wait for it... by lordtoran · · Score: 1

      Well, it's only a screenful and every second word is "patents". The word "freedom" doesn't occur a single time. Further, it doesn't mandate access to the source code, which worries me even more.

      --
      Want to hear the voice of GOD? cat /boot/vmlinuz > /dev/dsp
    10. Re:Open Source?! Wait for it... by Macthorpe · · Score: 1

      Microsoft doesn't have anything about open source actually.

      Except for the Ms-PL that I mentioned above, which is an OSI-approved open source license.

      What was your point, exactly?

      --
      "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
    11. Re:Open Source?! Wait for it... by Anonymous Coward · · Score: 0

      Who cares if it's GPL compatible? Being GPL compatible is not the qualifier for what is and what isn't open source.

      As for the rest of your post, you hate Microsoft and therefore anything associated to them. You fail to understand that not everyone feels this way.

    12. Re:Open Source?! Wait for it... by Anonymous Coward · · Score: 0

      You're dealing with an entity that became so dominant in its industry by means of shrewd business decisions and Machiavellian strategy..

      I resent that.

      --Nicola Machiavelli

    13. Re:Open Source?! Wait for it... by Kalriath · · Score: 4, Insightful

      If Microsoft really wanted to release source in a way that is useful for the community, then they would be compatible with the GPL or would simply use the unmodified GPL.

      Oh bullshit. Something doesn't have to be GPL to be useful for the community - take FreeBSD for instance. Demons, GPL zealots are as bad as Apple zealots!

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    14. Re:Open Source?! Wait for it... by Anonymous Coward · · Score: 0

      In an ideal world, all open-source software would be released under BSD, in order to get maximum exposure (BSD projects cannot easily import GPL code). I don't buy into the idea that a project would die because someone forked it, changed it, and then sold the closed-source derivative. That would not make the original BSD code disappear off the face of the earth, nor would it disallow anyone from modifying the original BSD code to mimic the closed-source project's new functionality (if it's even worth mimicking).
      The other nice thing about BSD is that it's so incredibly simple. The entire license text fits in a single page on a standard terminal (80x25 characters), so you don't need to be a lawyer to understand its implications.
      It's simple and boring, and doesn't really make good cocktail party conversation. Maybe that's why it gets overlooked...

    15. Re:Open Source?! Wait for it... by Moofar · · Score: 0

      If Microsoft really wanted to release source in a way that is useful for the community, then they would be compatible with the GPL or would simply use the unmodified GPL.

      Oh bullshit. Something doesn't have to be GPL to be useful for the community - take FreeBSD for instance. Demons, GPL zealots are as bad as Apple zealots!

      BSD is GPL compatibile you idiot. GPL compatibility is far more important than most people realize. Its the most important question about any license after knowing whether its open or closed source. http://en.wikipedia.org/wiki/License_compatibility

    16. Re:Open Source?! Wait for it... by not+already+in+use · · Score: 1
      You open source zealots are fucking hilarious.

      The first choice is to ignore it and avoid using it, because I would certainly expect Microsoft to vigorously pursue anyone who violates their license.

      Yeah, and what would happen if MS was found using GPL'd code in their software?

      So Microsoft can't use GPL code, and you're totally cool with that. But as soon as GPL'd code can't incorporate MS OSS, it's some sort crime against humanity? Do you realize how stupid this is?

      Microsoft is a business. GPL'd software is their competitor. If they want to start releasing OSS software, why would they release code that their competitor could use freely, while they couldn't touch their competitors code. Do you see the stupidity in your complaint? I think it's great that Microsoft is joining the open source game, and I sure as hell don't blame them for being smart about it.

      --
      Similes are like metaphors
    17. Re:Open Source?! Wait for it... by causality · · Score: 2, Insightful

      You open source zealots are fucking hilarious.

      If you believe that recognizing the strategic aspects of Microsoft's business decisions makes one a zealot, then you are fortunate. You are fortunate because you have never seen a real zealot.

      Yeah, and what would happen if MS was found using GPL'd code in their software?

      The same thing that would happen if a Free Software developer were found using Microsoft's non-GPL code in their GPL software: a legal problem. The incompatibility of the licenses is mutual and I never suggested otherwise. Thus, I'm not sure what you believe you are explaining to me.

      So Microsoft can't use GPL code, and you're totally cool with that. But as soon as GPL'd code can't incorporate MS OSS, it's some sort crime against humanity? Do you realize how stupid this is?

      Microsoft can use GPL code if they want, they just have to honor the GNU Public License. They have chosen not to do that, which is their prerogative. Microsoft can't (legally) use GPL code in their closed-source software, and I am "totally cool with that," yes. Free Software developers who release software under the GPL can't (legally) use Microsoft's non-GPL code, and I am "totally cool with that" too. I never claimed it was a crime against humanity. I claimed that there are consequences which work together to make sure that this situation doesn't do very much to benefit the Free Software community and that Microsoft, since they are not stupid, knows this. You do know that the purpose of Open Source is so that other developers can actually use the code, right? Your reaction is out of proportion to what I was saying and I suspect that you know it.

      Microsoft is a business. GPL'd software is their competitor. If they want to start releasing OSS software, why would they release code that their competitor could use freely, while they couldn't touch their competitors code. Do you see the stupidity in your complaint?

      But that's exactly my point. GPL'd software is indeed their competitor and shrewd businesses, such as Microsoft, don't assist their competitors. That's why it doesn't make much sense to celebrate Microsoft's "open source" when it's "open source" that most of the community cannot use. Open Source that you can't actually use might as well be closed source. That wasn't a complaint, by the way, it was an observation.

      The observation is very simple. The point of the GPL is freedom. Most Free Software developers use the GPL for that reason. Microsoft cannot profit from this. Microsoft then releases non-GPL-compatible code. Free Software developers cannot use Microsoft's code without losing the full freedoms of the GPL. Thus, it would be a mistake for them to do anything but ignore Microsoft's code because the price for using it is too high. If there is any part of that which you do not understand or which looks like I am "complaining about a crime agianst humanity", you let me know and I'll clear it up for you.

      I think it's great that Microsoft is joining the open source game, and I sure as hell don't blame them for being smart about it.

      I don't really "blame" them because I would have to blame them for being true to the nature of a corporation. Their position is easy to understand and the actions they are taking are predictable. What I question is the "greatness" of Microsoft "joining the open source game" when they are doing it in a way that ensures that the existing "players" of the "open source game" cannot utilize their contributions. It's a PR move, plain and simple. Good PR for Microsoft and a way to tempt developers away from the GPL might be a reason for Microsoft and its stockholders to celebrate but it's not a reason for anyone else to celebrate.

      Microsoft has produced code that is "open" in name only and is actually all-but-useless for develo

      --
      It is a miracle that curiosity survives formal education. - Einstein
    18. Re:Open Source?! Wait for it... by tbogart · · Score: 2, Insightful

      "... nor would it disallow anyone from modifying the original BSD code to mimic the closed-source project's new functionality "

      How do you make that leap? As I mention above, neither BSD or public domain prevents the commercial vendor (or an individual for that matter) from copyrighting their deltas. Were you to do something similar, it is an open question whether they would have a court case against you. Worse, of course, if they got a software patent.

      "It's simple and boring, and doesn't really make good cocktail party conversation. Maybe that's why it gets overlooked..."

      Uh, yeah, I am SO sure that is why IBM, HP, Oracle, etc, etc choose to participate in GPL projects, even though BSD has been around so much longer. Couldn't have anything to do with the guarantee of a level playing field. I think you nailed it. It must be the cocktail party conversation value ......

      Damn, I see bold, itallic, where is irony?

    19. Re:Open Source?! Wait for it... by MrResistor · · Score: 2, Insightful

      So Microsoft can't use GPL code, and you're totally cool with that.

      What an asinine assertion! Of course MS can use GPLed code, just like anyone else can. They just have to abide by the terms of the license... you know, just like anyone else.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    20. Re:Open Source?! Wait for it... by Kalriath · · Score: 1

      You're right, and not. GGP was claiming that if Microsoft cared about Openness, they'd use GPL. Which is wrong, because BSD is just as open (perhaps more so) and isn't GPL. So why must something be GPL to be open? Or even GPL-compatible for that matter? Lots of licenses aren't GPL compatible - including other versions of itself! Does that make them not open? I propose that the answer to this is: no.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    21. Re:Open Source?! Wait for it... by not+already+in+use · · Score: 1

      demonizing me and calling me "zealot" and other names because I dared to make observations and support them with reason

      Sorry, your long winded response isn't going to convince me otherwise. The article and summary simply stated that Microsoft had released open-source software, which they did. You're an evangelist of a particular open source license that has all sorts of religion behind it, preaching down other licenses that don't align themselves with your principles. To say that nobody will find this useful is ridiculous. Sure, your "community" might not have any use for it. What is it with your community and their sense of entitlement?

      --
      Similes are like metaphors
    22. Re:Open Source?! Wait for it... by not+already+in+use · · Score: 1

      Ok -- So what you're saying is that Microsoft should change its entire business model to cater to the GPL folks. See, what you're suggesting is asinine.

      --
      Similes are like metaphors
    23. Re:Open Source?! Wait for it... by MrResistor · · Score: 1

      I never said any such thing. You said they couldn't use it, as if the open source community would immediately start filing class action lawsuits if they even expressed an interest in doing so, which is simply not true.

      The simple fact is that Microsoft has the same access to GPLed code as anyone else does, and there is absolutely no reason why it should be otherwise. If their ideology prevents them from taking advantage of that fact, then that is nobody's problem but their own, and they are free to write their own code.

      If you meant that they would get smacked if they were caught using GPLed code in violation of the license then, again, that's the same as anyone else would be treated in that scenario.

      There's no special treatment for MS going on here. The code is offered under certain terms, and they are free to accept those terms or not use the code, just as you are free to accept the terms of the Windows EULA or not use Windows.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    24. Re:Open Source?! Wait for it... by not+already+in+use · · Score: 1

      The simple fact is that Microsoft has the same access to GPLed code as anyone else does, and there is absolutely no reason why it should be otherwise. If their ideology prevents them from taking advantage of that fact, then that is nobody's problem but their own, and they are free to write their own code.

      EXACTLY. That's my point! See, here's the problem -- Microsoft isn't the one complaining that they can't use GPL code. It's the GPL folks complaining that they can't use MS OSS code. Why? Because of idealogical differences.

      So just like you say, GPL folks have the same access to Microsoft's open code as everyone else. Their ideology prevents them from taking advantage of that fact.

      --
      Similes are like metaphors
    25. Re:Open Source?! Wait for it... by causality · · Score: 2, Insightful

      demonizing me and calling me "zealot" and other names because I dared to make observations and support them with reason

      Sorry, your long winded response isn't going to convince me otherwise. The article and summary simply stated that Microsoft had released open-source software, which they did. You're an evangelist of a particular open source license that has all sorts of religion behind it, preaching down other licenses that don't align themselves with your principles. To say that nobody will find this useful is ridiculous. Sure, your "community" might not have any use for it. What is it with your community and their sense of entitlement?

      Eh let's make one observation that should be fairly obvious: if not for the success of Open Source software under the GNU Public License, of which the most prevalent expression is the GNU/Linux operating system and its associated applications, then Microsoft would not now show any interest in publically releasing any code of theirs. As much as they talk of innovation, and as many new things as they have genuinely innovated, Microsoft is just following someone else's lead on this one.

      So, Microsoft sees an existing community based on the ideals of Open Source software. This is an active, vibrant community that continues to grow. That community has largely standardized on the GPL. Thus, there is already an established and widely-used way to do this. Microsoft sees that and does it another way. That cannot be an accident. It is obvious that any incompatibility is deliberate. The reasons you gave are adequate to explain it; GPL is a competitor.

      So I sign onto Slashdot and I see a story about this. Then what do I see? I see people coming from a largely Linux background discussing the merits of Microsoft's code as though it were of any use to them. My message was for them, that this is not the community contribution from Microsoft that they may have been expecting. This is, in fact, a PR move. Companies make PR moves expecting that people who see them will be impressed by them. I'm not. Knowing that any good feelings I may have had about this were carefully engineered by someone in Microsoft's marketing department really ruins them for me. I don't know how I could more simply explain this to you.

      Now, I see the GPL and I find that it works. The Free Software community did not just arbitrarily choose the GPL because they rolled some dice. The GPL works and it works for a reason. It provides everything you need to have this sort of community based on the free exchange of ideas. Thus, I am not an evangelist, no more than I am an "evangelist" for aspirin if I tell you that it will make a headache go away. Further, you have a screwey definition of "entitlement". When I say "this is not useful for the community" that is not a statement of entitlement. Now, if I said "this is not useful for the community and this is some sort of crime" then THAT would be entitlement. Now that someone has illustrated the difference for you, you can avoid this sort of confusion in the future.

      In reality, people like you are a dime a dozen. You think you know the first thing about me, including what I believe, how I am motivated and why I might say what I say. Like most of your kind, you don't realize that I am the world's foremost expert on what I think, so even when I tell you that your assumptions about me are wrong, you continue to argue. That you presume to know where I am coming from better than I would know this, and without claiming any sort of psychic powers, is quite amazing. This, by the way, is why the Open Source community often discourages its more religious advocates -- people like you can't tell the difference between a real fanatic and someone who merely appreciates freedom, and yet you feel entitled to paint with a very broad brush. I'd like to see what you as an individual look like when you jump off of this bandwagon.

      Get a little d

      --
      It is a miracle that curiosity survives formal education. - Einstein
    26. Re:Open Source?! Wait for it... by not+already+in+use · · Score: 1

      In reality, people like you are a dime a dozen. You think you know the first thing about me, including what I believe, how I am motivated and why I might say what I say.

      What you say defines the perception of your character. You appear no different than most people on slashdot, seemingly intelligent yet pigeon-holed by an ideology that cripples your ability see the world (specifically the technology industry) in an objective manner. All things corporate and CSS are inherently bad (specifically Microsoft), while all things GPL and FOSS are inherently good. This is not true. Both have led to innovations. There is *nothing* wrong with owning sole rights to your source code and profiting from your hard work. There is nothing fundamentally wrong with either ideology.

      Your assertion that Microsoft's OSS intentions are simply a ploy because they don't use the GPL are ridiculous and short-sighted. Microsoft is, after all, a business and as such using a license that essentially offers their competitors the ability to freely use their code, while Microsoft would not be able to incorporate others' GPL code into their own products, would be an entirely counter-productive business practice. Now, before you go make the argument that, "Yes, Microsoft could use GPL'd code if they just GPL'd their own code," let's assess the absurdity of such a statement. Besides issues regarding other licensed source code in their products, it would require them to adopt an entirely different business model, which not only would be far less profitable, but the process alone would incur massive costs. The bottom line is that YES, Microsoft could use GPL if they were to change their ideology, just the same as GPL software could use MS OSS if they were to change their ideology. My problem, in particular with your argument, is where do you get off saying that the GPL is a holy standard that others must adhere to?

      --
      Similes are like metaphors
    27. Re:Open Source?! Wait for it... by causality · · Score: 2, Insightful

      My problem, in particular with your argument, is where do you get off saying that the GPL is a holy standard that others must adhere to?

      That's quite trivial, though "holy" is your word, not mine. You just can't get over the fact that someone can appreciate freedom, including software freedom, without being a zealot and so you feel the need to insert words that I clearly never used. Feel free to perform a text search on this thread if you don't believe me; you won't find me calling it "holy" anywhere, nor will you find me saying that anyone "must" adhere to it. That you feel a need to do this is a position of weakness that you'll abandon once you see the folly of it for yourself.

      To answer your question: the majority (perhaps a plurality) of all Open Source software is licensed under a version of the GPL. When I say "community" below, I refer to every Linux distribution and almost every piece of Linux software as well as cross-platform Free Software such as FireFox and all of the associated programmers and users. All of those either directly use or derive some benefit from the GPL. The reasons for the GPL's prevalence are not difficult to discern; it provides everything you need for the free exchange of ideas and prevents others from removing those freedoms. That's why the growth of available Free Software skyrocketed when the GPL was adopted, in a way that it did not with the existing BSD-style licenses.

      In other words, it works and it works well and among members of the community it is widely used. That's exactly why I make the self-evident observation that if someone wants to do something for that community, they would do so under the GPL or at the very least, a license that is compatible with it. From there it follows that it was not Microsoft's intention to allow this community to derive any benefit from its code. That is emphatically not a statement that they should have done otherwise; it is a simple observation. Thus, the community has no reason to celebrate Microsoft's published source code. To you or me, Microsoft's business position is obvious; unfortunately, some people are a bit naive and need to have this pointed out. Thus, the purpose of making this claim was to correct the growing misconception that Microsoft is ever going to be an ally of Free Software, which is a stricter term than "Open Source".

      That was my sole claim. So far you've addressed 2-3 claims I never made. That you can do that without feeling silly should give you pause. It's somewhat rare but you are not the first to do this whom I have encountered. At any rate, your choice now is to either address that claim or to set up another straw man consisting of claims I never made and then proceed to attack that straw man. If you do, I'll see the weakness of the tactic and the desperation to feel "right" that drives it and I'll observe this knowing that it is beneath you. Now, I challenge you to either demonstrate why my reasoning is flawed or admit that zealots are not known for correct reasoning. You are unable to perform the former and you're prideful enough to have a difficult time with the latter, obvious though it should be.

      I'm interested in how you resolve the dilemma. If you want to continue down the path you are already on, you could try a little harder to make this into a personal matter. If so, you will fail because that isn't tempting for me no matter how belligerent you get, but it's the only "third option" you have other than just deciding not to respond at all. I think you can do much better than the desperation you have shown so far, but that's not very important unless you also think so.

      I think this whole argument between us occurred because you could already see Microsoft's business position and its implications on your own. To you that was obvious, and it should be, but there is a great deal of ignorance concerning basic business strategy and those who already understand it were not my target audience. Mayb

      --
      It is a miracle that curiosity survives formal education. - Einstein
    28. Re:Open Source?! Wait for it... by not+already+in+use · · Score: 1

      Maybe you have encountered zealots before and now you think there's one hiding behind every corner, as though they have traumatized you in some way.

      I did have to laugh at this. Slashdot is a traumatizing place if your goal is reasonable and objective discussion. Part of my fun here is pointing out the ironies in peoples arguments.

      So now that you've made the mistake, you feel committed to it no matter how useless that is.

      This is something I pride myself in not being. I (try to) let my thoughts and views on anything everything evolve as time goes on. As far as arguing against points you never made? Yes, I was. Perhaps because I'm arguing against the FOSS, or more appropriately RMS mindset, not necessarily you in particular. But I do admit that I made assertions about you and your viewpoint that weren't necessarily true. So for that, I'm sorry.

      Now, back to the issue at hand. It is important for people to understand the differences and incompatibility of GPL vs Ms-PL. On the other hand, it is also important to understand why this is necessary from Microsoft's perspective. Lets not rain on their parade -- It is a step in the right direction.

      --
      Similes are like metaphors
    29. Re:Open Source?! Wait for it... by causality · · Score: 1

      did have to laugh at this. Slashdot is a traumatizing place if your goal is reasonable and objective discussion. Part of my fun here is pointing out the ironies in peoples arguments.

      To me, that is a challenge, not in the sense of a contest but in the sense of exploring what is possible. The challenge is to bring reason and objectivity, and things higher still than those, into discussions where they otherwise would be absent. The art is to do that in a self-evident way that can show reason to the unreasonable, or to show that a thing is true on its level but that there are higher perspectives available. It's a most rewarding thing to do.

      This is something I pride myself in not being. I (try to) let my thoughts and views on anything everything evolve as time goes on. As far as arguing against points you never made? Yes, I was. Perhaps because I'm arguing against the FOSS, or more appropriately RMS mindset, not necessarily you in particular. But I do admit that I made assertions about you and your viewpoint that weren't necessarily true. So for that, I'm sorry.

      Pride is an obstacle as much as it's an ally. You just summed up how it may be an ally. I'll show how it's an obstacle. I think you suspected early on the truth in what I was trying to tell you. What I perceive as the theme of this thread is that you were testing me to see if I would be found wanting. Note that people rarely do things like this consciously and deliberately. Possibly you've heard lots of things that sounded really great, except they came from people who were no less miserable than you, no stronger than you, no more compassionate than you, so you reason quite rightly that their beliefs haven't done them much good. If I lost my patience with you and became insulting or angry or anything like that, it would mean that I was found wanting. It is difficult or maybe even impossible to accept truth from people who are found wanting. Pride is the reason why you felt a need to test what could have been directly known in what you may call an intuitive sense.

      I've said before that you are intelligent; to me that is easy to discern. The problem with intelligence is that it alone is not enough. Please pardon the expressions I use to explain this; this is how I once explained it years ago to a friend of mine. I'll illustrate: if you take a belligerent, angry, conceited fuck and give him intelligence, what will happen is that he or she will become better at being a belligerent, angry, conceited fuck. No breakthrough will be made that will refine the person's character or bring about anything like true wisdom. That's one of the least-understood aspects of intelligence, cleverness, high IQ, whatever you call it. It's the folly of our exclusive reverence for it.

      I appreciate that you have what it takes to make the admission you just made. It takes some courage to do that. I can now explain how wisdom and real compassion protect you from succumbing to the foibles of others and replicating their mistakes. You said "I'm sorry" but had you asked me to forgive you, I would tell you that there is nothing to forgive. I see things that are true and I call them by their proper names, to the best of my ability -- that is discernment. What actually makes human beings suffer needlessly is quite different. I never judged you in the first place, so I never condemned you as a person and I never got angry or upset with you. That means I never suffered because of anything you said or did. Thus, there is no injury to be forgiven.

      Namaste. May you find real joy and the guidance of true inspiration. If life suddenly becomes simple and effortless because you yourself are not doing anything, then you've found them.

      --
      It is a miracle that curiosity survives formal education. - Einstein
  3. auto-hack or brute force? by Gothmolly · · Score: 4, Insightful

    Does this bombard all exposed functions with garbage data and look for overflows, or does it actually comb source code, look for off-by-one bugs and try to outwit the code by using boundary conditions? It's nice for Kaminsky to praise his pimps, but how does this tool really differ from any of the other leak-detectors and bug-finding tools that already exist?

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:auto-hack or brute force? by interiot · · Score: 4, Informative

      The article mentions it does fuzz testing, so it'd be the former.

    2. Re:auto-hack or brute force? by Anonymous Coward · · Score: 1, Funny

      They also don't say they've run any of it on Microsoft products or standards before...

      Quite a few(think SMB) could have used a bit of fuzz-testing before the ink dried.

    3. Re:auto-hack or brute force? by Anonymous Coward · · Score: 0

      how does this tool really differ from any of the other leak-detectors and bug-finding tools that already exist?

      Because it changes the game, man. Read the summary, at least.

    4. Re:auto-hack or brute force? by Wodin · · Score: 2, Informative

      The article mentions it does fuzz testing, so it'd be the former.

      Actually, the article says it's used during fuzz testing, not that it does fuzz testing.

      It's a Windows debugger extension that's used during fuzz testing[...]

      It sounds more like an automated crash dump analyzer used after a fuzzer has caused the program to crash.

      --
      -- Wodin
    5. Re:auto-hack or brute force? by Anonymous Coward · · Score: 0

      you're confused - this is not a bug finding tool, once you *already have a bug*, this guesses if it's exploitable or not.

    6. Re:auto-hack or brute force? by Effugas · · Score: 4, Informative

      Sup Goth, this *is* Dan.

      !exploitable isn't about finding bugs -- it's not a fuzzer, it's not a static analyzer, etc. It's about looking at a crash and saying, "Heh, this isn't just a Null Pointer Deref, you got EIP." Sure, that's obviously exploitable to you, but to some junior tester, that's not obvious at all.

      That's why it's a game changer. The dev writing the buggy code can't just say, meh, prove it's exploitable. Now the tester can point out the output of !exploitable and say, prove Microsoft is wrong. Shifts the burden of proof in the exact direction you'd want.

    7. Re:auto-hack or brute force? by harlows_monkeys · · Score: 1

      Does this bombard all exposed functions with garbage data and look for overflows, or does it actually comb source code, look for off-by-one bugs and try to outwit the code by using boundary conditions?

      Neither. RTFA, where your questions are answered.

    8. Re:auto-hack or brute force? by Ed+Avis · · Score: 1

      It still seems a bit pointless. If you have a null-pointer bug, just fix it and move on. It's not worth worrying about whether it is exploitable or not: a bug is a bug.

      I suppose it might influence the decision of whether to push out a patch. But even there I prefer the Linux approach of issuing an advisory for anything that might possibly be a vulnerability, even if no obvious exploit yet exists. Maybe on Windows installing updates is more likely to break things or require reboots (empirical data needed here) so there is a greater cost in making a bugfix release of software?

      --
      -- Ed Avis ed@membled.com
  4. I'm feeling quite dizzy... by Anonymous Coward · · Score: 4, Funny

    Microsoft has released an open source product that detects security flaws in code... my irony detector just exploded. :)

    1. Re:I'm feeling quite dizzy... by Anonymous Coward · · Score: 0

      I guess the first app they need to run this against is windows

    2. Re:I'm feeling quite dizzy... by mail2345 · · Score: 2, Funny

      Which just causes the finder to crash.

    3. Re:I'm feeling quite dizzy... by Anonymous Coward · · Score: 0

      No you read the article wrong, Microsoft product designed to create security flaws in open source software.

    4. Re:I'm feeling quite dizzy... by noidentity · · Score: 1

      Nono, it only finds exploits in open-source code. Microsoft code is safe from this evil tool. It's just another way they are attacking open source!

    5. Re:I'm feeling quite dizzy... by carlmenezes · · Score: 1

      +1. I hope they were NOT using this themselves before release - a negative track record has gotta be the worst recommendation.

      Then again, maybe its a beautiful tool, but they misused it, relying on it too heavily. Then when it didn't fix all their problems and they ran out of ideas to improve it, they decided to open source it, coz we all know that's what a company does when they need ideas they don't want to pay for.

      Or maybe Ballmer threw a chair at the guy responsible for this product after all the negative press M$ got for security. Maybe the project was declared "no good". Then Ballmer, in a fit of genius, thought of poisoning the open source well by adding this one to the drinking water.

      Uh Steve, if you're reading this, I bet you're shifting uncomfortably in your chair...or maybe I should start writing conspiracy theories :)

      Oh the possible scenarios .... hehe.

      --
      Find a job you like and you will never work a day in your life.
    6. Re:I'm feeling quite dizzy... by Zwicky · · Score: 1

      No, it's still running. Some poor Microsoft developer is still going through the results.

      "Your code has an exploitable bug. Cancel or Allow?"

      --
      "Three eyes are better than one" -- Lieutenant Columbo
    7. Re:I'm feeling quite dizzy... by oftenwrongsoong · · Score: 2, Interesting

      Nono, it only finds exploits in open-source code. Microsoft code is safe from this evil tool. It's just another way they are attacking open source!

      You know what's incredibly funny? If they did use an evil tool to uncover every exploit in open source code, to make the FOSS community look bad, they'd be shooting themselves in the foot because the bugs would get fixed at warp speed. Beyond the initial "bad" publicity they'd generate for FOSS (there's no such thing as bad publicity), the joke would be on them because they'd still be stuck with their bugs but we'd be free of ours. :-)

    8. Re:I'm feeling quite dizzy... by Anonymous Coward · · Score: 0

      Is your woody or stony detector still working though?

  5. Things that make you go hmmm... by Anonymous Coward · · Score: 5, Funny

    Could Microsoft be purposely trying to confuse people and associate the terms "open source" and exploits?

    1. Re:Things that make you go hmmm... by Anonymous Coward · · Score: 0

      Thats what I thought when Half Life "Source" was released.

  6. Direct link to explanation by DavidR1991 · · Score: 5, Informative
    1. Re:Direct link to explanation by Ken_g6 · · Score: 2, Insightful

      Naturally, that's an OOXML file that OpenOffice doesn't quite display properly. Outline view seems to be the best.

      --
      (T>t && O(n)--) == sqrt(666)
    2. Re:Direct link to explanation by Anonymous Coward · · Score: 0

      This file contains a virus, right?

    3. Re:Direct link to explanation by HappySmileMan · · Score: 1

      It contains really insecure software, it's a "learn by doing" exercise, much more effective than traditional presentations

    4. Re:Direct link to explanation by Anonymous Coward · · Score: 0

      There's a presentation that explains how it works: http://download.microsoft.com/download/7/2/8/728FE40F-93B6-47BD-B67D-78D04B63E27D/Automated%20Security%20Crash%20Dump%20Analysis.pptx

      sweet! a new leaked windows 7 serial key!

  7. AFAICT, Neither by spaceturtle · · Score: 2, Informative

    They talk about what to do when a bug is discovered. My understanding is that beta testing may result in thousands of crash reports. Clearly you'll want to prioritize fixing the exploitable crashes before the non-exploitable ones. It seems this software is to help you do that, although the article is short on technical detail.

    1. Re:AFAICT, Neither by krappie · · Score: 1

      Am I the only one that thinks it's ridiculous we still have programs crash? It's 2009, why are we still programming in C? It's certainly possible to have the same speed and low level expressiveness and include assurances against crashes and buffer overflows.

    2. Re:AFAICT, Neither by Hurricane78 · · Score: 1

      That's why I am very happy to completely steer around C/C++. I never liked its messy syntax anyway. ^^
      I used Pascal, Java, and now Haskell. And in 20 years of experience, I never have seen such an impressive beast of a compiler as the GHC (Glasgow Haskell Compiler).

      Sure, you can fuck up things in Haskell too. But you have fuck up explicitely. By doing something very stupid. Not by not doing tons of checks right and left.
      I also found the tradeoff of slowness for stability in Java, a good thing. But Haskell simply gets to the core of the problem, instead of fixing something that is bad at it's core.

      But I must say, that for operating systems, drivers, and the like, there is no alternative to C and a bit of assembler. Not for speed reasons (as this is a thing of optimization, and you can use assember anyway), but because C was made for such low-level things.

      (I am a high-level (of abstraction) programmer, so naturally, this is my POV. I do not consider any level of abstaction better. I think it depends on the level your code is meant to run at.)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    3. Re:AFAICT, Neither by krappie · · Score: 1

      Yeah, there isn't really an alternative to C for low level things, which is what bothers me. It seems like an alternative language is the obvious solution to huge classes of security problems.

      ATS looks interesting, they even have a paper on writing linux device drivers in ATS. Maybe the alternative will turn out to be ATS, or maybe BitC, but it needs to hurry up and people need to start abandoning C/C++.

    4. Re:AFAICT, Neither by shutdown+-p+now · · Score: 1

      They talk about what to do when a bug is discovered. My understanding is that beta testing may result in thousands of crash reports. Clearly you'll want to prioritize fixing the exploitable crashes before the non-exploitable ones.

      When it's Microsoft we're talking about, it's not just for beta testing. Remember that dialog about "Your application has crashed. Send information to Microsoft?" that happens every time something segfaults on WinXP+? That pretty much sends the minidump of the crashed process to MS if you click "Yes" (unless the publisher of the application has subscribed with MS to receive crash reports for it). Now, can you imagine the volume of that? Clearly some automated tools are needed to deal with all this; I guess it's one of them.

    5. Re:AFAICT, Neither by TuringTest · · Score: 1

      people need to start abandoning C/C++

      Won't happen anytime soon. Developers can be extremely conservative people (in the traditionalist sense) when it comes to their programming environments.

      --
      Singularity: a belief in the "God" idea with the "demiurge" relation inverted.
    6. Re:AFAICT, Neither by gtall · · Score: 1

      Does Haskell have a development system yet? Last time I checked, there wasn't even a debugger.

  8. It's nice to see... by rlanctot · · Score: 3, Funny

    Microsoft releasing their internal tools finally. I myself am waiting for their '!MakePortedAppsSuck' and '!CrushAllResistance' apps with baited breath...

    1. Re:It's nice to see... by Quothz · · Score: 3, Funny

      with baited breath...

      Speaking of Microsoft and security, I think you've picked up a worm.

    2. Re:It's nice to see... by TheRaven64 · · Score: 2, Funny

      And the fact that they start the executable name with an exclamation mark shows us why Windows is so buggy; they secretly all use RiscOS internally and only pretend to eat their own dogfood.

      --
      I am TheRaven on Soylent News
    3. Re:It's nice to see... by Anonymous Coward · · Score: 1, Informative

      bated
      adjective (in phrase with bated breath)
      in great suspense; very anxiously or excitedly : he waited for a reply to his offer with bated breath.
      ORIGIN late 16th cent.: from the past participle of obsolete bate [restrain,] from abate .
      USAGE The spelling : baited breath instead of bated breath is a common mistake that, in addition to perpetuating a cliché, evokes a distasteful image. Before using the expression bated breath, think of the verb : abate, as in : the winds abated, not fish bait.

    4. Re:It's nice to see... by Blakey+Rat · · Score: 0, Offtopic

      If you ever find either of those tools, please give it directly to Apple's iTunes department post-haste.

    5. Re:It's nice to see... by Kalriath · · Score: 1

      Don't forget Quicktime.

      Please don't forget Quicktime.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  9. Libre? by Toe,+The · · Score: 1

    OK, so the source is viewable, but does it qualify as free software as in freedom?

    Or is that a senseless question anyway since it runs under Windows?

    1. Re:Libre? by Macthorpe · · Score: 5, Informative

      It's released under the Ms-PL, which is OSI-approved.

      --
      "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
    2. Re:Libre? by Anonymous Coward · · Score: 1, Informative

      Or is that a senseless question anyway since it runs under Windows?

      To answer the rhetorical question, yes it is a senseless question and the software is not really free. Here's an article on such a situation http://www.gnu.org/philosophy/java-trap.html

    3. Re:Libre? by LingNoi · · Score: 1

      Is that the license OSI approved which got a lot of flak because it says the source can only be run on windows or did they remove that use clause from their OSI licenses?

      I don't keep up to date on such things so I am generally interested.

    4. Re:Libre? by poetmatt · · Score: 1

      The proper way to say it is "it's not open source compatible (gpl/others)", and even OSI knows that.

      Just because its close in name, doesn't mean it's still not as proprietary as possible.

      This is like putting an open source bumper sticker on a car and saying it's open source.

    5. Re:Libre? by larry+bagina · · Score: 5, Informative

      The GPL isn't open source compatible with most other open source licenses, either.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    6. Re:Libre? by Anonymous Coward · · Score: 1, Informative

      "it's not open source compatible (gpl/others)"

      Since when has Open Source and GPL been synonymous? BSD comes to mind....

    7. Re:Libre? by 99BottlesOfBeerInMyF · · Score: 4, Informative

      Is that the license OSI approved which got a lot of flak because it says the source can only be run on windows or did they remove that use clause from their OSI licenses?

      No. Those are the MS-LPL and MS-LRL licenses. The MS-PL license is fairly innocuous excepting the patent clause which is debatable. It allows the distribution of the source under this license and distribution of binaries for commercial use with a different license.

    8. Re:Libre? by janwedekind · · Score: 4, Interesting

      The GPL maximises protection against software patents and forbids distribution as proprietary-only software. The Ms-PL minimizes protection against software patents and forbids distribution as libre-only software. The Ms-PL formally fulfills the requirements for an OSI approval but apart from that it is everything what you would expect a license from Microsoft to be. To understand the Ms-PL just imagine the Venn diagram for the following equation: MsPL = ( OSI - GPL ) & Microsoft

    9. Re:Libre? by Raenex · · Score: 3, Insightful

      You mean, "It's from Microsoft! It must not be labeled as open source, even if it is!"

      If you aren't saying this, then maybe you can say in what aspect the license doesn't meet the Open Source Definition

      .

    10. Re:Libre? by ClosedSource · · Score: 1

      In other words, the GP is right.

    11. Re:Libre? by ClosedSource · · Score: 0, Flamebait

      Nobody said that the code was "free as in redefined by GNU".

    12. Re:Libre? by Anonymous Coward · · Score: 0

      Or is that a senseless question anyway since it runs under Windows?

      To answer the rhetorical question, yes it is a senseless question and the software is not really free. Here's an article on such a situation http://www.gnu.org/philosophy/java-trap.html

      And GCJ is still a piece of shit.

    13. Re:Libre? by janwedekind · · Score: 1

      Yes. The motivation for making the GPL incompatible is a totally different one.

    14. Re:Libre? by Anonymous Coward · · Score: 0

      Atleast that's what they say, but who trust Stallman?

    15. Re:Libre? by oftenwrongsoong · · Score: 3, Informative

      Or is that a senseless question anyway since it runs under Windows?

      SVN runs under Windows. GCC runs under Windows. Gimp runs under Windows. Apache runs under Windows. Hell, just about any project with a configure script will either compile for Windows as-is, or will after slight modifications. FOSS has nothing to do with whether it runs under Windows or not.

    16. Re:Libre? by mrsteveman1 · · Score: 1

      In other words, the GPL is incompatible with many open source licenses, BUT "we're trying to change the world, so it's ok"

    17. Re:Libre? by janwedekind · · Score: 1

      The GPL license is just about protecting individuals who want to develop and use software in freedom. It's up to you to take advantage of this protection or not.

    18. Re:Libre? by tjstork · · Score: 2, Insightful

      The GPL license is just about protecting individuals who want to develop and use software in freedom. It's up to you to take advantage of this protection or not

      The best protection is public domain. Retaining ownership to force an ideological end is silly. The GPL was born out of emacs getting "ripped off" by other people... but did that stop emacs at all? Nope, we're still stuck with it, even though everyone knows vi is better....

      --
      This is my sig.
    19. Re:Libre? by Anonymous Coward · · Score: 0

      GPL isn't really free. It force-feeds GPL.

    20. Re:Libre? by bh_doc · · Score: 1

      The MS-PL license is fairly innocuous

      I first read that as "insidious". My /. brainwashing is coming along nicely. :)

    21. Re:Libre? by janwedekind · · Score: 2, Insightful

      But the current legal system allows coercion by means of patents, technical restrictions, ... The GPL is not by any means more silly than the environment in which it is being used.

    22. Re:Libre? by Anonymous Coward · · Score: 0

      "libre-only software" - well that's what happens when you define words to suit a political agenda. The MS-Pl forbids re-licensing under another open source license because of the hypocrisy of some GPL folks who took BSD code and wouldn't contribute back. Now, yes, BSD allows this, but that attitude stunk and was very childish.

      However you are talking crap - if we take "libre" as "software that can be used, studied, and modified without restriction, and which can be copied and redistributed in modified or unmodified form either without restriction, or with minimal restrictions only to ensure that further recipients can also do these things" then the MS-Pl meets every single criteria set out. That "or" is a tricky thing.

    23. Re:Libre? by mcgrew · · Score: 1

      The best protection is public domain.

      In some instances, yes.

      Retaining ownership to force an ideological end is silly

      Your straw man is on fire; it has nothing to do with ideology, everything to do with practicality. If you place your work in the public domain, a commercial vendor can freely use your code to compile a binary, and then copyright the binary that was compiled with your code. He then "owns" (actually has a limited time monopoly) the product of YOUR work with out compensating you.

      The GPL protects the individual programmer against the corporation that would use him and abuse him.

      Nope, we're still stuck with it, even though everyone knows vi is better....

      IWNFTT, espacially such an old one

    24. Re:Libre? by ShieldW0lf · · Score: 1

      The GPL license is just about protecting individuals who want to develop and use software in freedom. It's up to you to take advantage of this protection or not

      The best protection is public domain. Retaining ownership to force an ideological end is silly.


      So, ditch the ownership laws. Then it's all public domain. Easy. Get on the phone to your representative and make it happen...

      --
      -1 Uncomfortable Truth
    25. Re:Libre? by Anonymous Coward · · Score: 0

      ooooooooh the gpl folk stole bsd and won't give back troll!!! didn't see you in a long time, how'd you fare? aah. the memories... the memories...

    26. Re:Libre? by janwedekind · · Score: 2, Insightful

      If you look for hypocrisy, you should probably have a look at other license before criticising the GPL. Also you must have a distorted view of the situation if you criticise GPL developers for incorporating BSD code, but at the same time you are completely oblivious of the fact that entire software companies are making money from selling modified BSD software without contributing back.

    27. Re:Libre? by Zero__Kelvin · · Score: 1

      "The GPL isn't open source compatible with most other open source licenses, either."

      I like open source compatible mashed potatoes. WTF? Only on Slashdot could a sentence be modded informitive and insightful in spite of the fact that it doesn't even parse, and makes absolutely no sense even if you try to afford the benefit of the doubt.

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    28. Re:Libre? by Zero__Kelvin · · Score: 1

      "In other words, the GP is right."

      You are close to the mark. The GP would definitely have to use other words to be right ;-)

      Unfortunately your comment is not open source compatible with other open source comments made elsewhere in this thread.

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    29. Re:Libre? by Zero__Kelvin · · Score: 2, Insightful

      Holy shit. This is getting ridiculous. People, get a clue. Licenses are different. If they weren't we wouldn't need to throw all of these plurals and license names about. There would be just one Open Source license (OK, two. The original, and the one M$ embraces and bends^H^H^H^H^H extends.)

      The definition of Open Source compatible is not: a license which can be used interchangeably with any other Open Source license.Some licenses are compatible with each other and others aren't. It is called freedom of choice, which is what FOSS encourages and promotes.

      Holy shit I'd like to hit some of you with a serious clue stick right about now ...

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    30. Re:Libre? by tbogart · · Score: 1

      "The GPL isn't open source compatible with most other open source licenses, either."

      In that sense, no open source license is compatible with any other - since each is trying to do something _slightly_ different.

      If they all said the same thing, they wouldn't be different licenses would they?

      Yet, there is quite a range of "differences". Some licenses are quite similar and some wildly different.

      Your statement is without useful meaning.

    31. Re:Libre? by tbogart · · Score: 1

      "... but who trust Stallman?"

      Who cares. Read what it says.

      Of course, if you would look at the history, revisions and the very fact that _you_ choose the version that _you_ feel best fits the philosophy, it is hard to argue about trust.

      It just isn't _necessary_ to take advantage of the result.

    32. Re:Libre? by tbogart · · Score: 1

      "The best protection is public domain."

      As has been pointed out numerous times, public domain is no "protection". BSD is no "protection". Either allows someone else to claim ownership of code changes based on your work. Maybe you are a week away from similar - even better extensions, but if they beat you to copyright, you are hosed.

      And since when did "emacs getting "ripped off" by other people" have anything to do with him getting started in open source? Seems the published account that has been around all these years somehow missed that ....

    33. Re:Libre? by sumdumass · · Score: 1

      The GPL protects the individual programmer against the corporation that would use him and abuse him.

      Not really, I could do all of the above while keeping it GPL compatible and there is nothing that could be done. There would be no need to compensate the programer or anything under the GPL. The only difference is that if I changed anything, then I would have to make those changes availible. But if I gave those changes only to my customers, you wouldn't get them without either finding a customer willing to give it away or buying the product yourself. It's the same effect.

      It's more about Ideology then anything else. You have convinced yourself it's different because you believe in the Ideology, that's the biggest difference.

  10. This is M$ double speak for "Finding Free Sofware" by Anonymous Coward · · Score: 0, Interesting

    The threat free software has to your buddies at M$ is astronomical. This is the reason M$ will do anything ion their power to remove all free softwre from M$ Winblows, which includes the use of M$'s new tactic of removing free software and using multiple accounts to back the story. The only way to eliminate the M$ exploits is to use free software instead of non-free software, or any software from M$.

    --
    Friends don't help friends install M$ junk.
    Friends do assist M$ addicted friends in committing suicide.

  11. Re:This is M$ double speak for "Finding Free Sofwa by gcnaddict · · Score: 3, Insightful

    Your comment loses all credibility not so much because of your lack of evidence but because of your use of "M$."

    Also, your suicide joke wasn't funny.

    --
    Viable Slashdot alternatives: https://pipedot.org/ and http://soylentnews.org/
  12. I'm not a programmer... by Quantos · · Score: 1

    But it almost sounds to me like the users are supposed to run this and then report their findings.
    Do the people that run it get a paycheck? Or is that the part that's open source?
    Aren't there other programs that also do this? If so(I really can't imagine that MS are the first to release something like this), then how is this news?

    --
    Some people are only alive because it's against the law for me to hunt them down and kill them.
    1. Re:I'm not a programmer... by Anonymous Coward · · Score: 0

      The summary say "identifying security vulnerabilities in software while it's still under development", where do you get the idea that it's intended for end users?

    2. Re:I'm not a programmer... by Quantos · · Score: 1

      Is beta testing not considered part of the development process?
      True, most end users aren't interested in running beta tests. However MS always seems to manage to leak their software early, I'm assuming it's to get more testing done by the public.

      --
      Some people are only alive because it's against the law for me to hunt them down and kill them.
    3. Re:I'm not a programmer... by LingNoi · · Score: 1

      It's open source so everyone wins, not just Microsoft.

  13. pronounced 'bang exploitable crash analyzer' by c.derby · · Score: 2, Funny

    ...or as i prefer to call it, "bang beca."

    --
    -- derby
    1. Re:pronounced 'bang exploitable crash analyzer' by Anonymous Coward · · Score: 0

      Yeah, it sounds less like a Microsoft name than something that Miguel came up with for his open source knockoff.

      - and I heard that a Hong Kong filmmaker is suing Microsoft, seems the name was already taken.

  14. People in glass houses... by AnalPerfume · · Score: 0

    ...only see Windows.

    "Now, Microsoft wants to help secure third-party applications that run on top of Windows."

    Microsoft can't even secure their OWN stuff, what makes them think anyone can take them seriously when they try to secure third party stuff? Who knows, maybe it will make third party stuff more secure, which puts the blame back onto Microsoft for every exploit. It will just enhance the fact that the best way to make Windows secure is to use as little Microsoft software as you can on it. It may also backfire on them if people start wondering why they don't use their little tool to make Microsoft software more secure too. If they do, will the difference be noticeable? Will people get noticeably fewer malware infections per week?

    1. Re:People in glass houses... by BenoitRen · · Score: 1

      Most malware infections are thanks to the vulnerability between the keyboard and the chair.

      So no, we won't see less infections with a securer Windows.

  15. interesting excerpt from bang source code by Anonymous Coward · · Score: 5, Funny


    int assess_severity( struct* bug )
    {
        string vendor = get_application_vendor( bug );
        if ((vendor == "Google") ||
            (vendor == "Adobe") ||
            (vendor == "Mozilla"))
              return MAJOR_RISK_UNINSTALL_IMMEDIATELY;
        else if (vendor == "Microsoft")
              return TRIVIAL_SECURITY_RISK;
        else
              return MODERATE_SECURITY_RISK;
    }

    1. Re:interesting excerpt from bang source code by Anonymous Coward · · Score: 0

      I suppose they're right about Adobe :p

    2. Re:interesting excerpt from bang source code by Anonymous Coward · · Score: 0

      Software + Customers (Innocence & Ignorance) = Microsoft Business

    3. Re:interesting excerpt from bang source code by mach1980 · · Score: 2, Funny

      The funny thing is that the function is violating at least two MISRA C rules and don't even check for null-pointer argument :)

      Sorry if I come across as an asshole. I'm currently working to raise the code quality at my company and see similar code every day. It gives me the itch...

      --
      Break the sound barrier - bring the noise.
    4. Re:interesting excerpt from bang source code by Cederic · · Score: 1

      Unless == has been overloaded to do something silly, there are no null pointer exceptions possible in this method.

      get_application_vendor can be easily written to successfully return without errors irrespective of the parameter passed to it, and the rest of the code makes no assumptions that vendor is non-null.

      Unnecessary null pointer checking is crufty and should be avoided. Your unit tests should include passing a null parameter and will thus catch any incorrect handling should someone subsequently introduce a bug anyway.

    5. Re:interesting excerpt from bang source code by mach1980 · · Score: 1

      I couldn't agree with you more. Did I mention that not all projects even have unit-tests? *sigh*

      Problem is that we're just using intra-procedural static code checks on code modules used by many projects. That implies that any tainted data or call outside your module should be checked.

      We're currently evaluating programs to try to find more elaborate problems using flow-sensitive static analysis etc. Got any tips?

      --
      Break the sound barrier - bring the noise.
  16. There's already proof that this can't work by mark-t · · Score: 1

    It's called Turing's halting problem.

    1. Re:There's already proof that this can't work by spydabyte · · Score: 4, Informative

      That's proof that it can't always work. Not that it never works.

    2. Re:There's already proof that this can't work by MoralHazard · · Score: 2, Insightful

      Has anybody every told you "'Perfect' is the enemy of 'good enough'."? Perhaps after listening to you explain why your project is behind schedule, then sighing and face-palming?

      The halting problem says that there cannot be a GENERAL ALGORITHM that works in all cases, for any of the infinity of possible programs that can exist.

      That proves ZERO about, say, whether I can write an algorithm that covers 99% of the common cases. The lack of a general solution doesn't imply that it can't be done often enough, in practice.

    3. Re:There's already proof that this can't work by mark-t · · Score: 0

      What's 1% of infinity? It can't work.

    4. Re:There's already proof that this can't work by mark-t · · Score: 2, Insightful

      And just like anti-virus software, it will lull people into a false sense of security that can easily result in catastrophe

    5. Re:There's already proof that this can't work by aslate · · Score: 1

      No, all it states is that it cannot prove the program is bug free. It can, however, keep running and finding as many bugs as possible.

      If you get to a stage where you don't find bugs after a long enough period of time, you've probably reached the limits of that particular testing method's ability to provide any useful data about the application. That or the bugs are now awkward to find and probably won't be found by the majority of user input either.

      On the halting problem basis, users will never find every bug in an application either, so lets not fix them!

    6. Re:There's already proof that this can't work by Zironic · · Score: 1

      What part of the word "common" are you unable to comprehend?

    7. Re:There's already proof that this can't work by Anonymous Coward · · Score: 0

      I bet you don't use lint either, because it doesn't catch every possible problem?

    8. Re:There's already proof that this can't work by TwilightXaos · · Score: 1

      Because the majority of crash-inducing bugs don't result in security vulnerabilities, there can be a fair amount of internal debate when they're discovered during development.

      a repeatable tool that takes a look at a crash

      Both of the above quotes indicate that the tool does not determine when a program will crash. It only analysis the crash after a tester/developer has found a bug that makes the program crash.

      This is not the halting problem, but a more ambiguous problem of weather a specific crash inducing bug is a security risk, or just a bug.

    9. Re:There's already proof that this can't work by TheRaven64 · · Score: 1

      The halting problem is solvable in the general case if you restrict the inputs to finite programs running on finite inputs (any such program can be represented by a DFA, and then you just have a graph colouring algorithm to find non-terminating states). Although this is a tiny subset of the infinite number of possible programs, it does include all programs that can run on computers that will fit inside the universe, which is a sufficiently large set for most uses (of course, in some cases, you will need a computer with more memory than can fit on a single planet).

      --
      I am TheRaven on Soylent News
    10. Re:There's already proof that this can't work by Paradise+Pete · · Score: 5, Funny

      And just like anti-virus software, it will lull people into a false sense of security that can easily result in catastrophe

      Exactly. That's why I'm also against railroad crossing gates, smoke detectors, and those silly "Bridge Out" warning signs.

    11. Re:There's already proof that this can't work by mark-t · · Score: 1

      And what part about "infinity" do you? There's no such thing as "common" in an infinite field of possibilities, everything is infinitesimally rare.

    12. Re:There's already proof that this can't work by mark-t · · Score: 1

      I use lint because it makes my code more consistent and accordingly easier for others to understand not because it will catch problems that haven't happened yet.

    13. Re:There's already proof that this can't work by Zironic · · Score: 1

      Since you're mentally challenged I'll spell this out for you. The set of common cases is not infinite, especially since the creator of the algorithm gets to define "common".

      Did you flunk the part of automata where they explained that not all sets are infinite and there exist such a thing as a finite subset of an infinite set?

    14. Re:There's already proof that this can't work by mark-t · · Score: 1

      Not all sets are infinite, but the set of possible algorithms is, and no finite subset of them can represent a "common" case except with respect to what has been done _so far_, which considering the exponential rate at which knowledge is growing, is only liable to represent an obsolete minority of actual cases after a measure of time that is hardly proportional to the effort involved in detecting those cases.

    15. Re:There's already proof that this can't work by MoralHazard · · Score: 1

      You incorrectly assume that "an infinite number of different programs" and "all possible programs" are the same set. They are not.

      Turing's proof shows that no algorithm can solve the Halting Problem for *all possible* programs. But there ARE proven algorithms that solve the the Halting Problem for certain classes of programs, that is, subsets of "all possible" programs.

      Many of those subsets (all the interesting ones, really) containg an infinite number of possible programs. Not *all* possible programs, mind you--just an infinitely-large subset of another distinct, infinitely-large superset.

      (Please read the Wikipedia page on infinity, and grok the part about different sizes of infinity, before we continue. Don't worry, I've got time.

      Got it? Good.)

      Also, you wrote "...in an infinite field of possibilities, everything is infinitesimally rare." This statement is mathematically absurd--obviously, you've never taken probability, so you don't know how to talk about it in a useful way. Let me demonstrate:

      There are an infinite number of possible lengths--the entire real number space, right? But not all shoelace lengths are all equally probable in that space. I'd guess that more than 99% of all shoelaces are shorter than 1 meter--my local drug store doesn't stock anything longer than about 75 cm.

      Now, does that mean that my drugstore's policy "can't work"? Of course not--it works fine, they make a profit. If a clown with giant shoes needs mile-long shoelaces, nobody cares. It's perfectly useful to only solve 99% of the possible cases, right?

      Back to programs: IF you define the probability distribution of human programmer output as totally random, you'd have a point. But humans don't bang out random strings of gibberish machine instructions like monkeys at typewriters. We tend to follow certain well-worn paths, and some of these subsets have proven Halting Problem-solvable. Tools that implement those insights aren't "general algorithms", but they're still useful.

      Go read up on tools like Electric Fence, and other automated debugging aides. This is not a new concept, and you should really learn more about the subjects (math, software). It's embarrassing, for you.

    16. Re:There's already proof that this can't work by mark-t · · Score: 1

      First of all, as a minor nitpick, tools like electric fence don't detect problems before the program actually does something it's not supposed to. But secondly, and more importantly, athough you gave a reasonable example of how there is only a finite range of shoelace lengths that are practical, you also seem to assume that there are similarly finite dimensions to the assortment of possible algorithms that can be utilized in useful programs. This is not remotely proven.... or even particularly likely. Computers are a very recent development in human history. Given that knowledge and information are being exchanged at exponentially rising rates, we cannot possibly have not even made a significant scratch in the surface of what is possible, or even particularly probable.

    17. Re:There's already proof that this can't work by leomekenkamp · · Score: 2, Insightful

      Hmmm. Most people do not know how computer viruses work. Installing anti-virus software can lull people in a false sense of security since they also do not know how the anti-virus software does (not) work, but hey, it's not called 'anti' for nuttin, right?

      Railroad crossing gates are intuitive for most people: train may pass by crushing and killing you, so such a crossing calls for extra attention automatically.

      Smoke detectors do not cause most people to suddenly leave their burning candles unattended or to start playing with matches.

      'Bridge out' warning signs call on the viewer to pay extra attention.

      So, anti virus software makes ppl less attentive, railroad crossings and warning signs make ppl more attentive and smoke detectors do not alter behaviour. I am afraid I fail to see your point.

      --
      Wenn ist das Nunstueck git und Slotermeyer? Ja! Beiherhund das Oder die Flipperwaldt gersput.
    18. Re:There's already proof that this can't work by HappySmileMan · · Score: 1

      you also seem to assume that there are similarly finite dimensions to the assortment of possible algorithms that can be utilized in useful programs. This is not remotely proven.... or even particularly likely. Computers are a very recent development in human history. Given that knowledge and information are being exchanged at exponentially rising rates, we cannot possibly have not even made a significant scratch in the surface of what is possible, or even particularly probable.

      So the software works for many common cases PRESENTLY, and it gets UPDATED in the future.

    19. Re:There's already proof that this can't work by MoralHazard · · Score: 1

      "...athough you gave a reasonable example of how there is only a finite range of shoelace lengths that are practical..."

      NO. That's NOT what I did.

      I demonstrated that:
        * While there is a THEORETICALLY INFINITE RANGE of possible theoretical shoelace lengths;
        * Nonetheless, the probability distribution of actual shoelace lengths assigns a non-infinitessimal (and rather large) probability to a finite (and rather small) range of lengths.

      Do you remember WHY that's important? It's because in your previous post, YOU CLAIMED that:

      "...in an infinite field of possibilities, everything is infinitesimally rare."

      Which is just utter horseshit. You denied the existence of uneven probability distributions--seriously, what the fuck is wrong with you?

      You are now, officially, squirming like a fish on a hook. You have been owned at every comment, by pretty much everybody, probably because your math training is well below average for Slashdot.

      You can keep trying to sneak your way out of this argument, so you can maintain your fragile sense of self-worth, but nothing will change the fact that you got your ass royally whooped.

      Go back to school, kiddo, and pay more attention in class.

    20. Re:There's already proof that this can't work by mcgrew · · Score: 1

      As with antivirus software or bulletproof vests, if it doesn't ALWAYS work it might as well never work.

    21. Re:There's already proof that this can't work by mcgrew · · Score: 1

      And just like anti-virus software, it will lull people into a false sense of security that can easily result in catastrophe

      Exactly. That's why I'm also against railroad crossing gates, smoke detectors, and those silly "Bridge Out" warning signs.

      Unlike this MS tool or antivirus, the things you mention always work. They give you REAL security rather than a false sense of it.

    22. Re:There's already proof that this can't work by mark-t · · Score: 1

      I wasn't actually trying to argue with anybody.... and it's been pointed out to me far more politely than you have done above that my overgeneralization was inaccurate (at the time I had made that statement, I was thinking of the set of reals compared to the set of real vectors, where no matter how large of a set of reals you take, the set of vectors will always be infinitely larger). My original point remains, however. There is no general solution to the problem that Microsoft is claiming to have found... and to make that sort of claim strikes me as little more than hype.

    23. Re:There's already proof that this can't work by Paradise+Pete · · Score: 1

      the things you mention always work.

      While admittedly much more often than antivirus software, and my reply was mostly in jest, those things can still impart a false sense of security:

      Ok I'm too lazy^H^H^H^Hbusy to continue, but googling smoke detector malfunction would probably yield a story or two. BUt like I said, it was mostly in jest. And the "bridge out" thing, well, I needed a third item and couldn't think of anything better :-)

  17. In related news by Anonymous Coward · · Score: 0

    Windows 7 is delayed 8 months, and Vista is being recalled...

  18. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  19. Re:This is M$ double speak for "Finding Free Sofwa by Megane · · Score: 1
    --
    #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  20. The first thing Microsoft should do with it by Anonymous Coward · · Score: 0

    is run it against explorer.exe and find out why explorer.exe is such a stinking piece of shit application. If there has been one thing in every version of Windows since 95 that has caused me to nearly lose my temper and smash something so many times it is explorer.exe. Freezing, glacier slow with networks and networked drives, and other assorted annoyances like taking the goddamn task bar and desktop out when having to kill the explorer.exe process in Task Manager. Every time one of those things happens in XP, I'd love to smack Ballmer in the face with a chair.

    1. Re:The first thing Microsoft should do with it by Anonymous Coward · · Score: 0

      Kill yourself!

  21. THOUSANDS OF BUGS? by v1 · · Score: 0, Flamebait

    Dan Kaminsky, a well-known security expert who also provides consulting services to Microsoft, hailed the release a 'game changer' because it provides a reliable way for developers to sort through thousands of bugs to identify the several dozen that pose the greatest risk."

    Maybe I'm just totally out of touch here, but for my development, finding the bugs is the time consuming part, fixing them usually goes pretty quick. I welcome anything that helps find my bugs, that saves so much time. If your code is so decrepit that this tool is going to find "thousands" of bugs, you need to go back to school for awhile.

    Given a tool like that, I'd be running it regularly and not just addressing the "important" bugs. Making that thing pass clean would be one of the steps in my development cycle.

    Or maybe he's just speaking more about a common windows programming philosophy? (I certainly hope not)

    --
    I work for the Department of Redundancy Department.
    1. Re:THOUSANDS OF BUGS? by MoralHazard · · Score: 4, Insightful

      How large of a programming team do you work with? And how big are the projects to which you contribute code? And what kind of development model do you use (waterfall, Agile, ad-hoc, etc.)?

      Shipping a large project with 1,000 bugs might be a perfectly valid decision. Are any of those 1,000 bugs deal-breakers for your install base? If so, how many clients does it affect? Are these "real bugs", or just incomplete/unpolished functions, or documentation issues, or output typos, or what?

      And what kind of software is this? Are you building a time & expense web application, or a filesystem driver? In the former case, most bugs will be interface glitches--ugly, annoying, and harmless. In the latter case, even one bug could easily cause silent data corruption.

      Remeber what Linus Torvalds said: Release early, release often. Don't wait til all your bugs are fixed before shipping your software, or you'll lose your "market" window. If it's good enough, the early-adopters will understand, and might even contribute bug reports or patches that will speed you up.

    2. Re:THOUSANDS OF BUGS? by owlstead · · Score: 1

      Thousands of bugs? They must have tested it against their office suite :)

      But seriously, Microsoft must have loads of legacy code lying around, so thousands of bugs are to be expected. Office just happens one of them (and the number of Word related crashes on my office computer is just about hopeless).

    3. Re:THOUSANDS OF BUGS? by v1 · · Score: 2, Interesting

      Shipping a large project with 1,000 bugs might be a perfectly valid decision

      Why don't we just change that to Shipping a large project with 1,000 bugs might be a perfectly valid business decision

      I don't ship crap.

      And if I had a really large project, I still wouldn't ship crap. Too many pinheads cutting corners to save a buck, particularly on large projects, because they count that an an excuse and want to rush it out the door ASAP to start generating revenue. Not me thank you very much. Just because there's a fair number of vendors that play that game doesn't mean it's the rule.

      I still can remember back to the days when "version one-point-oh" didn't always have to mean "train wreck, we'll start seriously fixing bugs around 2.5". Today's translation works as follows: Today's 1.0 is yesterday's early beta. Today's 2.0 is yesterday's Still Beta. Today's 3.0 is yesterday's 1.0.

      Software should work out of the box. You shouldn't have to wait for an update or two for it to become stable enough to use.

      --
      I work for the Department of Redundancy Department.
    4. Re:THOUSANDS OF BUGS? by v1 · · Score: 1

      Remeber what Linus Torvalds said: Release early, release often. Don't wait til all your bugs are fixed before shipping your software, or you'll lose your "market" window. If it's good enough, the early-adopters will understand, and might even contribute bug reports or patches that will speed you up.

      I forgot to address this. Yes, early adopters and capturing your market are important. I can see where "version 1" could be considered beta for the purposes of getting your foot in the door. I don't think anyone expects a polished product on 1.0. But I'm talking about things that have gotten a ways. I mean, Windows SEVEN? Come on, by now everyone expects you to have your act together. You should already have your market carved out. Nobody is "early adopting" Windows anymore. Releases should be solid by 3. There is no excuse for a product's major releases 3+ years after initial release to be crutching themselves up on the notion of "early adopters" and "capturing market".

      --
      I work for the Department of Redundancy Department.
    5. Re:THOUSANDS OF BUGS? by jlebrech · · Score: 1

      MS have to keep the legacy bugs in there for compatibility reasons.

    6. Re:THOUSANDS OF BUGS? by scribblej · · Score: 1

      While I agree that people could do better, your overall attitude of EVERY BUG MUST GO BEFORE WE RELEASE is probably why you have to say "if I had a big project" rather than "the big project I'm on now..."

      "Software should work out of the box. You shouldn't have to wait for an update or two for it to become stable enough to use."

      Agreed, we're not talking about bugs that prevent use of the software here. Your inability to distinguish possibly hinders you professionally.

    7. Re:THOUSANDS OF BUGS? by wampus · · Score: 2, Insightful

      Not all software is a product for sale, and in the real world there are deadlines and budgets. Users can deal with bugs, business owners can't deal with late, over-budget projects.

    8. Re:THOUSANDS OF BUGS? by Kjella · · Score: 2, Interesting

      I don't ship crap. And if I had a really large project, I still wouldn't ship crap. Too many pinheads cutting corners to save a buck, particularly on large projects, because they count that an an excuse and want to rush it out the door ASAP to start generating revenue. Not me thank you very much. Just because there's a fair number of vendors that play that game doesn't mean it's the rule.

      There's a balance, there are also those people that think that perfect software can be created in some kind of bubble and you might be one of them, I think. In a large project I can assure, with 100% certainty, that between the start of the project and the final release the requirements have changed. A lot. It does not matter if you design up a perfect software development method, not that I think such a thing exists, because people are very poor at specifying in an abstract specification what it is they want to do. Sometimes they don't even know exactly how, even if you could hire a telepath at the start of the project. And thinking that all code is written after one master plan is unlikely, more likely you've bought up functionality from other companies or migrated it from legacy products and it's patchwork under the hood.

      Releasing early and getting feedback is usually the only way to get the design right. It's much better to hear "yeah umm, but that's not the way we work" or "yeah umm, but that doesn't solve our challenge" before everything's set in stone. If you get told at the very end to rip out that well tested and well integrated piece of code then all that effort is really wasted. In large development projects these kinds of communication problems are very real. You could accept lots of small issues like a house where they said "that light fixture doesn't work, but it'll get fixed in the next release". What you couldn't accept is "the foundation is quicksand, the drainage is shot and the pillars rotten". In computer terms things like "the solution can't scale, it's crashing often and we have major data loss".

      Seriously, think of all the trivial things that can be considered bugs. Typos are bugs. A non-working shortcut is a bug. I think the most trivial bug I've seen is that you have a list. A to Z will jump you to the first item starting with that letter. But Æ, Ø and Å will not. Workaround? Scroll and pick. It's a genuine bug, but like hell if it's something that should hold up a software release. On the admin side I'm more like "if there's a dark voodoo way of doing it then fine" because I'm much more interested in them fixing bugs affecting a thousand people than me. Software delivers value and bugs detract from value, but this is important - a bugfree but useless application also has no value. Something that isn't used where they put it in an Excel spreadsheet instead has no value. Developers need to be working on the right things first, then they can do them right. Sounds easy and obvious but damn how hard that is.

      --
      Live today, because you never know what tomorrow brings
    9. Re:THOUSANDS OF BUGS? by Effugas · · Score: 2, Informative

      This is Dan.

      OK, my DNS bug took two days to find, and six months to fix. I'm not sure what universe you're in; in mine, we have to actually test.

    10. Re:THOUSANDS OF BUGS? by Your.Master · · Score: 1

      You don't ship *anything*.

      Also, !exploitable can check for bugs in beta software. And it can check for bugs in internal builds. You do *not* need to have released to get bug reports on major projects -- testers, fellow developers, and even yourself can run into bugs to investigate later.

      Firefox 3.5 is supposed to have fixed over 1000 bugs so far in its release cycle, and that was supposed to be a short-cycle release -- and there are still bugs that are WONTFIX or even still active from years and years ago.

      Not to mention that anything with any sort of plugin architecture (like most browsers and operating systems) is bound to have a tonne of crashes that you can do literally nothing to prevent but you do have to filter to see if there are ones that you could prevent.

    11. Re:THOUSANDS OF BUGS? by MoralHazard · · Score: 1

      Who said we were talking about MS and Windows? You just brought that up, right now. I don't think it proves anything, one way or another, that one company has a crappy process.

      Honestly, it seems like you just tried to "move the goalposts", redefining the terms of an argument you were losing so you can feel like you're winning.

      That's lame, and I'm calling you out on it.

    12. Re:THOUSANDS OF BUGS? by MoralHazard · · Score: 1

      So... You're a perfectionist who will hold a project hostage until YOU decide, on your terms, that it's not "crap"? And anybody who disagrees with your assessment of costs versus benefits is a "pinhead"?

      Remind me to hire you, really. I love programmers who sneer at business concerns, refuse to compromise with their teams, and are so inexperienced that they believe that any business can get done that way.

      Man, if I had a whole team of guys like you, I'd be able to... Hmm. People like you actually detract from the productivity of a team. With enough of your clones running around bragging about how big their dicks are, business would grind to a halt. Hell, with a whole company of you, we could probably put global software productivity into reverse, it would be so bad.

      "...if I had a really large project..."

      I think this says it, right here, folks. If you ever you DO get on a large project, give me a call. Maybe you'll have learned enough to hire you.

    13. Re:THOUSANDS OF BUGS? by v1 · · Score: 1

      It's interesting to read how you so clearly hate the idea of someone else having control, and at the same time you want that exact same control all to yourself above the devs. That's the most common problem with the middle-management level of development, they're in charge and they're going to have it their way, all other factors be damned.

      What the development team as a whole needs is balance. I'm not saying for either side to hold things hostage, I'm just saying don't let the PHB's decide when it's "ready" based solely on a trade show date. (with props to Dilbert)

      You're almost certainly going to have to let it out the door with some issues, the trick is to get everyone together early to draw the line, and hold your ground when someone barges in with an eraser.

      --
      I work for the Department of Redundancy Department.
    14. Re:THOUSANDS OF BUGS? by wampus · · Score: 1

      So projects should be managed on the whims of the developers? I really hope I don't get hooked up with whatever failshop you work for.

    15. Re:THOUSANDS OF BUGS? by Kaboom13 · · Score: 1

      Assuming it's something I actually want to start with (aka it does something not done before on my platform of choice, or does it better then any alternatives) a program with bugs I can use now is better then one with no bugs due to be released "sometime". Obviously there's a point where bugs make it unusable, or inferior to it's more mature competitors.

      I've yet to see a single program (that actually accomplished a sophisticated task), whether its been in development for a month or 10 years, that didn't have some form of bugs. Software that never gets released, or gets released after it is obsolete, is no good to anyone. Accurately identifying and prioritizing bugs that serious show stoppers is a great tool.

    16. Re:THOUSANDS OF BUGS? by Anonymous Coward · · Score: 0

      Remeber what Linus Torvalds said: Release early, release often.

      and it's lead to the popular impression that Linux is a piece of shit. You can release your 1000 bugged program giving your product and company a bad name however I'm not stupid to do something like that.

    17. Re:THOUSANDS OF BUGS? by not-my-real-name · · Score: 1

      Have you flown on any modern commercial airliner? I can guarantee that the software, even the critical software, has bugs. The thing is, if you go to the FAA to certify some software and you tell them that there are no open problem reports, they are going to have some serious questions about your software verification process.

      Now, for every one of your open problem reports, someone has to review them, analyze them, and come up with a justification of why it's OK not to fix them. In many cases, it's better to leave a well understood bug than to try to rush in a fix at the last minute.

      The thing to keep in mind is that not all bugs are created equally.

      --
      un-ALTERED reproduction and dissimination of this IMPORTANT information is ENCOURAGED
    18. Re:THOUSANDS OF BUGS? by shutdown+-p+now · · Score: 1

      I don't ship crap.

      Bender, is that you?

    19. Re:THOUSANDS OF BUGS? by MoralHazard · · Score: 1

      "It's interesting to read how you so clearly hate the idea of someone else having control, and at the same time you want that exact same control all to yourself above the devs. That's the most common problem with the middle-management level of development, they're in charge and they're going to have it their way, all other factors be damned."

      I AM a dev, you idiot. Back when I was fresh and new and guileless, like you, I thought a lot like you. Everything I knew about development had come from two sources, CS assignments and Slashdot--I didn't even know how little I knew.

      Most of that got that beat out of me, eventually--not by management, but by other engineers who just didn't have the patience for my snotty, immature attitude.

      "What the development team as a whole needs is balance. I'm not saying for either side to hold things hostage, I'm just saying don't let the PHB's decide when it's "ready" based solely on a trade show date."

      And now you're just redefining your side of the argument because I burned it out from under you, in my previous comment. Changing your tune, now, cannot erase your previous comments. YHL, HAND.

    20. Re:THOUSANDS OF BUGS? by mcgrew · · Score: 1

      Shipping a large project with 1,000 bugs might be a perfectly valid decision

      A large project... like a car?

      I can't remember the last time I had to take my car to the dealer to fix a factory defect. You people in the software industry should be ashamed of yourselves. Real engineers laugh at the likes of you guys.

      About fifteen years ago I bought a new lawnmower. My elderly next door naighbor saw it, liked it, and bought an identical one a week later. It lasted two years (twice the warrantee), and then died from a broken piece.

      A week later my neighbor's lawnmower died from the exact same fault. Now THAT'S engineering!

    21. Re:THOUSANDS OF BUGS? by Cederic · · Score: 1

      Ha! Finally he admits it! We always knew you'd written that backdoor into DNS.

      Very clever of you given your age at the time, and the way you got someone else to front the code as their own...

      (Hmm. Now I'm wondering. You're possibly young enough that the code predates you. Now that _is_ clever!)

    22. Re:THOUSANDS OF BUGS? by Anonymous Coward · · Score: 0

      Depends on your users; if fixing that scrolling issue saves your company 10 seconds per call and you have thousands of users doing thousands of calls, it CAN be worth it.

      If you have one customer that calls once a year with à at the beginning of their surname, then, no, not really worth it.

      Cost benefit test, nothing more, nothing less.

  22. Am I the only one that already wondered... by Anonymous Coward · · Score: 0

    whether microsoft has run this app on itself? I'm waiting for the first exploit. Let me suggest that we name it "crash bang exploitable crash analyzer".

  23. Enough problems of their own by kimvette · · Score: 0, Flamebait

    This is another form of FUD, IMHO, Why not focus on finding all the exploits in their own software which results in easy installation of rootkits and spyware and other malware in their systems which results in boot times of 5 to 15 minutes, where there can be literally HUNDREDS to THOUSANDS of processes infesting the Windows platform and the Microsoft Office suite?

    I have yet to see an exploit in *nix that can't be relatively easily removed. I HAVE seen rooted boxes but they have been installed by determined crackers - on slowlaris and Linux - in those cases the exploit was able to be removed and verifying against known-clean machines has verified they were clean - in an enterprise environment at a state college. Other infections I've seen have been confined to individual user accounts, or to an individual application (apache).

    Heck, I've had a machine rooted because I did not want to update OpenSSL on one of my machines a few years ago. I had opened the machine up to the net (it was normally on a clean net but I opened it up and forgot to close the firewall after I finished testing) but even that was easily cleaned, and I verified against a backup that I had successfully cleaned the system. I did reinstall as a safeguard and finally patched OpenSSL. However that was a known-and-patched exploit that I didn't care to upgrade because it was a private machine normally inaccessible from the wild. It was the result of carelessness. I cleaned it in under 15 minutes and could have left it and been safe but I took the opportunity to upgrade to a newer distro release anyhow.

    The difference is, so many Windows apps require admin/root access that it is the normal operating mode of Windows, and one application with an exploit (MSIE and IIS in particular) can almost invariably result in the box being rooted, and Windows does not make it easy to clean. Why? Because even "safe mode" can be exploited to run processes at startup. Cleaning up the mess is a tedious process, and while BartPE or WinPE (if you have access to WinPE) do make the job a little easier, it's still a pain in the neck.

    Linux exploits usually are the result of one to three things:

    1. Carelessness: running an intentionally-or-uninentionally patched box open to the 'net. I've done this before and had to clean up the mess.

    2. User running as root - this is a surefire way to get exploited. No mainstream applications not designed for administration tasks require root access, and unlike Vista's UAC, the privilege escalation mechanisms in *nix variants/distros actually do what they are designed without being obnoxious.

    3. Sheer determination: the cracker just keeps pounding and pounding on the box using all known exploits and then turns to brute force. Eventually the user will get in unless the firewall detects the attempts because you can't stop determined douchebaggery.

    Now, as far as Windows is concerned: there are a quintillion (OK, a slight exaggeration) unpatched known exploits (some of them having been known for 10+ years), probably >99% of users run as Administrator because many applications and even some games require admin access to run, so the boxes are uber-easy to hack.

    So, why doesn't Microsoft produce these tools for Windows, so the mass populace can help identify, log steps to reproduce, and report the exploits? Why are they using their resources to create tools for testing open source software for exploits? It is so they can give windows fanbois tools to create yet more anti-Linux and anti-F/OSS FUD, pure and simple. It's not about caring about F/OSS, it's not about wanting to contribute, and it certainly is not about being a good netizen. It is entirely self-centered. And, it makes sense for Microsoft since their duopoly is in danger and they know they peaked long ago and the only direction they have to go is down, and they know it.

    --
    The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    1. Re:Enough problems of their own by Anonymous Coward · · Score: 0

      Nice tirade, but the "open source" designation refers to the exploit-finding tool, not to the programs it analyzes. In other words, Microsoft released a tool for finding exploits in programs, and this tool was released under an open-source license.

    2. Re:Enough problems of their own by Anonymous Coward · · Score: 0

      Maybe if you would RTFS before posting, you would know that this software is an exploit finder that is open source, not an exploit finder that targets open source.

      So yes Microsoft can, and should, use this tool to find exploits in their own software. The problem is they can't really brag about doing this because if the tool fails to find a lot of exploits it will be seen as a failure, but if it does find a lot, then MS will have to admit that Windows itself has been a failure, from a security standpoint.

    3. Re:Enough problems of their own by Anonymous Coward · · Score: 0

      You're misinterpreting the title.

      They released and exploit finder under an open source license, not an exploit finder for open source applications.

    4. Re:Enough problems of their own by Anonymous Coward · · Score: 0

      I think you misunderstood the title, as I did initially. The tool is an "Open source exploit finder" in the sense that it is an exploit finder which is open source, not that it finds exploits in open source software.

    5. Re:Enough problems of their own by Anonymous Coward · · Score: 0

      Wow you spent a lot of time on that comment. Unfortunately, you read the title without reading the description? The exploit finder IS open source, not FOR open source.

    6. Re:Enough problems of their own by BasharTeg · · Score: 4, Insightful

      So, why doesn't Microsoft produce these tools for Windows, so the mass populace can help identify, log steps to reproduce, and report the exploits? Why are they using their resources to create tools for testing open source software for exploits? It is so they can give windows fanbois tools to create yet more anti-Linux and anti-F/OSS FUD, pure and simple.

      Are you retarded? This tool isn't a "find exploits in open source software tool." It's an open source "find exploits in software tool". So Microsoft has an internal tool that they've developed to search for exploits in their software like Windows and Office, but they decided to open source that tool and share it with everyone else. It has nothing to do with Windows versus Linux.

      As far as your ridiculous rant regarding Windows and programs running as Administrator, if you actually looked at the most recent versions of Windows, the number of system services that run under NETWORK SERVICE and other less privileged accounts has been increased, and with UAC, running users as non-admin is actually feasible. I don't know if you'd ever tried running as non-admin under XP, but the idea of logging out and logging back in to make a change, or hoping to hell that runas will actually work, just makes no sense. In addition, their work on Protected Mode where IE runs in a sandbox is another example of MS working to implement the least privilege principle.

      Microsoft has made *considerable* progress on the non-admin front, and continues to work on that.

      Oh, and whoever modded you up for this nonsensical misinterpretation of the tool needs a meta-mod down.

    7. Re:Enough problems of their own by cybrthng · · Score: 1

      I wish i could mod you up.. i'm not sure what high horse the OP was on, but i'd like some of what he is smoking!

    8. Re:Enough problems of their own by Anonymous Coward · · Score: 0

      If you were not an obvious fanboi, I might suggest you read the article.
      But don't let the truth prevent you from spewing anti-MS zealotry.
      They are not testing open source software exploit. The tool is an MS open source tool (not GPL, their MS-pl in all likelihood). There is a difference in being an open source tool and a tool for open source.

    9. Re:Enough problems of their own by Anonymous Coward · · Score: 0

      MODS: how is this flamebait? Everything said is factually correct as far as I can tell and he's replying to a post that was full of shit. Again, how is this flamebait? I hope you mods get meta-moderated to hell.

    10. Re:Enough problems of their own by Anonymous Coward · · Score: 0

      The only insight I got from this post is how retarded and full of hate people can be for no reason.

    11. Re:Enough problems of their own by 99BottlesOfBeerInMyF · · Score: 1

      MODS: how is this flamebait?

      It can validly be considered flamebait because it starts with, "Are you retarded?" This is unfortunate because, it is factual and corrects the misconceptions of a highly modded post that is, well a little retarded. That's a harsh way to phrase it as well as offensive. In truth the original poster was not retarded, just uninformed and "ranty".

    12. Re:Enough problems of their own by DavidD_CA · · Score: 1

      Perhaps you didn't take a moment to read the article.

      The tool they developed is an exploit finder, and they made it open source.

      This is not an exploit finder for open source Linux software, OMGWTFBBQ, the sky is falling, and MS is up to their old shit again.

      Now, Microsoft wants to help secure third-party applications that run on top of Windows. Last year, the company released a threat-modeling tool and other resources designed to help software developers kick-start secure development lifecycle programs in their organizations. The idea was to package the security experience Microsoft has attained so it can serve as a sort of template for other companies.

      They took a tool that they used internally for their own apps, tweaked it to work with third-party Windows apps, and made it open-source.

      --
      -David
    13. Re:Enough problems of their own by BasharTeg · · Score: 1

      How do you know I was intending to be offensive? Perhaps I was literally asking him if he had some kind of learning disability, which would make sense considering his completely incorrect reading of the post and/or article. :)

      Hey, if Obama can get away with it...

  24. A bounty for first exploit of !exploit by PrescriptionWarning · · Score: 1

    Just wait till people get to see the code for this thing, then we'll see the true colors of their idea of security

  25. Re:Here's a better idea by FooAtWFU · · Score: 1

    Well, that's a nice idea, but it takes a finite nonzero amount of time to do so. And, during that time, if you already have a product which is out (as many people do), people may be exploiting it, and so the bugs they are most likely to exploit are probably worthy of being deemed more urgent to fix, and what bugs are more likely to be exploited than the ones you can find using automated tools?

    --
    The World Wide Web is dying. Soon, we shall have only the Internet.
  26. Re:This is M$ double speak for "Finding Free Sofwa by DrSkwid · · Score: 5, Insightful

    yeah, FOSS exploits are cuddlier

    But strange that in the 20 years I've been using Microsoft OSes, I've never had a virus or trojan or malware. I must be doing something wrong.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  27. !static code analyzer by owlstead · · Score: 1

    I would be more impressed if they released a free and open static code analyzer to include for their compilers that may also compile to native code (e.g. Visual C++).

    That said, I'll be nice and applaud this effort. But if anywhere possible, use managed code (scripting or a secure VM) instead of relying on this kind of analysis. With this rate, it will take centuries to get rid of all the buffer overflows and other rather inexcusable code out there. I would be very amazed if this tool would (help to) remove all those kind of vulnerabilities.

    This article scores an 11 on the inflammatory headline, shame on the editors for letting this get through. Slashdot seems to be getting worse (which is certainly kind of amazing).

    1. Re:!static code analyzer by LO0G · · Score: 1

      It's not "free and open" but do you mean a source code analyzer like this one which is available in Visual Studio 2005?

  28. Wow! by edivad · · Score: 0, Flamebait

    Once again, Microsoft invented the ... drum roll ... wheel!
    Fuzzy data injection is used by ages in the security world. By both bad and good guys.
    Oh, and the Address Space Layout Randomization thing, Linux had it long before them, so I guess that according to their very same rules, they invested that too.

    1. Re:Wow! by harlows_monkeys · · Score: 0

      Tip: you can avoid looking like an uninformed idiot if you RTFA before posting.

    2. Re:Wow! by edivad · · Score: 1

      Do the tinfoil hats come with the enrolling package in the Microsoft funny-boys club, or you've to build them by yourself?

    3. Re:Wow! by harlows_monkeys · · Score: 1

      Why don't you RTFA?

  29. really? by someone1234 · · Score: 2, Informative

    Are you sure, Coward?

    http://www.opensource.org/licenses/ms-pl.html

    Or you say it won't be released under ms-pl?

    --
    Patents Drive Free Software as Hurricanes Drive Construction Industry
    1. Re:really? by Anonymous Coward · · Score: 2, Funny

      Are you sure, Coward?

      Please, no need for the formality. You can call me Anonymous...

    2. Re:really? by jacquesm · · Score: 0, Redundant

      the temptation is killing me... sorry...

      "that's what she said..."

  30. Re:This is M$ double speak for "Finding Free Sofwa by mikesd81 · · Score: 1

    Or maybe you're an educated user and know what you're doing and know how to safely use the the internet and install programs. I haven't had any malware or viruses either, because I know not to install questionable programs and go to questionable sites.

    --
    That which does not kill me only postpones the inevitable.
  31. Eat your own dogfood? by v1 · · Score: 0, Troll

    Microsoft Unveils Open Source Exploit Finder

    Kind of makes one wonder why they don't oh I don't know... say... Run it on their Windows source???

    --
    I work for the Department of Redundancy Department.
    1. Re:Eat your own dogfood? by LO0G · · Score: 2, Informative

      Why do you believe that Microsoft doesn't run it on their own code?

      Remember that !exploitable is a debugger extension that is used on a crash dump to determine if it's possible that the crash was caused by an exploitable bug. It's not a source code analyzer - it's purely a post-mortem analysis tool.

      From the paper I would expect that Microsoft routinely runs this tool over crashes, especially over the crashes that are found by its internal fuzzing tests (the paper says that they ran over 350 Million fuzzing iterations in Vista).

  32. OSS bug search engine already exists! by jumper32 · · Score: 1

    http://bugspy.net/ do this already- It gatheres tens of thousands of bugs.

  33. It's Called Windows by Anonymous Coward · · Score: 0

    Microsoft's program aimed at finding and analyzing security and exploit issues is named "Windows". All version will help you do this.

  34. huh??? by iScharfschtze · · Score: 1

    N still, they dont use that in Win?! lol

  35. Valgrind? by Anonymous Coward · · Score: 0

    Haven't read TFA. Will not do, but this sounds a lot like a mixture of grep and valgrind on a bugzilla.

    If they've been sitting on this for a while, we know how good it is then.

    1. Re:Valgrind? by lordtoran · · Score: 1

      That were my thoughts exactly. They reinvented valgrind ... poorly. Nothing to see here.

      --
      Want to hear the voice of GOD? cat /boot/vmlinuz > /dev/dsp
  36. Re:This is M$ double speak for "Finding Free Sofwa by Anonymous Coward · · Score: 0

    Hi bleeding rectum.

  37. Open Source Exploit Finder? by D+Ninja · · Score: 1

    So...let me get this straight...they're open sourcing their Windows code base?

    I'm here all week. The veal is amazing!

  38. Help me understand this. by wonderboss · · Score: 1

    This tool "combs through bugs that cause a program to seize up, and assesses the likelihood of them being exploited by attackers". So we then decide whether to fix the crash or not based on whether the crash is exploitable? Anyone that buys this idea is fired.

    --
    more cowbell
  39. Re:This is M$ double speak for "Finding Free Sofwa by jav1231 · · Score: 0, Troll

    Yeah, because we all know how benevolent Micro$oft is, right?

  40. Re:This is M$ double speak for "Finding Free Sofwa by multisync · · Score: 5, Insightful

    You know, I'm starting to take issue with comments that protest the use of the M$, Micro$oft etc. memes. I know how something can get on your tits - articles that identify companies by their stock symbols is a particular irritant of mine.

    But being annoying to a given reader does not cause a comment to lose all credibility. I mean, you can judge a comment by any criteria you choose, even moderate that way if you like. But you and I can't have a conversation either, if at any time you might write off everything I've said because I violated some arbitrary boundary you have. It's like people who dismiss an otherwise intelligent comment because it was posted AC. Again, it's their prerogative, but it makes it hard for the rest of us to talk to them.

    And I am not suggesting the comment you replied to was "otherwise intelligent." The comment you replied to was obviously a troll, and should be dismissed for that reason. I would agree that a user who says something like "Winblows" isn't making any kind of lucid point with that act, but he may just be really frustrated for a good reason. Let him vent - he "paid" for that right - then see if he has an actual point.

    In defense of the use of M$ etc, I see it as sort of a short hand, like Garry Trudeau would do with politicians. A feather for Dan Qualye, a bomb for Newt Gingrich ... To a passionate free software advocate, M$ is a concise, efficient and - IMO - accurate moniker.

    In two characters, the anonymous poster - who is probably Twitter - told us all we need to know about his opinion of Microsoft. I don't think an anti-Microsoft - or anti-Google/Linux/Apple bias for that matter - invalidates anyone's opinion. If it does, good grief we're all doomed.

    BTW, I agree with you about the suicide remark.

    --
    I don't care why you're posting AC
  41. Curious to See... by Quartz25 · · Score: 1

    Has Microsoft run Crash Analyzer on Crash Analyzer?

    --
    Most people don't get why the integral of "e to the x" is so funny. Most math majors don't have a sense of humor.
  42. windbg needs PDB so app must compile in MSVS by formal_entity · · Score: 5, Informative
    It's a plugin to the windbg debugger. so that when it hits an access violation (which is MS speak for SIGSEG) you can do !expoitable and it will use some heuristics to guess whether this bug is an exploitable security vulnerability.

    Since Microsoft receives millions of crash dumps every days for every single Windows app (including third-party apps) they need hardcore bug triaging tools.

    For decades each crash they received went into the "!analyze -v" automatic bug triage tool which tries go figure out whether it's a Microsoft bug or a bug in the third-app. It also tries to classify the bug using advanced heuristics which has been refined over many years.

    Now, they have decided to do the same for security bugs as well and thus they created the !expoitable windbg plugin. This plugin has been in production use inside Microsoft for over a year already. However, they know that it doesn't matter in what application the security hole is, if a box is owned Microsoft always get's bad press regardless.

    Also note that this tool cannot easily be used to find security bugs in the linux kernel and not in linux-only apps either because you must run it inside windbg. Further, in order for windbg to be useful you just have debug symbols loaded from the proprietary debug symbol format PDB that Microsoft created, which in practice mean you must have compiled it with Visual Studio (and not mingw etc).

    So you need not just a port to windows (using mingw or similar) but you actually need to port the app to compile under MS compiler if you want to use this.

    Apps like Firefox will be able to use this tool though, they already have debug symbol server online that hosts PDB debug symbols for every single release build of Firefox.

    I absolutely think the open source community should use this tool to scan cross-platform apps but in the long term, I hope there will be a gdb plugin with similar functionality which also has heuristics geared for *nix exploits.

    1. Re:windbg needs PDB so app must compile in MSVS by Anonymous Coward · · Score: 1, Informative

      While a PDB makes windbg easier to read it is not a requirement to have one and you can get a lot of good info about a crash if you understand what your looking at in windbg, PDB's just make it a lot easier to read, a use it on crashes for apps I have no symbol files for all the time.

  43. Re:This is M$ double speak for "Finding Free Sofwa by Anonymous Coward · · Score: 0

    Hi troll

    --
    Friends don't help friends install M$ junk.
    Friends do assist M$ addicted friends in committing suicide.

  44. Rules of Open Source club by CarpetShark · · Score: 4, Funny

    1. Fork the project
    2. Change the name

    1. Re:Rules of Open Source club by Anonymous Coward · · Score: 0

      Oh yeah, OSS programmers love to fork. The problem is that you can only fork so much before everyone's working on a solo fork and the baby never comes to term.

    2. Re:Rules of Open Source club by Anonymous Coward · · Score: 0

      what.

      the.

      fork.

    3. Re:Rules of Open Source club by Ethanol-fueled · · Score: 1

      Fork you, you forking jigger!

    4. Re:Rules of Open Source club by Anonymous Coward · · Score: 0

      3. ?????
      4. Profit!

      No wait.. You can't possibly make any money if people can see your source code, duh!

  45. Re:Here's a better idea by wonderboss · · Score: 1

    You're saying you ship a product with so many crashes that you can't possible fix them all quickly? We are not just talking bugs. To quote the original post the tool "combs through bugs that cause a program to seize up, and assesses the likelihood of them being exploited by attackers". You're fired.

    --
    more cowbell
  46. WinDbg by Ralish · · Score: 1
    Aside from all the other people pointing out that your long rant is completely misguided and a result of misintepreting the article, I'm just going to address one single part of a sentence.

    So, why doesn't Microsoft produce these tools for Windows

    The tool in question is a debugger extension for WinDbg. I'm not sure how many people are debugging their Unix/Linux applications with WinDbg, but I'm guessing it's not a large number.

  47. bang exploitable or unexploitable? by hwyhobo · · Score: 1

    Not that this is important, but was it really pronounced "bang exploitable" when it started its life? It sounds to me like some top brass (or a journalist) wanted to show off that they know how "!" was pronounced in old UNIX speak, but without a real understanding of what it meant. You know, as in, "I am one of you, but I have no idea what the hell I am talking about".

    --
    End anonymous moderation and posting on /.
    1. Re:bang exploitable or unexploitable? by Curate · · Score: 2, Informative

      There's nothing mysterious about the "bang exploitable" nomenclature. That's how all the windbg extensions are commonly called verbally... bang analyze (!analyze), bang process (!process), and so on. It's been that way for as long as I can recall.

    2. Re:bang exploitable or unexploitable? by hwyhobo · · Score: 1

      Thanks for the explanation. In other words, the pronunciation of the "!" is preserved, but the meaning is different than the old "NOT". Is this just a Microsoft thing to use "!" for such extensions, or do other do it as well? I am not familiar with that convention.

      --
      End anonymous moderation and posting on /.
    3. Re:bang exploitable or unexploitable? by dbIII · · Score: 1
      It's just like their convention to use "." at the start of a word and "net" for local applications.

      In other words, irrelevant bullshit but it's their stuff so they get to pick the name.

    4. Re:bang exploitable or unexploitable? by Anonymous Coward · · Score: 0

      Bangbros, Bangthumbs ...

    5. Re:bang exploitable or unexploitable? by Curate · · Score: 1

      It's simply what you would type at the windbg prompt to invoke the debugger extension. You'd type "!exploitable" to invoke the "exploitable" extension, or "!foo" to invoke the "foo" extension. Extensions are just DLLs that get loaded on the fly when you use the "!" syntax (and anybody can create one). By corollary, built-in debugger commands don't start with a "!"; they just start with a letter or sometimes the "." character. I don't know if other debuggers use "!" for extensions or if they even support extensions in a similar way that windbg does. Incidentally when I say windbg, I mean the whole family of Windows debuggers -- windbg, cdb, ntsd, and kd. The same extensions work with all of them.

    6. Re:bang exploitable or unexploitable? by hwyhobo · · Score: 1

      Doesn't it confuse and annoy programmers at Microsoft? I am sure most of them have been around long enough to see that "!" is used everywhere to designate logical negation.

      --
      End anonymous moderation and posting on /.
    7. Re:bang exploitable or unexploitable? by Kalriath · · Score: 1

      Others do it as well. Look at the first line of a Unix script, such as a Perl script, which reads with a "#!" - which is also not used for logical negation.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    8. Re:bang exploitable or unexploitable? by hwyhobo · · Score: 1

      I understand the purpose of #!, but I was referring to using ! as part of a program's name. Oh well, not really that important. As a previous poster said, they can do whatever they like.

      --
      End anonymous moderation and posting on /.
  48. Re:Here's a better idea by 99BottlesOfBeerInMyF · · Score: 1

    Here's a better idea... Fix all the bugs and then you're sure you've fixed all the big bugs.

    Well, that's a nice idea, but it takes a finite nonzero amount of time to do so.

    You both make good points. MS's security culture is fairly awful in that when developers find bugs that are potential security issues, they have to fight the system to get them prioritized for fixes and most are considered "low risk" and ignored. Anything that helps prioritize bug fixes is good, provided it is not used a an automated way to ignore a huge number of bugs in an effort to produce a mediocre and "good enough" product in terms of security.

  49. Re:This is M$ double speak for "Finding Free Sofwa by Raenex · · Score: 3, Insightful

    To a passionate free software advocate, M$ is a concise, efficient and - IMO - accurate moniker.

    It's also meaningless, since every business is out for dollars. You might as well say $un too, and same goes for any business with an "s" in its name.

  50. Re:This is M$ double speak for "Finding Free Sofwa by jacquesm · · Score: 1

    If you don't connect your computer to the net it does not count :)

    Alternatively, it's a bit like a poker game, if you don't know who the idiot is, it's you. In other words, the chances are big that you were at some point virused, trojanned or malwared but you did not detect it.

    When adaware first came out I ran it on the machines of some friends and it was quite surprising how much crap there was on these so-called clean machines.

    Probably you install very little software on your machines, that alone would be a big factor in your favour. If you have kids around the house browsing the net with those pc's then kudos to whoever set up your AV.

  51. Re:This is M$ double speak for "Finding Free Sofwa by ClosedSource · · Score: 1

    While an argument shouldn't be cast aside just because someone uses M$, I don't agree that it is "a concise, efficient and - IMO - accurate moniker". It's really just an irrelevant and off-topic device unless the conversation is specifically about cost of software.

    It would be like constantly referring to RMS as "The Great Unwashed Guru" in a discussion that had nothing to do with personal hygiene or delusions of Godhood.

  52. Wow. Awesome headline. by Torodung · · Score: 1

    Did anyone else misread this (before reading the summary) as Microsoft is working on an automated program to find *security exploits in open-source projects*?

    Man, I had to readjust my tinfoil hat for a second there.

    --
    Toro

    1. Re:Wow. Awesome headline. by leomekenkamp · · Score: 1

      I am with you on that one; I actually thought: even MS cannot be that evil.

      --
      Wenn ist das Nunstueck git und Slotermeyer? Ja! Beiherhund das Oder die Flipperwaldt gersput.
  53. Mod down please by Blakey+Rat · · Score: 1

    Could somebody please mod this clown down? He couldn't be more wrong.

    Or, in short:

    So, why doesn't Microsoft produce these tools for Windows, so the mass populace can help identify, log steps to reproduce, and report the exploits?

    This tool is for Windows you dumbshit.

    1. Re:Mod down please by DMUTPeregrine · · Score: 1

      GP seems to be confused, thinking that because the tool is open-source it must be for debugging open-source software. It's an open-source tool for debugging ANY software, though only really useful if you have the source of the software you are debugging. But that goes for most debugging tools.

      --
      Not a sentence!
    2. Re:Mod down please by Blakey+Rat · · Score: 0, Troll

      He's not confused, he's just such an empty brainwashed open source shill he doesn't even bother to stop and think even a fraction of a second before writing out long articles full of vitriol. He's the opposite of intelligent conversation.

  54. Re:This is M$ double speak for "Finding Free Sofwa by jfim · · Score: 4, Insightful

    You know, I'm starting to take issue with comments that protest the use of the M$, Micro$oft etc. memes. I know how something can get on your tits - articles that identify companies by their stock symbols is a particular irritant of mine.

    But being annoying to a given reader does not cause a comment to lose all credibility. I mean, you can judge a comment by any criteria you choose, even moderate that way if you like. But you and I can't have a conversation either, if at any time you might write off everything I've said because I violated some arbitrary boundary you have. It's like people who dismiss an otherwise intelligent comment because it was posted AC. Again, it's their prerogative, but it makes it hard for the rest of us to talk to them.

    And I am not suggesting the comment you replied to was "otherwise intelligent." The comment you replied to was obviously a troll, and should be dismissed for that reason. I would agree that a user who says something like "Winblows" isn't making any kind of lucid point with that act, but he may just be really frustrated for a good reason. Let him vent - he "paid" for that right - then see if he has an actual point.

    In defense of the use of M$ etc, I see it as sort of a short hand, like Garry Trudeau would do with politicians. A feather for Dan Qualye, a bomb for Newt Gingrich ... To a passionate free software advocate, M$ is a concise, efficient and - IMO - accurate moniker.

    In two characters, the anonymous poster - who is probably Twitter - told us all we need to know about his opinion of Microsoft. I don't think an anti-Microsoft - or anti-Google/Linux/Apple bias for that matter - invalidates anyone's opinion. If it does, good grief we're all doomed.

    BTW, I agree with you about the suicide remark.

    I beg to differ. If you're so puerile to have the need to use "M$ Winbloze" or "open sores software" in a rational discussion, it seems as if you're trying to sidestep the issue with colorful language. Call things by their name and focus on arguments rather than taking trite potshots.

    As for identifying corporations by their stock ticker symbols, it allows to easily differentiate between corporations who would have otherwise similar names(for example, an article talking about the Royal Bank could refer to both RY and RBS) and to look them up quickly and unambiguously.

  55. why? by koutbo6 · · Score: 1

    why there aren't any erotic references to ! "bang" in the comments is beyond me.
    Am I on /.?

    --
    You speak London? I speak London very best.
  56. A related interesting project by i.of.the.storm · · Score: 1

    One of the CS professors here is working on a research project that seems to have a similar use, except it relies on binary analysis. http://bitblaze.cs.berkeley.edu/ They also made a tool to automatically generate exploits based on Microsoft patches, and I guess they're just hoping that that capability doesn't fall into the wrong hands... Professor Song is scary.

    --
    All your base are belong to Wii.
  57. Re:This is M$ double speak for "Finding Free Sofwa by causality · · Score: 1

    In defense of the use of M$ etc, I see it as sort of a short hand, like Garry Trudeau would do with politicians.

    I don't generally use "M$" but I wanted to tell you how I see it. I see it as a way to separate the petty members of the audience who cannot overlook a small and harmless "transgression" (even that word is too strong for it) from those who are less superficial. I prefer to directly deal with wrong responses so this does not tempt me, but this is something that I wish more people understood. If I wanted to apply a self-maintaining "filter" to the audience, then I would deliberately do things like this. Then they would do all of the filtering work and categorize themselves for me because the people who balk at seeing "M$" will either decide not to respond or will soon make their objection known. Either way, they filter themselves so I would not have to, thus I could quickly move on to a post that answers whatever point I was making. They would actually self-select and assist me with disregarding them (this is the important part) no matter what their actual intentions were.

    What I described above is a very basic and simple example of strategy. There is a certain mindlessness to merely re-acting to what other people do. It allows their actions to determine your behavior. Just about any predictable response that you have which can be operated in such a push-button fashion can be used against you. Now, I think that's appropriate only for an adversary who cannot be reasoned with, because other human beings are not toys and it is wrong to treat them as such (even with their active assistance). However, you can bet that your politicians and advertisers and public relations types have no such moral qualms. There are far more malicious uses of this process than having people unwittingly filter your Slashdot responses for you.

    --
    It is a miracle that curiosity survives formal education. - Einstein
  58. Re:This is M$ double speak for "Finding Free Sofwa by Anonymous Coward · · Score: 0

    In two characters, the anonymous poster - who is probably Twitter - told us all we need to know about his opinion of Microsoft.

    I disagree that using M$ to represent Microsoft is a full representation of my feelings towards that company (I'm not the AC from the comment above).

    I find the M$ abbreviation to be clever, brief, and valid representation of what is a very large and wealthy corporation. Additionally, there are the past comments from Ballmer and Gates comparing open source software to communism, so the capitalist slant is appropriate.

    But now you have to make assumptions about my feelings towards that observation. Just because I can see it, doesn't say whether I think it is good or bad. So you are being defensive, and projecting your own bias towards the commenter.

    I use and appreciate open source software. I also purchase and use proprietary software. It's often worth the money. The only problem with some closed source products is that they lock-in my data as well, limiting how I can interact with it, and consequently lowering the value of the product being sold.

    As far as commenting AC, that has more to do with the Slashdot community (which I find to be remarkably intelligent, funny, and wise; the reason for visiting this site is the comments) which is so well established, and places a premium on a low user ID (not IQ). There's little incentive at this point to create a new account.

  59. Re:This is M$ double speak for "Finding Free Sofwa by phantomfive · · Score: 3, Insightful

    How do you know? What tool do you use that automatically detects every rootkit ever invented? I've seen Linux boxes owned, I've seen SGI boxes owned, and I've seen Windows boxes owned. It happens to everyone: even OSX. In fact, given that every OS has had security problems, if your box hasn't been owned, it's because you were lucky enough to not have your box targeted at the crucial moment.

    Every time I hear anyone using any system say, "I've never had a virus or trojan or malware," I always think, "there is a guy who doesn't know how to detect malware on his machine." And it's usually true.

    I'm not saying you don't know how, but you said a genuinely stupid thing right there. It's possible that right now you're computer has been rooted, covered up, and you don't even know it. Because Microsoft sure wasn't protecting you for the last 20 years.

    --
    Qxe4
  60. choose our software, it is opensource by Anonymous Coward · · Score: 0

    but it runs only on windows which you need a tiny $499 license for if you deploy the code in a production environment, which of course would be Win Server 2008 upwards, and using .Net 3.5 and Silverlight.
    Concessions will be given to those who use text like "best viewed in Internet Explorer 8" in the footer.

    We know the story all too well, out here at slashdot.
    m$ sucks.
    (to be factually complete, a part of the linux community sucks too, but that is for other reasons - they can't keep their open source hands to themselves... )

  61. Re:This is M$ double speak for "Finding Free Sofwa by DrSkwid · · Score: 1

    I can only tell you the truth.

    A linux box I inherited as sysadmin was owned one time.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  62. Re:This is M$ double speak for "Finding Free Sofwa by causality · · Score: 1

    I disagree that using M$ to represent Microsoft is a full representation of my feelings towards that company (I'm not the AC from the comment above).

    I find the M$ abbreviation to be clever, brief, and valid representation of what is a very large and wealthy corporation. Additionally, there are the past comments from Ballmer and Gates comparing open source software to communism, so the capitalist slant is appropriate.

    But now you have to make assumptions about my feelings towards that observation. Just because I can see it, doesn't say whether I think it is good or bad. So you are being defensive, and projecting your own bias towards the commenter.

    I appreciate seeing anyone who is willing to call things what they are. It's a pleasing thing to see. It's a shame that more people don't understand the difference between discernment and judgment. The way I often hear it explained is that discernment plus resentment equals judgment. It's as good of an explanation as any until you can see the dynamics of it for yourself (I know that you yourself can do this; that was for anyone not familiar with it).

    As far as commenting AC, that has more to do with the Slashdot community (which I find to be remarkably intelligent, funny, and wise; the reason for visiting this site is the comments) which is so well established, and places a premium on a low user ID (not IQ).

    If you think they put a premium on a low UID, they really put a premium on posting non-AC. Really though, I find that anyone who sees my six-digit UID (or anything else, for that matter) and thinks that this entitles them to make personal assumptions about me is coming from such an extreme position of weakness that I can make short work of them. I have had people do things like this when I correctly used certain "key words" -- I intended their standard meaning as found in a dictionary while they assumed that I must be just like other people who use similar words. You'll notice that some people are very desperate to find a way to dismiss you or write you off or make you (in their minds) like something they have dealt with before and to which they feel superior.

    That's usually because they dislike what you say but are aware that they don't have what it takes to properly explain why they disagree with it. Maybe they are afraid of losing an argument. Maybe someone who is secure in what they believe represents a challenge to why they are not. Maybe they know you are right and still don't like it. Whatever their reason may be, they are judgmental, reactive, quick to try to make things personal, and they lack a solid foundation of self-evident truth for their beliefs. All of these things mean that they are cowardly and you have nothing to fear from them.

    If anyone acted this way towards me because of my relatively high UID, they never admitted it. I never felt that UID had much to do with it in my case. I think it's more that they don't really know how to deal with someone who isn't trying to win their approval (ego) and won't cave in to their various forms of pressure (control), because most of the world does both of those things. It's as though they see something different and are not very discerning so they need to test it. Thus, they turn up the pressure to see if you will react the way that they would, i.e by doing back to them what they have done to you.

    If you do, then you lose your real brightness. Then they can rest assured because the challenge you didn't know you posed to them has been eliminated. Then they can continue to feel superior to you and judge you because you crumbled under their pressure. If you do not succumb to their attempts to belittle or degrade or intimidate or pressure, then you reveal what sort of person they really are and at the same time show them a living example of a higher standard. It makes their tactics backfire and they actually experience the upset that they intended to i

    --
    It is a miracle that curiosity survives formal education. - Einstein
  63. Re:This is M$ double speak for "Finding Free Sofwa by lordtoran · · Score: 1

    If Slashdot would be capable of more than ancient 7 bit ASCII, you could even write Google with a Euro sign.

    --
    Want to hear the voice of GOD? cat /boot/vmlinuz > /dev/dsp
  64. Re:This is M$ double speak for "Finding Free Sofwa by phantomfive · · Score: 1

    Yeah. Sometimes it's obvious when a box is owned, sometimes it's not. As far as I know, I've never had a virus on any of my machines either, but then again, it could be these words I'm typing are being intercepted by a keylogger that I don't know about. I've seen smarter people than me have their boxes get viruses, so I can't say it is something special I did to prevent it. I've just gotten lucky, or it's been hidden so well I've been unaware. As at this time I may also be.

    --
    Qxe4
  65. Well... by coppro · · Score: 1

    This is probably under one of Microsoft's "Permissive" Licenses, which is a shame, but still, this is way better than WebKit.

    Microsoft: 1, Apple: 23

  66. Re:This is M$ double speak for "Finding Free Sofwa by trickyD1ck · · Score: 0, Troll

    ... To a passionate free software advocate, M$ is a concise, efficient and - IMO - accurate moniker.

    then isn't "freetard" more concise, efficient and accurate than "free software advocate"?

  67. Re:This is M$ double speak for "Finding Free Sofwa by oftenwrongsoong · · Score: 1
    Let me modify that suicide joke for the GP:

    Friends don't help friends install M$ junk.
    Friends do assist M$ addicted friends in upgrading to Ubuntu.

    Heh heh... my favorite Linux distro. :-)

  68. Here is the code by fireman+sam · · Score: 2, Funny

    #include <stdlib.h>
    #include <stdio.h>
    int main(int argc, char *argv[])
    {
    #ifdef WIN32
        fprintf(stderr, "Your system is not secure\n");
    #else
        fprintf(stderr, "Your system is not popular enough to be targetted, therefore it is secure\n");
    #endif

        return 0;
    }

    --
    it is only after a long journey that you know the strength of the horse.
  69. Indeed you are. by Anonymous Coward · · Score: 0

    But strange that in the 20 years I've been using Microsoft OSes, I've never had a virus or trojan or malware. I must be doing something wrong.

    You left the ethernet cable unplugged.

  70. Re:This is M$ double speak for "Finding Free Sofwa by Goaway · · Score: 1

    To be fair, any discussion where RMS is mentioned would have to be at least tangetially about personal hygiene or delusions of Godhood, you would think.

  71. Re:This is M$ double speak for "Finding Free Sofwa by Anonymous Coward · · Score: 0

    Yeah. Good job on an impersonation of twitter, but I know that isn't him.

    For next time - you laid it on a bit thick.

  72. Re:This is M$ double speak for "Finding Free Sofwa by Anonymous Coward · · Score: 0

    God knows what you are doing behind your computer all day long. Playing tetris and using notepad my guess ...

  73. Re:This is M$ double speak for "Finding Free Sofwa by QuestionsNotAnswers · · Score: 1

    But strange that in the 20 years I've been using Microsoft OSes, I've never had a virus or trojan or malware. I must be doing something wrong.

    I am sure you have had to deal with the effects of viruses/trojans/malwares with your friends/family/workmates using Microsoft OSes ... or do you have another peculiarly anomalous anecdote?

    --
    Happy moony
  74. Re:This is M$ double speak for "Finding Free Sofwa by causality · · Score: 1

    I beg to differ. If you're so puerile to have the need to use "M$ Winbloze" or "open sores software" in a rational discussion, it seems as if you're trying to sidestep the issue with colorful language. Call things by their name and focus on arguments rather than taking trite potshots.

    I've never seen it demonstrated that a puerile character is the one and only reason why anyone would ever use an epithet like "M$". That would be a very difficult thing to prove and just one exception would destroy the proof. It may be a common reason but if so we have a word for that, which is "stereotype", and the problems with basing decisions on them, especially character judgments, are well known. Assuming that there is absolutely no other reason (and it is an assumption) is a convenient way to look down on someone or to dismiss what they say without ever having to show why their argument was wrong. That's about the only "useful" purpose it serves. I've never felt like those tactics were necessary or appropriate if you really are right and they really are wrong. If you're skilled, you can "win" arguments whether you are actually right or not; that is done with tactics like this.

    Finding a personal trait that you find distasteful (justifiably or not) and then thinking it provides a valid reason to disagree with an argument without showing the reasoning which led you to do so is the definition of "ad hominem attack." It amounts to "I don't like you, so you must be wrong". If someone is sidestepping an issue, by all means call them on it. However, identifying that doesn't depend on the way they spell a company's name. It's so easy to identify, in fact, that using such a heuristic could only hinder you.

    I believe that most of the attempts to disparage or characterize Microsoft, including this one, come from a general frustration with their strong-arm tactics and ruthless dominance of this market. Indeed that frustration is wrong, and if you want to do something about it, why not do something that has a chance of addressing the root problem? The root problem is that people see the undesirable things that Microsoft does and then they make the mistake of resenting them for it. It comes out in the language and epithets that they use and it's easy to detect. Microsoft is not exactly an angel so this wrong way of dealing with them is easy and tempting.

    If you feel any sort of anger or forms of anger like frustration or resentment, know that it is always preceded by a judgment. If not for judgment, then you could watch the wrong that others do and call it what it is without being affected by it. When you see Slashdotters deal with Microsoft in this wrong way and then judge them for it, you are actually doing the same thing. You are repeating with them the error that they made with Microsoft. Describing your objection with more sophisticated or neutral language does not change this. That's actually what anger does; it makes you replicate wrong. It cannot be otherwise because it is a negative energy. Just like those people, you feel justified. Effectively, this means you are following their lead while protesting what they are doing. Thus, they won't feel a need to listen to you because this process makes you just as wrong as they are. They can sense that whether or not they are consciously aware of it (most are not).

    That's what judgment is; it's the wrong way of being right. You can repeat the post you just made until you every last Slashdotter has read it. It would either change nothing or it would make a few people change for the wrong reason: not because they learned anything or became stronger people, but because they want to win the approval and agreement of others. The better way is to show them what I am trying to show you, that their frustration is part of the problem. That won't give you the "satisfaction" of judging the person, but all that ever did was to make a mockery of real satisfaction.

    I'm trying to give you

    --
    It is a miracle that curiosity survives formal education. - Einstein
  75. Oh pick me pick me! I have a new name!!! by Anonymous Coward · · Score: 0

    Wait! Wait! I have a new name for this amazing new marvel of original 'game changer' technology. I want to call it 'The Stanford Code Checker'. ...Oh, oh wait. No. It seems that name is already taken.... by software that checks computer software source code for bugs. And since microsoft doesn't release source code (ever), how will this help, you know, local developers create secure code? How was that supposed to work again? Oh.. oh yeah. That open (at least OSI approved) license thingie. Got it.

  76. Game changer danger by xactuary · · Score: 0

    Dan Kaminsky, a well-known security expert who also provides consulting services to Microsoft, hailed the release a 'game changer' because it provides a reliable way for developers to sort through thousands of bugs to identify the several dozen that pose the greatest risk.

    I, for one, welcome our new, less risky, Horde Overlords!

    If this Game Changer doesn't work, does that mean it's game over?

    --
    Say hello to my little sig.
  77. yeah right by Anonymous Coward · · Score: 0

    Another devious attempt by Microsoft to slander Open source.

  78. Re:This is M$ double speak for "Finding Free Sofwa by ozphx · · Score: 1

    It's also meaningless, since every business is out for dollars. You might as well say $un too, and same goes for any business with an "s" in its name.

    Except $ourceforge (LNUX). Cos... ya know.... they seem to be more about losing money ;)

    --
    3laws: No freebies, no backsies, GTFO.
  79. OSS SHOULD be concerned by WindBourne · · Score: 0, Flamebait

    Right now, Windows really is pure crap. For all the fanbois that defend it, it remains a joke (and the fanbois prove their total ignorance). BUT, the problem remains that IFF Windows ever gets to be more secured than say Linux, mac, or even DOS, then the crackers WILL focus on less secured systems. Basically, this will be a case of not having to run faster than the bear, but simply having to run faster than somebody else. At this time, nearly ALL OTHER OSs are more secure than Windows. Something like this COULD BE A GAME CHANGER.

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:OSS SHOULD be concerned by Anonymous Coward · · Score: 0

      Flamebait. I love it. What was written above is absolute truth. How many really think that MS is secured when on a daily basis a new virus and new openings are announced? The simple fact is, that if MS can finally after 40 years get their act together and can sux less than OSS/Mac/Etc., all the security issues WILL be directed at the rest.

  80. How about the other bugs? by hcmtnbiker · · Score: 1

    "...hailed the release a 'game changer' because it provides a reliable way for developers to sort through thousands of bugs to identify the several dozen that pose the greatest risk."

    Yea, because who would want to fix EVERY Bug before release? Certainly not Microsoft, that's for Service Packs are for!

    --
    If i had one dollar for every brain you dont have, i would have $1.
  81. open src is not about competition....... by Anonymous Coward · · Score: 0

    it's about cooperation...and community...
    don't be faked by so-called technical reports....
    they are really......"technical".....without human factors....u think this world is driven by competition?....hell no......hahaha.....
    only few guys in this world really know how this world runs.....r u the 1? or 0?

  82. Re:This is M$ double speak for "Finding Free Sofwa by Kalriath · · Score: 1

    No, it's twitter. He always does that.

    You probably wont believe this, but he posts anonymously because Anonymous Coward has a starting score (0) higher than all of his 15-20 other Slashdot accounts.

    Personally, I strongly disagree with the whole FLOSS vs Commercial debate (I also disagree with describing FLOSS as "free", but that's another story and mostly related to my pedantic usage of proper English). If something that's "free-libre" happens to do the job you want it for better than commercial alternatives, do it. If something commercial is better, use that.

    Why don't the zealots just let us use whatever the fuck we want? I happen to like Windows. I also like Mac OS. Hell, I even like Linux. Of course, because I said I happen to like Windows, people like twitter would have you believe that I am paid by Microsoft. Hell, I wish I were - they'd pay more than my real employer.

    --
    For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  83. Re:This is M$ double speak for "Finding Free Sofwa by Kalriath · · Score: 1

    You know, that argument has always annoyed me.

    You say that because you've never seen a virus or trojan on your PC, it's just because you didn't detect it.

    Why does this particular perspective only apply to Windows? Why is it never said that if you've never seen a virus or trojan on Linux that it's because you never detected it?

    (Actually, quite amusingly, the comment below me says exactly that. Go him or her!)

    --
    For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  84. Re:This is M$ double speak for "Finding Free Sofwa by Kalriath · · Score: 1

    I don't think you can lay the "twitterism" on too thick. He's pretty "thick" as it is (and I am not referring to his intelligence, merely that I don't think you can get any more twitter-like than he is)

    --
    For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  85. Microsoft's closed-source exploit finder by MobyTurbo · · Score: 0, Troll

    Microsoft has long had a closed-source exploit finder that this article doesn't mention: "Microsoft Windows".

    1. Re:Microsoft's closed-source exploit finder by interested+pyro · · Score: 0

      in recent years Microsoft made a Exploit Creator. Its called "Vista"

  86. Re:This is M$ double speak for "Finding Free Sofwa by SL+Baur · · Score: 1

    You know, I'm starting to take issue with comments that protest the use of the M$, Micro$oft etc. memes. I know how something can get on your tits - articles that identify companies by their stock symbols is a particular irritant of mine.

    It goes both ways. I'm irritated that `$' is being used as an intended insult. It's supposed to be a symbol of _earned_ wealth, which is never a bad thing in my book.

    I had a lot more fun irritating a former roommate expanding MS to Multiple Sclerosis. At the time, it was the more recognized expansion of MS.

    I don't mind using stock symbols as abbreviations either. I even recently proposed that when the CSC namespace runs out for Cisco bugids (we've been as wasteful as the IPV4 guys were) we use CSCO to identify an expanded namespace.

    Personally, I think using "M$" as an abbreviation for Microsoft just identifies the user as an idiot. Same as if one would write "Ci$co". The abbreviation that *really* pisses me off is abbreviating Microsoft Windows as "win". "Win" has unfortunate and untrue connotations when applied to Microsoft Windows.

    I guess I'll just be more fastidious and always write the names out in full, instead of occasionally using the stock symbol as an abbreviation.

  87. Re:This is M$ double speak for "Finding Free Sofwa by SL+Baur · · Score: 1

    (I'm glad you got modded up to +5 by the time I saw this)

    If you're so puerile to have the need to use "M$ Winbloze" or "open sores software" in a rational discussion, it seems as if you're trying to sidestep the issue with colorful language. Call things by their name and focus on arguments rather than taking trite potshots.

    Hear, hear!

    If one must troll or lay down flame bait, one should at least be clever about it. Simple sarcasm merely goes over the head of many moderators and should tend be avoided. Name calling is always boring.

  88. Re:This is M$ double speak for "Finding Free Sofwa by SL+Baur · · Score: 1

    If you can see that I wrote all of the above without ever thinking that I'm any better than you just because I know of a better way (a way that I did not invent), then you will understand where I'm coming from.

    I don't understand where you're coming from. You present an extraordinarily literate argument[1] though. Anyone who can write like you do has utterly no business defending `M$', justifiable anger or not. IMO.

    [1] And one which is going to fly over the heads of 99.99%, as a rough guess, of the folks here.

  89. Microsoft cares about crashes?? by Anonymous Coward · · Score: 0

    So this is so they are able to weed out the exploitable crashes from the regular crashes! Cool, since we all know Microsoft does really care about regular crashes very much!!

  90. Re:This is M$ double speak for "Finding Free Sofwa by Anonymous Coward · · Score: 0

    More accurately: un$

  91. Re:This is M$ double speak for "Finding Free Sofwa by Anonymous Coward · · Score: 0

    If you can see that I wrote all of the above without ever thinking that I'm any better than you just because I know of a better way (a way that I did not invent), then you will understand where I'm coming from.

    I don't understand where you're coming from. You present an extraordinarily literate argument[1] though. Anyone who can write like you do has utterly no business defending `M$', justifiable anger or not. IMO.

    [1] And one which is going to fly over the heads of 99.99%, as a rough guess, of the folks here.

    He's not defending the use of "M$" in place of "Microsoft;" he's saying it doesn't affect the validity of the argument. It's not even about "M$" in particular, but about people refusing to use their brains whenever they encounter presentation they don't like. It'd be like someone saying, "That mathematical proof must be invalid because it's printed in an ugly font."

  92. Re:This is M$ double speak for "Finding Free Sofwa by Virtual_Raider · · Score: 2, Insightful

    While an argument shouldn't be cast aside just because someone uses M$, I don't agree that it is "a concise, efficient and - IMO - accurate moniker".

    You don't agree that text in bold is HIS opinion? I don't agree with your disagreement :P

    --
    +Raider of the lost BBS
  93. Irony alert! by opieum · · Score: 0

    The Irony being that it's for Open Source software...not their own. Microsoft really needs to stop acting desperate and just making good software. Once their marketing machine can ratchet down the bullshit and just sell a solid reliable product instead of a complicated piece of software that has become synonmous with death (BSOD reference here). If they REALLY want to make money (hope you are reading this Ballmer) They could easily make an OS based on Linux open source it keeping certain elements proprietary while still keeping with the GPL and release at a lower price point. They do something like that that allows existing compatibility with ALL Windows and Linux programs (can you imagine a debian-like OS with 100percent windows compatability) And no not like WINE, great project but still far from 100 percent compatibility. They get the best of both worlds. They get the linux marketshare...and the anti-trust hawks off their back. Because people still have a choice. And if they do what is right by consumers while respecting their freedom of choice (creating a great product without the lame ass lockin), they will earn their name as a quality software provider. As it is they create "tools" to find the openings in other products flaws, but seem to miss their own. They had a few thousand bugs still open from 2002 do they not?

  94. open source exploit finder by nczempin · · Score: 1

    A tool to find exploits of open source software? That is so evil.

  95. Re:This is M$ double speak for "Finding Free Sofwa by SL+Baur · · Score: 1

    He's not defending the use of "M$" in place of "Microsoft;" he's saying it doesn't affect the validity of the argument. It's not even about "M$" in particular, but about people refusing to use their brains whenever they encounter presentation they don't like.

    That's a fine thing to say Mr. Anonymous Coward. If you _really_ believe that, you could at least have taken the time to log in and attach a name to those words.

    Name calling (and ad hominem attacks in general) are indicative to me of being part of a weak argument. I do not think I've ever seen an argument strengthened by usage of such. I've followed 'net discussions in various settings for over 20 years and US (first, Asian later) politics for much longer than that. Sociology is fascinating.

    Perhaps I am just disgusted with "The Politics of Personal Destruction", a phrase popularized by the man who brought its application to a high art form.

    Now, pop quiz, do the first two sentences in this response make me look good and strengthen what I have to say, or weaken it? (Actually I'm hoping someone will flame me over that before reading the rest of the post, thus making my point).

    It'd be like someone saying, "That mathematical proof must be invalid because it's printed in an ugly font."

    It's more along the lines of 99.9% of erroneous mathematical proofs use that font and unless I see something obviously interesting and very quickly, I'm going to ignore it. Guilt by association.

  96. Microsoft Unveils Open Source Exploit Finder? by Jeremiah+Cornelius · · Score: 2, Funny

    What! You mean they Open Sourced Windows!??!

    --
    "Flyin' in just a sweet place,
    Never been known to fail..."
  97. Re:This is M$ double speak for "Finding Free Sofwa by Anonymous Coward · · Score: 0

    On the contrary, I'd like to see MORE usage of "M$ Winbloze". But just so that nobody gets left out of the fun, I also recommend the following names:
    Lin$ux
    InbRed $Hat
    WHO?buntu
    Devient
    Genitoo or GentLoo
    Mac Oh It $ux
    FreeBS

  98. There are questions we want answers to by simplerThanPossible · · Score: 2, Interesting

    Has it been run on itself?

    Will subsequent versions exploit the exploits, setup botnets, send spam etc?

    If Microsoft entered the armor business, would they also supply arms to the other side?

    But seriously, Microsoft put a ton of research into finding their security holes, including embedding the acquired techniques in tools. They're useful tools, and have been critically useful to them. Why not release them? My only worry is that it is not in their fighter-nature to help their competitors, and of course the tool can also be used by crackers.

  99. "I was free yesterday, so I'm free today!" by Anonymous Coward · · Score: 0

    Nope, PD or BSD are not maintaining freedom.

    Even in real life you hear:

    "The price of freedom is eternal vigilance"

    which means you aren't free to just ignore it and hope you remain free tomorrow.

    "the tree of liberty must be watered with the blood of revolution"

    which means that if you want to remain free, you will have to remove the freedom from others else they will become your masters.

    PD and BSD are all "I was free yesterday so I'm free today!" and DO NOT WORK. They only remain free as long as someone uses their freedom to keep it free. And even that will fail if someone uses a patent. You CAN patent something up to a year after you code it up in a BSD program. And then you are in violation of using your own code. BSD be damned, you are not free any more.

  100. May already have been stated by HermMunster · · Score: 1

    Of course, you all know there's a difference between open source and Microsoft's opened source. Microsoft's offerings don't qualify as open source. It isn't free of restriction to use and reuse and it isn't free of the restrictions of the OS.

    There's no word for open source in Microsoft's vocabulary. It is opened source which is simply an opportunity to view the source but you can't use it outside of your closed project and can only be used under Windows.

    --
    You can lead a man with reason but you can't make him think.
  101. WTF? by pROCKrammer · · Score: 1

    Microsoft + OSS = LOVE ????

  102. Re:Here's a better idea by Cederic · · Score: 1

    Have you tested your software on
    - Windows XP Pro, no service packs
    - XP Home, none
    - Pro/home/Media Center edition, service pack 1
    - SP2, 3, etc
    - Vista, etc
    - Win XP MCE SP2 with IE8
    - Win XP Home SP1 with .Net CLR1 and CLR2

    I've skipped around 782 permutations, any of which may cause a crash that will not occur on another combination.

    Release software to enough users and they'll let you know when it fails. If one customer in 10,000 suffers a crash once ever then you have a lot of very happy customers, and on a 100m install base you also have 10,000 crash reports to sift through.

    Which crash do you spend the 8 man-months trying to replicate so you can fix it?

  103. Re:This is M$ double speak for "Finding Free Sofwa by causality · · Score: 1

    I don't understand where you're coming from.

    Paradoxically, it's much easier to understand than it is to explain. It's one of those things that is not so complex that few people could understand it, but rather, it is so simple that almost everyone overlooks it. I certainly overlooked it for a long time. Because of that, please excuse the length of this post.

    You present an extraordinarily literate argument[1] though. Anyone who can write like you do has utterly no business defending `M$', justifiable anger or not. IMO.

    If your respect for my arguments or my ability as a writer were genuine, you would perhaps be puzzled by my perceived defense of "M$" and may ask me about it but you would not presume to tell me what is or is not my business. That's tantamount to telling me what I should or should not say, or how I should or should not feel about an issue. I strongly doubt you would go along with someone else doing this to you; you seem far too independent and free-thinking for that. It's alright, for I think being so easily offended is a serious weakness, but you should know that it won't work.

    I wasn't actually pronouncing the use of "M$" to be right and good. I was accepting the reality that people are going to use it whether or not I enjoy it. The least-understood quality of human beings is that they always feel like what they do is right, or at least necessary. That's true no matter how wrong they actually are. This has an interesting effect because human beings also have egos.

    There is nothing to which ego is more sensitive than anger and its various manifestations, such as frustration or resentment. When you tell them "you're wrong", not because you see that they are misguided and want something better for them, but because what they did has offended you or caused you to resent or condemn or judge them, you stimulate their ego. Now it's no longer about whether you had a point. Now it's about who's going to yield to whom, who's going to win the contest in which you are now engaged. That's if they are inclined to contests. If they are not, they'll just write you off by judging you as "unpleasant" etc. and ignoring you. Then nothing changes.

    The simple fact is, you cannot convince anyone of anything without their consent. Get them on their high horse and they will make it a point to prove that to you. The way you were attempting to correct "M$" was from one ego to another, yours to theirs, which is why it must fail. It will fail or it will succeed for the wrong reason by appealing to the people-pleasers who should not be so concerned with whether you approve of them. Either way, no one learns anything and no one becomes a stronger person.

    It does not have to be that way, of course. There can be compassionate understanding instead. I'll sum up the true problem for you, the obstacle of obstacles, the one cause of all of the ignorance in the world. People are leaves in the wind. They are products of their environments with no real self-hood who better resemble automatons than independent, free-thinking human beings. They can be this way while still clinging to the idea that their beliefs and impulses are their own. Modern education and mass media only encourage these things because both are heavily invested in them. If you properly see this, then you realize that these people are like slaves and don't know it. You realize that they are far less free than you are and that they suffer in many ways because of it.

    If you yourself have not been too compromised, then you cannot see this without wishing that they be more free, that they not suffer so needlessly. You'll understand that any problem you could have with them comes from their slave status because only free people can truly understand and only free people can truly love. If they had real understanding and if they loved other people, then any "problem" you could have would not be a problem. You a

    --
    It is a miracle that curiosity survives formal education. - Einstein
  104. Re:This is M$ double speak for "Finding Free Sofwa by causality · · Score: 1

    It's more along the lines of 99.9% of erroneous mathematical proofs use that font and unless I see something obviously interesting and very quickly, I'm going to ignore it. Guilt by association.

    In other words, "I'm not a human being; I am a prize. Reaching me is the same as winning the prize. If you want to win that prize, you will submit to my control and play the game according to my rules. If not, you lose the game before you even started playing."

    The people-pleasers love this kind of invitation because then you can praise them for being "good" and agreeable. They go along to get along. It's the only "goodness" they will know because they are addicted to the approval of others. That addiction is what you exploit when you set yourself up to be some sort of prize. Hypothetically, it's like telling a crack whore that you'll give her some crack if she'll perform some sexual favors for you, except that doing it the way you do it allows you to believe that it's somehow noble. The crack whore has no such delusions, nor do her clientele, because in her case it is easy to call things what they are. In your case, the easy excuses that lead to a belief that you are doing anything other than attempting to control is an obstacle to calling this what it is. The belief in this sort of control and that it is ever legitimate leads to all sorts of perversions of the idea of authority. On the personal or family level, it leads to "do as I say, not as I do." On a national level, it's one of the forces that turns democratic nations into totalitarian states with increasingly authoritarian policies.

    It's an attempt to cause people to do what they would not otherwise do in order to please you and avoid your judgment of guilt, by association or otherwise. You won't be able to truly respect anyone who submits to this sort of coercion, so even if you get what you want, it is tainted. That is a proper result because this is one of the more subtle, less in-your-face ways to bully people (there are many such ways, some of them even look quite agreeable on the surface). No bully ever respects the weak people who submit to him, nor could he. Likewise, no bully respects the weak people who want to be an even bigger bully, which is why seeing the wrong of this does not tempt me to condemn you or insult you for it, not even in my mind.

    Of course the real flaw in the first paragraph is that you are in fact a human being. Control of others isn't worth reducing that status to a mere prize. The price is too high. Further, if you had a pure intent and were seeking knowledge, you would navigate the obstacles (real or perceived) like incorrect presentation and would not allow them to stop you from examining that knowledge. You would need no heuristic to replace or complement the process of evaluating the knowledge and applying whatever tests of truth you think are appropriate. That's why this is about control and can only be about control. I can tell that you are intelligent. If you really wanted to know something, it would probably be difficult to hide it from you. That's why this stumbling block is artificial.

    The alternative is childishly simple. It consists of accepting that people will often do things you don't like and realizing that they may feel the same way when they look at you, and then appreciating that the vast majority of those things don't matter. They don't matter unless they materially determine the truth or the falsehood of any claims that are made, facts that are presented, or reasoning that is elucidated. Things like the choice of a font or the spelling of a name fail this test. It cannot be otherwise. The actual truth or falsehood of an argument can only be determined on a case-by-case basis, so statistical comparisons based on the aesthetic choices of others cannot help.

    --
    It is a miracle that curiosity survives formal education. - Einstein
  105. Re:This is M$ double speak for "Finding Free Sofwa by DrSkwid · · Score: 1

    well yes, I've cleared loads of em off but been lucky in myself

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  106. Re:This is M$ double speak for "Finding Free Sofwa by Nesman64 · · Score: 1

    To a passionate free software advocate, M$ is a concise, efficient and - IMO - accurate moniker.

    It's also meaningless, since every business is out for dollars. You might as well say $un too, and same goes for any business with an "s" in its name.

    You can't say that on $lashdot.

    --
    coffee | nose > keyboard
  107. M$ Shills will always lie by Anonymous Coward · · Score: 0

    M$ Winblows has so many vulnerabilities it would not take long for a fresh install of M$ winblows to be breached, even when the network has numerous firewalls. That would make you a lying shill for M$ Troll. What you did wrong was becoming a M$ addict and shill.

    --
    Friends don't help friends install M$ junk.
    Friends do assist M$ addicted friends in committing suicide.

    1. Re:M$ Shills will always lie by DrSkwid · · Score: 1

      Hehe first time to be called everything. I didn't Windows was any good. I'm a FOSS user and advocate but I don't like lies and FUD.

      Hehe shill, that's going to keep me smiling. Just a shame you're an illiterate.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter