Slashdot Mirror


GDI Vulnerabilities: An Open Letter to Microsoft

UnderAttack writes "Tom Liston, the guy that brought us the LaBrea Tarpit, wrote an open letter to Microsoft regarding the GDI JPEG vulnerability, and Microsoft's scanning tool for this vulnerability, which he calls 'worse then useless'. Tom, who wrote his own scanning tool, ends his letter with 'Please stop treating your customers like idiots and give us information; information that we can use.' Like Tom explains, the official Microsoft scanning tool misses a lot of vulnerable DLL's installed by third parties, and Microsoft fails to explain if these libraries are a problem or not."

50 of 444 comments (clear)

  1. er, by LurkerXXX · · Score: 3, Insightful

    Sooooo, how exactly is MS responsible for all 3rd party DLLs?

    1. Re:er, by diginux · · Score: 2, Insightful

      They are responsible for informing you that 3rd party DLL's might infected, in my opinion.
      Also, if you write a program for searching out infected DLL's, why not do it for all libraries on the system?

    2. Re:er, by White+Roses · · Score: 3, Insightful

      Because it's not a 3rd party DLL? Because it's a MS DLL distributed by a 3rd party? It's still MS's code. RTFA.

      --
      Do not touch -Willie
    3. Re:er, by LurkerXXX · · Score: 4, Insightful
      So, is Linus going to put out an advisory that there may be some random explit in the Gimp that allows user level access to hackers? I know there must be some random buffer overflow in the Gimp somewhere. Linus should point this out according to your logic, shouldn't he?

      Kinda silly eh?

      Of course 3rd party apps might have exploits. It's up to those 3rd party vendors to supply patches. Even if the code is originally based on MS code, the 3rd party vendor may have modified it in any variety of ways and MS has no idea if those will be dangerous versions or not. MS has identified the bad code, the 3rd party vendors have been notified about it. It's up to them to tell you if their version is bad or not, and patch their software.

    4. Re:er, by julesh · · Score: 5, Insightful

      So, is Linus going to put out an advisory that there may be some random explit in the Gimp that allows user level access to hackers? I know there must be some random buffer overflow in the Gimp somewhere. Linus should point this out according to your logic, shouldn't he?

      If Linus wrote the code, and told the application authors that they were only allowed to use it by accessing a .so file (installed into a special directory for each application that uses it, for no good reason that anyone could gather, and Linus insists that they aren't allowed to modify it in any way), and there was then an update to that .so file, I would expect the update that Linus issued to fix all copies of it, yes.

      Of course, nobody behaves like this in the Linux world. Shared libraries are installed to /lib or /usr/lib and you only have one copy of each of them. An update would ensure that the single copy you depended on had the vulnerability eliminated.

    5. Re:er, by pjrc · · Score: 3, Insightful
      Of course, nobody behaves like this in the Linux world.

      I believe you missed the zlib buffer overflow, which turned out to be staticly linked into many applications, as well as in the shared library.

      Yeah, not quite the same, since static linking is different (perhaps worse) than having lots of copies of the DLL in different directories, as far as updating is concerned. Also, a different situation because developers had the option to link the way they wanted.

      But to say this sort of thing never happens in the "linux world" and that all library security bugs are easily cured for all apps by updating the shared libs neglects some really unfortunate occurances like the zlib buffer overflow.

    6. Re:er, by say · · Score: 2, Insightful

      MS however, has ZERO idea how the vendor modified the code, or how the rest of their app interacts with it, and if it is a security risk or not. The vendors DO know. They are the ones that should patch their own app.

      Sanity check: can you modify Microsoft SDK libraries? No. They are distributed in binary, not source.

      this is liked saying the since some Linux code may have been used in some 3rd party app like the Gimp [...] Linux should be responsible for checking the Gimp and any of a million and one other 3rd party apps, for any problematic code.

      Not it is not. I don't even bother explaining why. Or maybe I'll do it anyway.

      This situation is the equivalent of a car company getting parts (let's say the tires) from another company, and the tire company suddenly discovers that the tires might explode if you use them on asphalt. Who's responsible? Should the car company make the changes to the tires?

      You need to re-read your book en elementary logic.

      --
      Roses are #FF0000, violets are #0000FF, all my base are belong to you
  2. It's actually a tough job even on Linux by shoppa · · Score: 4, Insightful
    Scanning your own systems for vulnerabilities, especially when you have third-party stuff on it, is a tough job.

    You don't even need third-party stuff or an application to make it hard under Linux. Typical cycle is: kernel version x comes out in March. It's in a Red Hat release in July. Vulnerability found in September, with an immediate release of version x+1 on kernel.org (which also has a lot of changed/evolved drivers etc.) Red Hat back-patches the fix to version x and makes a new funny version number to signify this. They might include a couple other things from x+1 in the back-patch to version x. Except that the funny redhat version number doesn't signify much to anyone on the surface.

    Similar things happen for Red Hat (and other branded linux binary distributions) of Apache, SSL, etc., things that are all quite critical and you'd hope would be crystal-clear as to which patches your version has or doesn't have.

    Now finding whether version X of a library or application has a vulnerability patched usually isn't too hard. And Red Hat does a pretty good job of keeping on top, way better than say Microsoft.

    Disclaimer: I'm no fan of Microsoft, but I'm not a big fan of Red Hat (or, as I prefer, Head Rat) either (or any binary linux/gnu toolchain/popular application distro for that matter).

    1. Re:It's actually a tough job even on Linux by EnronHaliburton2004 · · Score: 2, Insightful

      That's assuming that you get all of your products via apt. Does 'apt-get upgrade' fix all of those Third Party issues?

      What if you compile a third party product from a tarfile? Third party products are as common on Debian as they are on any other distro.

    2. Re:It's actually a tough job even on Linux by sEEKz · · Score: 3, Insightful

      I don't think so!

      It's a complete different world...

      Normally you can see on security lists like bugtraq what kind of vulnerabilities are discovered, or patches which are available.

      Now you have different options.
      1. fix it yourself (you have the source)
      2. wait for maintainer of the program or library to release a patched version
      3. wait for your linux distro to release a patched version

      What I mean to say is, in Linux or other Open Source projects, it's pretty obvious what to fix or where the problem itself exists.
      Worst case scenario, you can fix it yourself.

      In case of Microsoft or other closed sources, you have to wait for the main distributer to get a fix of the program or library. And even then you're not 100% sure if the problem is fixed.

    3. Re:It's actually a tough job even on Linux by brianosaurus · · Score: 2, Insightful

      I don't use Windows, so I haven't been able to experience this firsthand, but I don't think the point of the article was that scanning was easy. It isn't. That's why Red Hat's system is a pain in the ass. However if you follow their procedure, you can (eventually) get to a point where you are confident that you have eliminated the vulnerability.

      The problem with Microsoft's system is that even after you follow their patching procedure, you still don't know if the problem is fixed, and they give you no way to be sure. The scanner says to update. Update says no new patches. But the scanner still says you "may be vulnerable". Leaving the user in an endless loop of wonder is not a sufficient solution.

      The article's author's scanner, i gather from its site, does a better job of informing the user where the problem is and how to fix it (software update, then delete "these" files, and ignore "these" files). After running his scanner and performing the suggested steps, a subsequent run should say "its all good", or again give a specific list of things to do, eventually resulting in "you are not affected."

      Microsoft should be offering tools and patching procedures that get you to a "you are not affected" state. Their increased focus on security should not depend on third-party tools and patches.

      --
      blog
    4. Re:It's actually a tough job even on Linux by LincolnQ · · Score: 2, Insightful

      Bad, and for several reasons:

      - It doesn't resolve the issue raised by your parent. If you execute your distribution's 'upgrade all new packages' function, after it has updated its repositories, you will get the new package. The problem is that the distributions don't update their repositories in a useful or regular way, and it's often difficult to execute this function.

      - What if the new code has serious flaws that make it worse to use than the old? You would prefer to regress. Especially if the security flaw is something minor like "local user is allowed to use the cd-burner even though he's not supposed to" -- if the new version comes out with all sorts of other features that break it, you would much rather use the old one that didn't have a flaw that you cared about, than many that you do.

      - What authority do you have to say 'nobody should ever install an insecure program again'? I'll admin my own system, and install what I want, thanks.

      - Infeasible to implement on such a scale as you suggest.

      - It's against some of the principles of Open Source software development, where you can always look at the past versions of software.

  3. Like We're Not Idiots? by MankyD · · Score: 5, Insightful

    Most users ARE idiots. It seems completely appropriate that they should be treated this way. I very much mean this.

    Yes, the slashdot crowd and others might do well to receive more information regarding vulnerabilities and fixes for them, but the average user would be overwhelmed.

    I once mentioned to a gentleman that the standard encryption on an 802.11b WAP wasn't entirely secure and he panicked. He asked if hackers would steal his credit card and social security numbers. I asked if he ever shopped online or transmitted those numbers across the internet to which he replied emphatically no (he didn't even store them on his computer for that matter). He still did not understand that a "hacker" can not steal his information from a WAP if it was never there in the first place. He promptly switched to using a ethernet based network.

    Most people are too stupid to be told even the fisrt thing about security. Better a patch is provided that works and they use it. Seeing as how the patch was not complete in this case, that'd differenty, yet the users should still be treated like morons.

    --
    -dave
    http://millionnumbers.com/ - own the number of your dreams
    1. Re:Like We're Not Idiots? by ConceptJunkie · · Score: 4, Insightful

      And all this approach does is scare the idiot users, because the typical computer-phobe will assume his machine's been infected with a virus.

      So really, the tool doesn't serve anyone well.

      --
      You are in a maze of twisty little passages, all alike.
    2. Re:Like We're Not Idiots? by Anonymous Coward · · Score: 5, Insightful

      "...Most users ARE idiots. It seems completely appropriate that they should be treated this way...."

      That's a little harsh especially considering your example. You can, of course, be a very smart person and not know much about wireless networking. That "gentleman" could be, for example, the lead scientist in a bio research project and if he asked you a question about something he had detailed knowledge of and you didn't know the answer he, too, could conclude most people are idiots.

      The world is full of technology that no one person can, or has the time, to absorb it all.

    3. Re:Like We're Not Idiots? by maxpublic · · Score: 4, Insightful

      Most users ARE idiots.

      Everyone's an idiot in a field they know little or nothing about. Computer users want their machines to work; they don't want to know how they work, and why should they? You regularly use devices, or the products of devices, that you can't even begin to describe the manner in which they function, yet I don't see engineers or factory workers or mechanics standing up and calling you an idiot for not knowing how these things work, or for not wanting to learn how these things work.

      Computers don't get a special exemption to this rule. They're just tools like any other tool, nothing more.

      Max

      --
      My god carries a hammer. Your god died nailed to a tree. Any questions?
    4. Re:Like We're Not Idiots? by Paulrothrock · · Score: 2, Insightful
      Difference: I don't have to make sure software patches in my car work for my airbag to deploy. And when it doesn't deploy I or my beneficiaries can sue the hell out of the car company.

      I'm not saying you're wrong, but computers are totally different from factory machines or cars.

      But, really, you're arguing semantics. Idiots isn't the best word to use to describe users. Unknowledgable is better. They don't know about the system they're using, and they shouldn't have to. We trust car designers and vacuum cleaner designers and toaster designers to make a system that's easy to use, and that protects us as much as possible from danger. We also trust business models, like banks, to keep things secure. (Probably a better analogy.)

      Example: There's a process you have to go through to withdraw money from your bank: Fill out a slip, walk to the cashier, show her ID, and then have her verify it and give you the money. People do this because it's the system that's in place for getting your money out, and it's pretty much secure.

      However, there are no systems for computer programs, at least that people can see. So instead of letting someone else verify your identity and give you the cash, you have to have an intimate knowledge of how to work the bank vault or you have an insecure transaction.

      So, no, users aren't idiots. But the systems in place don't allow for much human error, or protect users from it. Maybe UL should start certifying operating systems?

      --
      I'm in the hole of the broadband donut.
    5. Re:Like We're Not Idiots? by john_anderson_ii · · Score: 2, Insightful
      I strongly disagree. Most users are not idiots. By this statement I mean most users have the capacity, if not the desire, to learn quite a bit about technical security. My best friend and former roomate is fireman who can barely handle his remote control. However in a few Q & A sessions I've successfully taught him the concepts behind memory paging, how buffer overflows execute "arbitrary" code, and he's familiar in three seperate ideas of implementing SQL database load balancing. He picked up on these concepts through casual conversation. He's not some phenomenon, this occurance has come to pass often within my friends and family. Why? Well, when their computers break they call me, and I fix them. When they ask "what happened?" I friggin' tell them. I tell them in a way that they can understand it. Funny how they are having to call me less and less these days. I'm willing to bet it's not because of AOL's hammer-mouse fixer thingy.


      Those aren't easy subjects to gain an understanding of....even if you background knowledge under you belt.


      Microsoft knows damn well it can present detailed information on the nature of these flaws, what parts of the OS are affected, etc. in a way a great deal of it's costomers can understand.


      For christ sake if "ass-crack" Bob down at GM Goodwrench or whatever can explain to me the concepts behind fuel-injector deterioration and how the balance between detergents and octane in gasoline affects their lifecycle, then MS can sure as hell explain a buffer overflow to a 33 yr old housewife.

      --
      Be Safe! Sleep with a Marine. Semper Fi!
    6. Re:Like We're Not Idiots? by Zen+Punk · · Score: 2, Insightful
      The issue wasn't that the gentleman didn't know much about wireless networking (heck I don't too much about it myself), It was that he had no fucking sense.

      It was as if you had told him, "You know, the hinges on that model of safe are easily broken," and he freaked.

      "Oh no, does that mean someone could break in and steal my diamonds?!!"

      "Well sir, do you have any diamonds in the safe?"

      "No."

      WTF?

      --
      Sleep is futile.
    7. Re:Like We're Not Idiots? by black+mariah · · Score: 2, Insightful

      The word you're searching for and failing miserably in finding is ignorant. Most users are ignorant, and don't want to be anything else.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
  4. Other ways by globring · · Score: 5, Insightful

    Any valid points the author has about the uselessness of the tool, or the general state of affairs with security at Microsoft, are dimished by his pompous attitude and snide remarks.

    Why not write a technically detailed letter about the code you find (since he read it so many times) and perhaps offer some constructive alternatives to improve it?

    Not only would it be more interesting to read, but they might actually be more willing to consider it.

    1. Re:Other ways by slipstick · · Score: 3, Insightful

      As a way of getting Microsoft's direct attention the letter admittedly sucks.

      However, I would argue that the guys point wasn't to garner browny points with geeks as much as to get the frustration off his chest AND get geeks to recognize once again the flaws in MS's security protocols.

      Furthermore it isn't a "cheap pot-shot". He's venting, he's not bootlicking. He's saying "for crying out loud, you guys have Billions of dollars, resources up the wazoo and you can't get it right, damn I'm mad and I'm going to vent(but I'm going to be humorous in doing so)!" Haven't you EVER felt that way. The beauty of the web is that he can post that and hopefully feel better about it.

      So, your right, this isn't for MS, it's for the masses, including the press and geeks who might read it, giggle a bit, and maybe as a group hold MS's feet to the fire on this.

      --
      Sure information wants to be free, but how much are you willing to pay for the packaging?
  5. Re:Hate to quote a quote but... by LittleGuy · · Score: 3, Insightful

    which he calls 'worse then useless'
    So it gets worse, _then_ it is useless? :)


    With 40+ subvariants of the patch, just saying "there's a vunerability on this here machine" without giving the source of the vunerability and the solution to patch said vunerability is dangerous, bordering on the criminally neglient concerning network security.

    --
    Mod Karma -1: I sed bad wurds. If I cep my mouf shut, I wud be at riyses.
  6. I second that "information we can use" point by Asprin · · Score: 5, Insightful


    I spent about 45 minutes reading docs at MSDN/MSKB trying to find an explicit statement that IE6SP1 on Win98 is vulnerable, and I swear that they don't actually state that fact (explicitly) anywhere! I eventually was able to read between the lines and conclude that Win98 isn't vulnerable, but Win98 + IE6 is, so you should run Windows Update to DL the patch.

    Am I certain? No. Like I said, it's very difficult to find answers to very simple questions in their docs sometimes. I especially hate reading their security bulletins because it's like they were written by very technical lawyers who are trying to maintain the illusion of releasing information without actually doing so. As often as is possible, I try wait a day or two for the DHS CERT to issue their bulletins because they do a slightly better job of relaying useful information.

    --
    "Lawyers are for sucks."
    - Doug McKenzie
    1. Re:I second that "information we can use" point by M-G · · Score: 2, Insightful

      Yup. Lousy job of this whole thing. They show a patch available for Win2K with IE6 SP1, yet scanning said system with their tool says there is no vulnerability. Or did the fix magically get added into a different update that was already run?

      Another system claims that there 'may' be vulnerabilities. Installed all the patches that would apply. The tool still says the same thing.

      Another pretty stupid thing is that they have this run as part of Windows Update, but they really need to be able to have a way for the average user to run it multiple times. After all, if Joe User sees that he has vulnerabilities, and then goes off to do other updates, he's going to have to find the download page for the tool later to recheck. This one has disaster written all over it.

  7. Re:Yes, Microsoft can fix everybody's code! by BeerCat · · Score: 4, Insightful

    Actually, according to TFA, your analogy should be:

    "My home-built kit car has a Ford engine. There's a problem with the engine. Ford needs to fix it"

    --
    "She's furniture with a pulse"
  8. Either way you choose... by Vexler · · Score: 2, Insightful

    It seems that Microsoft, for all its blustery and arrogant, dismissive attitudes toward end users, manages to find itself in a quandary. If it releases too much vulnerability information, it could very well help exploits be written at a faster clip; if too little, then it risks being irrelevant. The timing is tricky too in this case.

    Another problem, though, may have something to do with the audience. Trying to be "all things to all people" (including less-than-clueful admins), it is likely that they decided to "dumb down" the announcement, in short proclaiming that your computer "may be vulnerable". Some could argue that it is language of FUD, but I would say that they are trying to impress on as many people as possible that this is not just another "critical" update. This one is really, really critical.

  9. Re:Yes, Microsoft can fix everybody's code! by AceCaseOR · · Score: 4, Insightful
    Funny, but irelevant. Microsoft wrote the DLL's in question, but distributed them through third parties (as has been mentioned by other posters).

    For a better analogy, Microsoft is refusing to pay Child Support for its bastard child.

    --
    Zagreus sits inside your head, Zagreus lives among the dead, Zagreus sees you in your bed and eats you in your sleep.
  10. Re:No Warranty Implied by Anonymous Coward · · Score: 1, Insightful

    Microsoft does not take warranty for their code, either.
    Fot not a single one of their products (and you shell out loads of money for)!

    This is a tool written to help and he cannot give warranties (in USA this may prove expensive...), because he is also a 3rd party and cannot know anything about this fricking hole.
    So take it or leave it.

  11. Re:No Warranty Implied by gl4ss · · Score: 4, Insightful

    would you give warranty for something you give for free?
    i don't think so.

    well, maybe he'll give you your money back!

    --
    world was created 5 seconds before this post as it is.
  12. In "How not to write an open letter 101"... by strAtEdgE · · Score: 4, Insightful

    ... first class on day one, they would cover off not including some pointless story about your childhood home which comprises half of the letter and has absolutely no relivence to the point of the letter, other than to say that windows users are "in the dark".

    Don't get me wrong, the letter itself was justified, and the author is right about the tool by microsoft I'm sure. But why is that story in there, to make sure that someone at Microsoft doesn't actually read it?

    --
    ----- sXe
  13. This is NOT just a Microsoft bug! by Ryu2 · · Score: 5, Insightful
    Microsoft did not write their own JPEG code; rather they used the freely available implementation from the Independent JPEG group. The flaw is actually in the IJG code, not any Microsoft code.

    Indeed, Netscape, which also uses that code for its JPEG decoding had that flaw (but it was fixed earlier, and of course, it did not make the news nearly as much as this Microsoft issue, owing to its much smaller market share.)

    http://www.openwall.com/advisories/OW-002-netscape -jpeg/

    --
    There's 10 types of people in this world, those who understand binary and those who don't.
    1. Re:This is NOT just a Microsoft bug! by Master+of+Transhuman · · Score: 2, Insightful

      "Microsoft did not write their own JPEG code"

      And they obviously never looked at it either, right?

      Not during their last "security initiative" and not during their PREVIOUS "security initiative" either.

      Anybody remember the "code freeze to tighten up security" several years back?

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  14. Re:In case it gets Slashdotted.... by gcaseye6677 · · Score: 2, Insightful

    This seems to be a trend for the "trustworthy computing initiative". I noticed that the much-hyped security features of XP SP2 consist mostly of the new firewall and popup blocker (which many people already had), along with more visible security reminders like that stupid shield that pops up when you download a file, visit an activeX using website, etc. It seems like they are trying to make the focus on security as visible as possible, without providing any real, useful details. I get the idea that it's more of an illusion of security rather than some massive overhaul of the operating system like they want us to believe. I have a feeling that this won't be the last of the MS security illusions that we see.

  15. Re:In case it gets Slashdotted.... by dustinbarbour · · Score: 2, Insightful

    Look.. I'm all for this "copy all the text and save everyone the hassle of waiting on a /.ed server" bit, but I'm getting freakin' tired of seeing these posts. If the idea was to put everything here at Slashdot, the editors would do so right at the outset. Stop doing this pre-emptive crap.. especially with a page hosted by the ISC!

  16. Re:Hate to quote a quote but... by LittleGuy · · Score: 3, Insightful

    Please back up your assertion that this is "bordering" on criminally neglient.

    Analogy: there's a part of your car which could explode at anytime. It's been a long-standing part of your car. This part can manifest itself in different sections of the car or in different accesories added to your car. You which might be able to track down the part(s) if you are an adequate mechanic and you've kept track on where the parts have been put.

    You go back to the manufacturer who says, "Well, we can tell you if you have the part, but we're not sure where on the car, or how many different parts of the car, but you should really get the parts replaced or else the car will blow up".

    --
    Mod Karma -1: I sed bad wurds. If I cep my mouf shut, I wud be at riyses.
  17. Re:Don't go for pretty software by Skye16 · · Score: 3, Insightful

    No, software should work AND look pretty. Just because form follows function doesn't mean it should be completely disregarded.

  18. Why not offer a common jpeg DLL? by AaronW · · Score: 4, Insightful

    I am surprised that Microsoft does not do what Linux does and have a common DLL provide all the JPEG functionality. At least in Linux, most, if not all apps, use libjpeg.so.

    Fixing a problem like this in Linux is trivial. Only libjpeg needs to be patched, and automagically, all apps that depend on that library are also rendered invulnerable.

    We saw this with png and other shared libraries. Also, offering many of these common libraries as DLLs helps reduce code bloat since every app no longer needs to reinvent the wheel.

    --
    This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
    1. Re:Why not offer a common jpeg DLL? by retro128 · · Score: 2, Insightful

      Fixing a problem like this in Linux is trivial. Only libjpeg needs to be patched, and automagically, all apps that depend on that library are also rendered invulnerable.

      What about programs that have been compiled statically? It wouldn't be a good thing to patch the library and then assume all of your apps are fixed. I realize that not many people do static compilations when they can avoid it, but it does happen in the name of portability, or maybe in the odd binary package where the packager didn't feel like writing in dependencies. I would think that unless you know FOR SURE your program is relying on the external library, it would be bad to put your faith in the fact that your programs are protected after updating it.

      --
      -R
  19. Re:No Warranty Implied by Trailer+Trash · · Score: 2, Insightful

    would you give warranty for something you give for free?

    Sure! If it doesn't work, they can have their money back...

  20. Re:Rules for this story by Allen+Zadr · · Score: 4, Insightful
    May I be the first to agree, except all of the DLLs complained about are Microsoft DLL files. Regardless of what 3rd party re-distributed the Microsoft DLL, I would hope that Microsoft's own scanning tool would be able to find and identify DLLs that Microsoft wrote (whether written for redistribution or core-os).

    Beyond that, if I find out that my Windows version of "The Gimp" is also vulnerable, I know enough to go to the author of that program and find a patch.

    If, on the other hand, 'The Gimp' told me that GTK may be vulnerable, and the 'GTK' folks told me that 'The Gimp' may be vulnerable, I would surely be the first person to stand up and write a singularly upset letter to those projects.

    On the other hand, I didn't pay $199 per copy of "The Gimp" and, as a condition of my use of said software, it clearly tells me that I am free to modify the code to my liking. Thus, I don't feel that "The Gimp" and the "GTK" projects owe me merchantability. Microsoft (on the other hand) I do feel owes me - at least - merchantability to perform as advertised...

    So long as Microsoft can fix the issues that are theirs (as opposed to point me in a circle), I have no qualms with spending more of my fine earned money to them for a really nice gaming OS.

    --
    Kinetic stupidity has a new brand leader: Allen Zadr.
  21. Re:Hate to quote a quote but... by PeterHammer · · Score: 2, Insightful

    IANAL but I it seems to me that any programmer writing C code in this day and age who leaves a buffer unchecked in their code should be guilty of criminal negligence if that buffer can be used to execute malicious code. The dangers of unchecked buffers have been documented well enough to the point that it seems reasonable to argue it is a gross deviation of accepted professional standards of software development to allow such sloppy coding to pass through.

  22. Re:Dumb Question by Nevo · · Score: 2, Insightful

    Actually, that's an excellent question. And believe it or not, the answer actually kinda makes sense.

    The file in question is gdiplus.dll. This file was included in Windows XP and Windows Server 2003, but was not part of previous operating systems.

    Therefore, apps that used this .dll (like Internet Explorer) when installed on previous operating systems (like Windows 2000) had to ship their own copy of the .dll.

    So some apps ship with their own copy, then along comes WinXP/2K3, and they add a second, system-supplied copy.

  23. Different rules for a monopoly by hachete · · Score: 1, Insightful

    Until Microsoft become a profit organisation rather than a tax-harvesting one, then they get all the stick they deserve.

    Thankyou,

    h

    --
    Patriotism is a virtue of the vicious
  24. Re:Rules for this story by SoSueMe · · Score: 3, Insightful
    "1.) Microsoft is somehow responsible for all third-party DLLs on a system. Their scanner must contain a self-sufficient, learning AI that just "knows" which DLLs to scan on any system in existence."
    Please read the letter again (assuming you read it once).
    When a third party vendor wants to distribute a Microsoft DLL with their product, don't they have to get permission from you? Wouldn't there be a list somewhere in Redmond of the third party applications that have distributed vulnerable copies of gdiplus.dll? Can you tell us what they are?
    As for the "...but Mozilla is vulnerable too!" defence, Yes I imagine Mozilla on Windows certainly is.

    As for the "we're not the only ones" plea, this is not a very adult response to any form of critique.
  25. Re:This whole open letter business by ClosedSource · · Score: 2, Insightful

    Only when they're more interested in communication with the supposed recipient than they are with getting publicity for themselves.

  26. Re:Hate to quote a quote but... by maximilln · · Score: 2, Insightful

    Please back up your assertion that this is "bordering" on criminally neglient.

    Yes, yes. We all know how apologists will assert to their death that there is no negligence or violation of expected product quality unless there's death and dismemberment.

    Microsoft has been charging money for a product which has demonstrated it's ability to be substandard for over a decade. Open source software, at the very worst, is on par AND it gives customers infinite flexibility.

    --
    +++ATHZ 99:5:80
  27. Re:DLL Hell by ewhac · · Score: 2, Insightful

    Why would upgrading an application also upgrade a shared system library at the same time? If the application needs the later library version, then the system needs upgrading as well (and probably a good thing, too). Only the system vendor, or the user by direct action, should be messing about in the system directories. Applications shouldn't be fscking around in there at all. If they do, then the result is guaranteed to be a complete and utter mess. (This is obvious, right?)

    Further, why would upgrading a shared system library break older applications? If the new library isn't backward-compatible, then the library vendor did The Wrong Thing. This can admittedly be a bit dicey when you've fixed a legitimate bug in the library, and dependent applications break. By definition, the applications were broken for relying on broken behavior, but sometimes pragmatism has to win out. However, if you have a well-designed method for establishing library entry points, you can mitigate this problem by just reassigning vectors (new apps bind to the new, fixed vector; and old apps get the old vector, whose bugs are emulated for no more than two major releases).

    Schwab

  28. Re:Hate to quote a quote but... by Sputum · · Score: 4, Insightful
    This tool is not designed for use or supported in enterprise environments.

    I see. The tool wasn't designed for use. They just made it available for download so we could all see what a tool would look like if one were available.

    --
    "What we imagine is order is merely the prevailing form of chaos"
  29. Re:Hate to quote a quote but... by G-funk · · Score: 2, Insightful

    Also, in all english speaking countries that aren't bordering with the US, they're pronounced totally differently.

    --
    Send lawyers, guns, and money!