Slashdot Mirror


MS Cites National Security to Justify Closed Source

guacamolefoo writes: "It was recently reported in eWeek that "A senior Microsoft Corp. executive told a federal court last week that sharing information with competitors could damage national security and even threaten the U.S. war effort in Afghanistan. He later acknowledged that some Microsoft code was so flawed it could not be safely disclosed." (Emphasis added.) The follow up from Microsoft is even better: As a result of the flaws, Microsoft has asked the court to allow a "national security" carve-out from the requirement that any code or API's be made public. Microsoft has therefore taken the position that their code is so bad that it must kept secret to keep people from being killed by it. Windows - the Pinto of the 21st century."

254 of 717 comments (clear)

  1. War by qslack · · Score: 5, Funny

    War is always the best excuse. One of my favorite cartoons on this is Mark Fiore's, at http://markfiore.com/animation/excuse.html. :)

  2. Nice by jayhawk88 · · Score: 5, Interesting

    When in doubt, raise concerns about terrorism, or inappropriately use 9/11 as a crutch. The new coin of Washington (both east and west it seems).

    Nothing will ever be the same again indeed.

    1. Re: Nice by Black+Parrot · · Score: 3, Funny


      > When in doubt, raise concerns about terrorism, or inappropriately use 9/11 as a crutch. The new coin of Washington (both east and west it seems).

      It's not just the USA. Want to wage war on a neighbor or on members of your own population? Just go ahead, and call it "War on Terrorism (tm)" if anyone expresses outrage over it.

      --
      Sheesh, evil *and* a jerk. -- Jade
    2. Re:Nice by bryan1945 · · Score: 2

      Or when in doubt, just remember the Navy ship that totally crashed when Windows BSOD.

      Which is worse- MS claiming that it would be bad to disclose their code and possibly compromise the OS, or just plug it in and have a multimillion ship need a tug into port?

      --
      Vote monkeys into Congress. They are cheaper and more trustworthy.
    3. Re:Nice by harlows_monkeys · · Score: 2
      Or when in doubt, just remember the Navy ship that totally crashed when Windows BSOD


      Wrong. An application crashed because it did not handle divide by zero (exactly the same thing that happens on Linux). The ship depended on that application, and so stopped working (exactly the same thing that would have happened had they used Linux instead of NT).

    4. Re:Nice by Moofie · · Score: 3, Insightful

      Look, I don't care WHAT the problem was. A military vessel is explicitly designed to keep working even if parts of it get destroyed. I would expect the vessel to continue functioning, albeit at a decreased efficiency, if I shot the computer with my sidearm.

      I don't care whose code broke...the fact that a software problem could cripple a ship is unconscionable.

      --
      Why yes, I AM a rocket scientist!
    5. Re:Nice by 1010011010 · · Score: 3, Interesting

      "Because of politics, some things are being forced on us that without political pressure we might not do, like Windows NT," Ron Redman, deputy technical director of the Fleet Introduction Division of the Aegis Program Executive Office is quoted as saying. "If it were up to me I probably would not have used Windows NT in this particular application. If we used Unix, we would have a system that has less of a tendency to go down."

      Another person at the Naval Air Warfare Center, who also requests anonymity, says: "In my view, and this is only my opinion, the move [IT 21] is not only illegal, but wrong. Moving the Navy completely towards a proprietary computer (a memo quoted states only 'Intel' computers could be purchased) and a proprietary OS (Windows) is against Navy procurement standards requiring OPEN competition. If anything, the Navy should stress compatibility, and open standards. MS Windows is not an open standard.

      David Kastrup of the Institut fur Neuroinformatik in Bochum, Germany observed last year that "The specifications call for use of Windows NT 5.0 [now Windows 2000] when available, without any prior tests for usability or whatever. This means that the military is signing a blank cheque of trust to Microsoft to deliver what their marketing hype promises.

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    6. Re:Nice by bmajik · · Score: 4, Interesting

      I agree with you (code shouldn't kill people).

      I don't see how thats microsofts problem. The government decided they wanted to use off the shelf computer equipment and software. They got sick of developing a computer system and maintaining it for 30 years. You realize that in the 80s there were software engineers that were maintaining code for submarines that had ferrous-core memory systems.

      The navy wanted to get away from that.

      So, its nice that you're mad about the navy's choice of computing infrastructure. The fact that it happened to fail has nothing whatsoever to do with microsoft, and you're being irrational about being upset with them over this.

      Not that there aren't other things to be upset with them about :)

      --
      My opinions are my own, and do not necessarily represent those of my employer.
    7. Re:Nice by femgeek · · Score: 2

      Completely off-topic to the story's subject, but that message in the logs is something I've seen in the 2.4.17 kernel as well. It has to do with the network driver, I believe. Upgrading to 2.4.18 got rid of it, FYI.

      - Jen

      --
      Do not meddle in the affairs of dragons,
      for you are crunchy, and taste good with ketchup.
    8. Re:Nice by Moofie · · Score: 2

      I understand that Microsoft gets away with the "this program is not suitable for any use at any time" crap with the public, but the Navy must demand higher performance.

      Is it Microsoft's fault? Depends on how involved they were with the systemn integration. The ISV bears primary responsibility for this problem.

      --
      Why yes, I AM a rocket scientist!
    9. Re:Nice by crucini · · Score: 2
      That caused the database to overflow and crash all LAN consoles and miniature remote terminal units.
      --Vice Admiral Henry Giffin

      Certainly the application was to blame, but if a large number of computers crashed due to data received over the network from one crashing computer, the OS used is probably not robust enough for this application.
    10. Re:Nice by mpe · · Score: 2

      Look, I don't care WHAT the problem was. A military vessel is explicitly designed to keep working even if parts of it get destroyed.

      Or at least that should be a basic design criteria.

      I would expect the vessel to continue functioning, albeit at a decreased efficiency, if I shot the computer with my sidearm.

      Shooting it with a pistol should do nothing at all to the actual control system. Just possibly break the input devices. Warships tend to be targeted by ordinance a lot more destructive than anything remotly man portable. A control system should be capable of withstanding at least one direct hit from a, non nuclear, anti ship missile.

    11. Re:Nice by Salsaman · · Score: 2
      The fact is that an application crashing should not bring down the entire OS.

      That is a sign of very poorly designed software.

    12. Re:Nice by mpe · · Score: 2

      I don't see how thats microsofts problem.

      You don't think it is possible that Microsoft could have lobbied the USN.

      The government decided they wanted to use off the shelf computer equipment and software. They got sick of developing a computer system and maintaining it for 30 years.

      As opposed to a system which will probably need a complete overhaul ever 5 years...

      You realize that in the 80s there were software engineers that were maintaining code for submarines that had ferrous-core memory systems.

      This being the same Navy which reactivated 4 Iowa class WWII designed battle cruisers around the same time.
      A lot of military hardware is fairly old. Military commanders tend to prefer it that way because it means that the behaviour of any machine is well understood. With as many of the bugs as possible shaken out.

      So, its nice that you're mad about the navy's choice of computing infrastructure. The fact that it happened to fail has nothing whatsoever to do with microsoft, and you're being irrational about being upset with them over this.

      Except that Microsoft's basic approach to making and selling software is completly inappropriate for the vast majority of military applications. Microsoft just don't provide reliablity or long term support. They don't need to buy warship XP they need the bugs in warship 85, 75 or 65 fixing. Warship XP shouldn't be considered safe to send anywhere near a shooting war until 2015...

    13. Re:Nice by opkool · · Score: 3, Insightful

      Can you please post the URLs?

      Thank you in advance.

    14. Re:Nice by bmajik · · Score: 2

      Did the OS fail or did the app fail ? The OS doesn't run the engines - the app does.

      If you show me where it says that the application crashed the operating system, then you've got something.

      Not that i'd be surprised -- we agree that if a userland app crashes the OS then there is work to be done, but i dont' think thats what happened here. The OS hosting the engine management software was NT4, and the software crashed, and i _dont_ think it took the OS with it, but its really academic since the engines stopped and the OS isn't even relevant when you're a sitting duck in the water.

      --
      My opinions are my own, and do not necessarily represent those of my employer.
    15. Re:Nice by Salsaman · · Score: 2
      Actually you can limit the number of filehandles and memory. You can do it (as root) using setrlimit(). You can also limit the cpu time, maximum file size, and the number of processes.

  3. MS sweating... by wowbagger · · Score: 4, Funny

    "Uhh, the judge is acting pissed. Did you see the way she looked at us when she said 'Obey the court'?"

    "Yeah, how can we BS her on this?"

    "Uhh, maybe we can find a link to terrorism?"

    "YEA! That's it! We can't comply, because of National Security"

    Harmph....

    1. Re:MS sweating... by Anonymous Coward · · Score: 2, Insightful

      In all seriousness, *is* the judge pissed in this case? I mean, how is the judge reacting? Does the judge seem to be able to tell when MS is BSing? Does the judge seem to be annoyed at the constant flagrant violations of the law and everything that makes the court system work?

      Basically, who seems to be winning over the judge so far? I realize the judge is going to avoid showing any emotion at all, since if the judge indicates that she has any opinon at all on the case this displays "bias" or something, but how is she acting within the case? Is she reprimanding MS when they do fucked up shit?

    2. Re:MS sweating... by jcr · · Score: 2

      In all seriousness, *is* the judge pissed in this case?

      Of course she's pissed. Judges don't like defendants who lie to them.

      Keep in mind, the appeals court didn't reject the breakup order out of hand. They sent the sentencing to judge Kotelly because Jackson talked to the press before the breakup was a done deal.

      He should have waited ten years before telling the world just how badly MS fucked up in his courtroom.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
  4. You have the emphasis wrong. by NoMoreNicksLeft · · Score: 2, Troll
    He later acknowledged that some Microsoft code was so flawed it could not be safely disclosed.

    Any fool knows that it is flawed to that magnitude. Only the fact that it was publically admitted by a M$ official is newsworthy.

  5. Now what are they trying to hide? by CoolVibe · · Score: 4, Interesting
    Microsoft code and national security? Hmm... Interesting :) Also another good question is: whose national security, als lots of foreign governments use Microsoft software.

    Worrying isn't it?

    1. Re:Now what are they trying to hide? by edrugtrader · · Score: 2, Interesting

      so if afghanistan uses MS... wouldn't releasing the source code allow us to end afghan terrorism by crippling their computer systems?

      --
      MARIJUANA, SHROOMS, X: ONLINE?! - E
    2. Re:Now what are they trying to hide? by cybermage · · Score: 4, Funny

      Worrying isn't it?

      I figure if Microsoft code was handling anything important, we'd be dead already. The concept adds a whole new meaning to BSOD.

    3. Re:Now what are they trying to hide? by bricriu · · Score: 2, Insightful

      Isn't this the company that was proposed as a gatekeeper to our government -- that is, use Passport to authenticate citizens?

      Disgusting.

      --

      AHHHHHHH! I'm burning with goodness again!
      - Reakk, Sluggy Freelance

    4. Re:Now what are they trying to hide? by zerocool^ · · Score: 2

      God:
      Come toward the blue light my son. Yes. Uh huh. No, no, ignore the zero memory reference error.

      ~Will

      --
      sig?
    5. Re:Now what are they trying to hide? by Admiral+Burrito · · Score: 2

      I figure if Microsoft code was handling anything important, we'd be dead already.

      Do you consider an Aegis cruiser "something important"? That's a bit dated now, of course. Hopefully they would've learned their lesson back then. (Yeah, right.)

  6. Hypocrits by Telastyn · · Score: 5, Interesting

    If the code is so bad as to be dangerous, shouldn't the government make them recall the code and return a properly functioning version?

    If a car was dangerous enough to possibly cause death, wouldn't the government require a recall? Wouldn't the media jump on them like rabid wolves like they did Firestone? Wouldn't people avoid the things like they did Firestone?

    1. Re:Hypocrits by pjt48108 · · Score: 3, Funny

      The problem here is that M$ is proprietary, and won't release their code. Therefore, government agencies cannot verify such claims of bad code. Also, one must agree not to disclose bugs in M$ software or face prosecution. In the end, the governmetn shuld do what the gov't of Chile has done, and require the use of free (...of proprietary code, etc.) software in all gov't operations.

      But, I agree... I'd love to see the gov't return MS stuff and REQUIRE working code. Watch M$ reply with a RedHat CD.

      --
      Mmmmmm... Bold, yet refreshing!
    2. Re:Hypocrits by MxTxL · · Score: 3, Insightful
      From Fight Club:

      I'm a recall coordinator. My job is to apply the formula....

      Take the number of vehicles in the field, (A), and multiply it by the probable rate of failure, (B), then multiply the result by the average out-of-court settlement, (C). A times B times C equals X...

      If X is less than the cost of a recall, we don't do one.


      In other words, if it is cheaper to pay off everyone neccessary to prevent a recall than to actually do one, they don't do one.

    3. Re:Hypocrits by Telastyn · · Score: 2

      True, though isn't the point of the story that they admitted to such things? Perhaps it's just one guy that is out of line, but it's another thing to add to the mounting list of circumstantial evidence.

    4. Re:Hypocrits by Midnight+Thunder · · Score: 2
      Although I am a big supporter of open source, I also believe that it is not the solution for every software project. Some companies depend on the income generated by closed source software, epecially when it is a question of ensuring that client companies don't simply take the code and walk.

      If your investors have provided the company $1 million for development of the software, the company needs to ensure that they will recup the money and also make some money, otherwise what's the point of the investment?

      One clause the could always be provided in any contract, is that if the company goes bankrupt, or kills a product with no suitable replacement, the code should be provided open source. Or maybe, like a patent, after 15 years the code gets opened. In the meantime the code would be kept secure with a government agency assigned to the task. But then again this is wishful thinking.

      Intellectual motivation is great, but it doesn't motivate all people and sometimes greed is the greatest motivator. Sad but true!

      --
      Jumpstart the tartan drive.
    5. Re:Hypocrits by interiot · · Score: 2

      Like it or not, this is in line with the government's stance towards possible problems at nuclear power plants: remove plant blueprints and other detailed information from public access.

    6. Re:Hypocrits by Asicath · · Score: 2, Interesting

      Say a car company was in the same position as microsoft: They are being sued for creating a monopoly on cup holders. Their cars come with cup holders installed and therefore 3rd party cupholder manufacturers are going out of buisness. Now the car company says they cant possibly remove the cupholders from the cars design because it they are essential for making the car run (a lie, but they've got enough money to back it up).

      Now on this car there is a secret button that unlocks the cars doors and starts the engine. It can only be found by maticulously taking the car completly apart 200 times or by reading the blueprint.

      If this car makes up 90% of all the cars owned in america, should they make this blueprint public over a small issue like a cupholder?

    7. Re:Hypocrits by deblau · · Score: 2, Insightful
      I'm sorry, but I must point out a flaw in your argument.
      If a car was dangerous enough to possibly cause death, wouldn't the government require a recall?
      That argument doesn't really work. Cars do kill people, thousands a year in the US alone. But we keep using them. The point is, that they kill when used improperly, which is, I think, your point.

      Going back to your first statement:

      If the code is so bad as to be dangerous, shouldn't the government make them recall the code and return a properly functioning version?
      Add the words "when used improperly", and your argument falls apart. All software can be dangerous (erase hard drives, destroy financial records, DoS some ISP) when used improperly. And yes, I mean all software. I have yet to see a program that does anything non-trivial that is completely secure. So no, the government shouldn't request a recall.

      However, there are regulations about manufacture of automobiles which help to prevent them from doing damage when used improperly, such as seatbelts and crash resistance regs, and so on. I see no reason similar regs shouldn't be enforceable, i.e. give teeth to warranties of merchantability for software. If Microsoft could get sued because their software caused unreasonable downtime (because of the warranty), you'd see security improve. And yes, getting cracked qualifies as unreasonable under the contract between you and Microsoft. If you don't like it, buy something else.

      --
      This post expresses my opinion, not that of my employer. And yes, IAAL.
    8. Re:Hypocrits by billcopc · · Score: 2, Insightful

      The whole closed-source model is flawed. The only things I think should be closed are games and other non-business-critical things. If your business heavily depends on some piece of software, then write it in-house or at least hire some qualified people to do it, rather than buy whatever Gates or Ellison want you to use. One way or another, it's just a huge lump of money that's being tossed around different pockets.

      Closed source wastes money and people on marketing and advertising and all that bullshit, but creates a profit in the end, from selling the software.

      Open source keeps things clean by only requiring developers/artists/a manager. No marketing, little waste. But you don't make any profit other than the use of your own software.

      Either way, programmers are being paid. The difference is that for closed source you have one ugly prick sitting on top of the company getting rich from doing absolutely nothing.

      Indeed, open source looks alot like communism from the dollar bill's point of view, whereas closed source is rooted deeply in capitalism, i.e. the rich getting richer at the expense of the poor.

      The solution to this dilemma obviously depends on which end of the social hierarchy you're closest to.

      --
      -Billco, Fnarg.com
    9. Re:Hypocrits by notsoanonymouscoward · · Score: 4, Insightful

      have you thought this through? What about interoperability? Modularity? If you worked like this, pretty much all NON software companys would end up doing everything in house, which is of course, not what they are in the business of doing. There is a reason microsoft exists. There is a reason someone is on top.

      --
      I ate my sig.
    10. Re:Hypocrits by Telastyn · · Score: 2

      No. I mean if the car was so poorly designed that when it hit a bump it blew up. IMO it's wholy reasonable to want a car I bought to drive over a bump properly.

      Furthermore I don't think it's unreasonable to expect win2k to run with multiple processes and not crash.

      win2k of course does this fairly well (even if other windows versions don't). So what about a better analogy?

      How about I expect my car to have a totally contained gas tank? I wouldn't want Joe Somebody to just walk up to it, and toss a match in...

      Windows (all versions) have SERIOUS problems with the code base, that like the open gas tank, are only concealed because nobody knows the tank is open, and nobody can look to see if it is open.

      Until of course someone comes along and tosses a match in. It's criminal negligence, which does not require improper use to be dangerous.

    11. Re:Hypocrits by Jburkholder · · Score: 2

      Yep, I remember learning about something like that in soc101

      Company realizes that product is defective and estimates it will cause x thousand accidents, y hundred serious injuries and z deaths. Cost of recall will be n million dollars.

      Figure out the anticipated cost of liability suits for accidents, injuries and deaths and if it is more than the cost of the recall then you do the recall.

      If not, congratulations... you have just put a dollar figure on a human life.

      No shit. This was a real example of leaked internal documents.

      "Well, we didn't really use that as the basis for our decision... we just made sure we analyzed it from every possible angle."

      (I did a couple searched on Google and couldn't find anything to back this up, sorry.)

    12. Re:Hypocrits by bmajik · · Score: 3, Informative

      Microsoft never made the statement that "this product is bug free, and has no security concerns whatsoever".

      The statement is, and always has been "we fix what we know about, if it wont break too much other stuff".

      Incidentally, within some egregious time window (10 years ?) they fix it for free.

      Thats the tradeoff the government willfully made when it wanted to use an off the shelf operating system, instead of doing it in house or submitting bids for a custom contract. (software that requires an ongoing support contract for security issues or _any_ issue at all)

      What you're asking for would be something like an A1 system under the old pre-Common Criteria scheme... i.e. a provably correct system.

      Guess how many products received A1 certs. Theres a list of some of them. It wouldn't take a long time to load the html. Even at 300bps.

      --
      My opinions are my own, and do not necessarily represent those of my employer.
    13. Re:Hypocrits by walt-sjc · · Score: 2

      Dude, you are confusing "open source" with "free software". You can have an open source product that requires a license for certain uses. There are lots of cases where you have software that's free for eval only, or maybe personal use only, educational use, etc. Just because you provide source doesn't prohibit you from making money on it, restricting distribution, etc.

      One of the problems we have today is the definition of "open source." Some people feel that it needs to have a GPL like license, others think BSD is OK, others think that it just means that source is available to anyone that wants to look at it. This variety of definitions causes much confusion.

    14. Re:Hypocrits by walt-sjc · · Score: 2
      The statement is, and always has been "we fix what we know about, if it wont break too much other stuff".

      Hmm. The problem is that they KNOW the code is broken, yet they are only fixing the stuff other people find. That statement is therefore a lie. To know that your code sucks and to do nothing until someone else find out about a problem violates the very essence of the "trustworthy computing" initiative. Why should we trust the software when MS says it's crap?

    15. Re:Hypocrits by Dwonis · · Score: 2

      No, there aren't. Open Source is defined by the Open Source Definition (which is basically the Debian Free Software Guidelines, by the way).

    16. Re:Hypocrits by Swaffs · · Score: 2

      The formula doesn't take into account the cost of bad publicity however. That's why that formula isn't really used by car manufacturers.

      --

      --
      "Karma can only be portioned out by the cosmos." - Homer Simpson [1F10]

    17. Re:Hypocrits by MulluskO · · Score: 2

      No, that's why when manufacturers decide not to issue a recall, they strong-arm thier victims into settlements with non-disclosure clauses.

      --

      Too busy staying alive... ~ R.A.
    18. Re:Hypocrits by MulluskO · · Score: 2

      Thinking about this, how do we know this hasn't already been done by Microsoft?

      --

      Too busy staying alive... ~ R.A.
    19. Re:Hypocrits by Convergence · · Score: 2

      Yup...

      And thats reasonably as they should be.. Money isn't free. Its like any other tradeoff where you trade safety for price. Why do my workplace building not have 3 meter reinforced concrete walls (to protect your house from meteors, crashing planes, and nearby truck bombs.)

      Would you be willing ot pay twice as much for a car thats 30% safer?

      This is just more of the same.. If the recall costs more than paying off the mistakes, why is that any worse than your workplace not putting up 3 meter walls?

      FYI, there is already a price on a human life, about 1-2 million dollars. This price was arrived at by the DOT, by looking at peoples willingness to pay for safety systems.

    20. Re:Hypocrits by mpe · · Score: 2

      The problem here is that M$ is proprietary, and won't release their code. Therefore, government agencies cannot verify such claims of bad code.

      Not being able to see the code makes it difficult to see if the code is good. You can see if the code is bad through it's behaviour....

      Also, one must agree not to disclose bugs in M$ software or face prosecution.

      Governments generally cannot be prosecuted. The only action Microsoft could take would be to become a terrorist organisation.

    21. Re:Hypocrits by mpe · · Score: 2

      have you thought this through? What about interoperability? Modularity? If you worked like this, pretty much all NON software companys would end up doing everything in house, which is of course, not what they are in the business of doing.

      Most companies are not in the building business, nor are they in the pumbing business, nor telecoms, nor electricians, etc. All these cases involve assembling components which are highly modular and interoperable. Why should software be treated differently from any other infrastructure? A

      There is a reason microsoft exists.

      Problem is that Microsoft produces a "one size fits all" type entity. Then expects you to both bend your business to fit the way their software works and to upgrade to their time schedule.

    22. Re:Hypocrits by mpe · · Score: 2

      The formula doesn't take into account the cost of bad publicity however. That's why that formula isn't really used by car manufacturers.

      More that a judge found out what they were doing and imposed a fine of serveral times what it would have cost them to fix it.

    23. Re:Hypocrits by mpe · · Score: 2

      Microsoft never made the statement that "this product is bug free, and has no security concerns whatsoever".

      They more often claim that they don't guarentee that it will do anything.

      The statement is, and always has been "we fix what we know about, if it wont break too much other stuff".

      "If we happen to agree that it is broken..."

      Incidentally, within some egregious time window (10 years ?) they fix it for free.

      For military applications 10 years is just getting started. For applications related to government then 10 years just dosn't cut it.

      Thats the tradeoff the government willfully made when it wanted to use an off the shelf operating system, instead of doing it in house or submitting bids for a custom contract. (software that requires an ongoing support contract for security issues or _any_ issue at all)

      If they do it with a software company in their own country then the chances of getting a decent product at the end are remote. Software companies just don't operate in the long term. Dealing with a foriegn software company is effectivly high treason.

      What you're asking for would be something like an A1 system under the old pre-Common Criteria scheme... i.e. a provably correct system.

      WHich you have even less chance of getting with a COTS approach.

    24. Re:Hypocrits by Noel · · Score: 2
      Microsoft never made the statement that "this product is bug free, and has no security concerns whatsoever"

      Well, not quite, anyway

      There are no significant bugs in our released software that any significant number of users want fixed.

    25. Re:Hypocrits by da3dAlus · · Score: 2

      Actually, that was Tyler Durden talking to the lady on the plane in "Fight Club"...but yeah, same point.

      --

      Sometimes I doubt your commitment to Sparkle Motion.
    26. Re:Hypocrits by Dwonis · · Score: 2
      That "one group" (namely Eric S. Raymond) coined the term "Open Source", which makes it a little more authoritative than, say, Microsoft.

      Perhaps you could clarify your point?

    27. Re:Hypocrits by notsoanonymouscoward · · Score: 2

      it is true that MS has become an unruly beast... but they did create the tools and standards which put them on top. Theres this little thing called windows which opened up the door to many applications Linux STILL doesn't have easy user access to. Pull YOUR head out of tux's @$$ and take a look around. Haven't you ever thought of MS as a standard?

      --
      I ate my sig.
    28. Re:Hypocrits by Jburkholder · · Score: 2

      Well, this was in 1986... a little before fight club (which I've actually never seen)

  7. Pintos should be offended... by cansas · · Score: 5, Funny

    The Pinto was never as dangerous as M$ products.

  8. Equality by jaavaaguru · · Score: 3, Interesting

    So they think that just because they are Microsoft, they deserve to be treated differently? If they made crap software that is full of bugs, and it gets released to other companies who my possibly take advantage of those bugs, then it's their own fault. If a product is meant to be remotely secure, the software company should employ QA teams to *TRY* and break into it, at the VERY LEAST. Writing poor code is no excuse for avoiding your punishment, MS. Perhaps those using the buggy software should be informed of this, and given a grace period to switch to another system before MS is made to open their source.

    1. Re:Equality by blonde+rser · · Score: 2

      I don't think they're argument is one of "deserve" or "justice" or "rightiousness." What they are saying is that, at a purely pragmatic level, it is in everybodies best interest to keep the code from being released. This is an argument that the courts often do take into consideration.

    2. Re:Equality by walt-sjc · · Score: 2

      Writting code that interprets untrusted, unknown code (HTML, javascript, etc.) in a secure fashion is HARD. I don't have a problem with the fact that IE has bugs, I have a problem with MS's attitude. I have a problem with "security by obscurity", and the response that the lack of security is due to customer demand.

      I REALLY have a problem with outlook's vulnerability to viruses. MS's response to that has always been that customers demand the ability to auto-execute email content. Pah. MS has always shipped software with all features (security holes) enabled by default, requiring customers to do massive hardening of a new system (which most consumers and MCSE's don't have the brainpower to do.)

  9. Re:Don't pick on me! My software sucks! by CoolVibe · · Score: 4, Funny
    Just count your lucky stars that Microsoft software isn't guiding ICBMs to their target...

    Well, at least I hope it doesn't. A comment like this from a Microsoft bigwig doesn't sound encouraging... Mid-air GPF anyone? *ouch*

  10. er, by Xzzy · · Score: 5, Insightful

    From the story:

    > The protocol, which is part of Message Queuing,
    > contains a coding mistake that would threaten the
    > security of enterprise systems using it if it were
    > disclosed, Allchin said.

    Then with all the billions and billions of dollars M$ has hanging out in the bank, why not hire someone and FIX THE PROBLEM. What's the problem with doing the things that make sense?!

    Single best thing M$ could do to improve their product security is to adopt the 'patch often' mindset. Fix something, release a patch, everyone goes home happy.

    The bi-annual (exaggeration) security patches they currently do ain't gonna do it.

    1. Re:er, by cperciva · · Score: 4, Insightful

      Single best thing M$ could do to improve their product security is to adopt the 'patch often' mindset. Fix something, release a patch, everyone goes home happy.

      That's great in theory, but the real world doesn't work like that. In the real world, it is very hard to get everyone to apply patches, and the software vendor gets blamed even when they've made the patches available months earlier; Code Red is a perfect example of this.

      In the context of system administrators who forget to patch their boxes, you actually end up with better security if you release a large patch every month than if you release small patches every few days.

    2. Re:er, by bobdehnhardt · · Score: 5, Insightful

      Never will happen. Releasing patches often would give the average users the idea that "this software is crap, they keep finding problems with it, that little Updates thingie keeps popping up and annoying me, why didn't they get it right the first time?" Far better to release one mega-patch every 6-9 months, label it a "Service Pack", and stress the "enhancements" over "bug fixes". At least, that's how Microsoft seems to view it.

      Microsoft is all about perception. They learned long ago that they can release pure shite as long as the general public perceives it as good. And that can be accomplished through Marketing, which is much easier to craft and control than Coding....

    3. Re:er, by elmegil · · Score: 2

      B.S. Sun Microsystems releases patches for Solaris quite often, and we're a market leader for commercial Unix systems.

      --
      7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
    4. Re:er, by larien · · Score: 2
      Which is why open protocols, subject to open review, are better...

      It really worries me that MS are now effectively admitting "our code sucks, and we can't fix it".

    5. Re:er, by joshamania · · Score: 2

      You should do both. That's what Hotfixes and Service Packs are for...except that M$ only fixes what it has to...not what it should.

    6. Re:er, by CoolVibe · · Score: 2

      WHAT?!?! Microsoft software has BUGS that could COMPROMISE SECURITY? *gasp* oh no!??!
      </sarcasm>

      Like that's new.. They should read NTBugTraq every once in a while then. Heck, even open source software has bugs. Code I write has bugs. Heck, that's a fact of life. And yes, sometimes they can compromise security.

      Their big mistake is not opening the code. Maybe some malicious underground cracker already figured out how to exploit this. You don't know. It's Security Through Obscurity, and will NEVER work.

      Great going Microsoft. Keep on going like that. I'll be waiting for the outcome.

    7. Re:er, by innocent_white_lamb · · Score: 2, Insightful

      B.S. Sun Microsystems releases patches for Solaris quite often, and we're a market leader for commercial Unix systems.

      But Sun isn't peddling their software to Joe Blogg's grandmother either.

      Perception is important in marketing; in fact, it's about the only thing that really is important when you get right to the basics. And MS wants to avoid fostering the perception that their software is "not right" in the minds of the average man-on-the-street. Frequent patches would undermine this effort.

      --
      If you're a zombie and you know it, bite your friend!
    8. Re:er, by markmoss · · Score: 2

      Not to mention the patches that unexpectedly break something else, in a few of the million different configurations out there...

    9. Re:er, by HiredMan · · Score: 3, Funny
      From the story:
      The protocol, which is part of Message Queuing, contains a coding mistake that would threaten the security of enterprise systems using it if it were disclosed, Allchin said.


      "That's business with .Net."


      =tkk

    10. Re:er, by mangu · · Score: 2

      it is very hard to get everyone to apply patches

      That doesn't apply to the military. Just create a "patch officer" position and make it his duty to apply patches.

    11. Re:er, by Danse · · Score: 2

      It doesn't need to be everybody patching. Just the people that run important systems. One would hope that they would be competent enough to patch their systems. Hell, I'm just a lowly jr. grunt db/app programmer and I can keep my boxes patched. Any sysadmin out there who is paid to keep their systems up and running should be able to do at least as much. If they can't, then there is a problem. Either they are using software that is innappropriate for the task, or they aren't competent enough for their job. The first may or may not be their fault, but the second would be.

      --
      It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
    12. Re:er, by Anonymous Coward · · Score: 3, Interesting
      IBM did something similar with the input queue on OS/2. They had a design problem that was part of a bad design from the very start. Everyone knew it. Why wasn't it fixed? It was going to require user programs to be fixed as part of the fix. It was a critical architectural failure when they started OS/2 2.0 under duress, they had some hard and critical deadlines to meet and they botched that piece of the equation. What's the alternative? You require a huge number of apps to be, at the very least, recompiled? That's barely practical with something like Linux, have any idea it takes to get full distribution up an running on a different architecture? Long enough that the biggest Linux companies still only support a handful of what GNU/Linux runs on. IBM didn't fix it, in fact some very good software engineers resorted to doing some fairly cheap hacks to try and get around it. When you start putting bandaids on the core, things are getting bad and it's only a matter of time, you've started to calcify the product. It's a bitch, what else do you do?


      How many of you kids remember a.out to elf? Or the switch from libc to glibc? Any of you try to upgrade through that yourself without reinstalling a new distribution? Think of both of those, multiply it by 10000 and throw a couple major security holes in that the entire world may not be privy to. Then you are starting to scratch the surface of how large this problem is. On top of that why not factor in some bullying from the MS sales force, how many larger MS customers have been bullied at one point or other? Probably enough that if they were told they have to replace everything some of them would get really pissed off and seriously think about shopping elsewhere.


      MS fucked up and they fucked up bigtime. They need more time too, they've got .NET in the pipe and they're porting their apps to it but they will need to rebuild the platform. I think the NT platform is starting to get to a good time when it's fair to look at complete rewrite or some kind of major overhaul but they need to time it right so that linux doesn't hurt them too badly and they are also going to need a culture change, you have to build large systems with lot's of abstraction and heirarchy, they want to put too much into kernel land and it's only going to make security problems harder to solve down the road and open up more parts of the OS to different kinds of attacks. 10 to 1 the queue holes involve sending messages as if an aplication has passed a security boundary and that they allow you almost free reign, it's something that almost doesn't apply to other platforms.

    13. Re:er, by bmajik · · Score: 2

      Sun is no champion of providing timely security patches. The latency between bug submission on bug traq and time to patch release was something like 9 months for a specific remote-root rpc compromise.

      Granted, thats not the norm, but thats a pretty poor showing.

      The only mainstream unix with a non-utter-fucking-joke security story is OpenBSD. And its patch story is somewhat less than desireable (no binary patches, although projects to do that "unofficially" keep getting kicked around. sometimes, people arne't in the mood to make world just to put off script kiddies)

      --
      My opinions are my own, and do not necessarily represent those of my employer.
    14. Re:er, by fferreres · · Score: 2

      Microsoft is all about perception. They learned long ago that they can release pure shite as long as the general public perceives it as good. And that can be accomplished through Marketing, which is much easier to craft and control than Coding....

      Not Marketing. I think it is leveraging and delivering what the users wont (be it a good or bad thing).

      Everyone can use Windows. Everyone has been using Windows. Some few people use Linux. Most nobody used *nixes in the past. (everyone: as in "mostly everyone")

      Things are changing because Unix is delivering something that more and more people are asking for: security, stability and usability.

      MS is trying to block the past, but if *nixes keep on delievering what the mayority wont, they will succed.

      No amount of marketing is going to make OpenOffice better (in terms of what average joe likes more) that MSOffice. It's won't happen, as people notice from the very second when they don't initialy like something.

      So, to make *nixes widespread you need to address the concerns on people that also care about "usability", "niceness", "easiness", "dumbedness". If and only if can *nixes satisfy this group, it will be widespread.

      The marketing is fine. But it's not the way MS has pushed their products into people. Leveraging the OS, controlling the OEMs and delivering what people "in the surface" want did the job.

      --
      unfinished: (adj.)
    15. Re:er, by IronChef · · Score: 2

      What's the problem with doing the things that make sense?!

      I have been working at Microsoft for about 1 month. I expected it to be a staggeringly inefficient operation, full of red tape, political infighting and all that.

      I was wrong. It is far, far worse than I ever imagined.

      Someone at MS may very wish to fix this particular problem, but when you factor in the considerable BS... well, there's a lot of intertial there. A hell of a lot.

      Frankly I am amazed that anything gets done there.

    16. Re:er, by walt-sjc · · Score: 2

      Hmm. Insightful. Hmm.

      The problem with the current scheme is patch hell. MS has service packs and hot fixes. What admins have frequently found is that hot fixes can break your system. Patches depend on other patches and service packs requiring a very specific installation sequence. Maintaining all these patches on hundreds of servers is a nightmare.

      What MS does NOT do often enough is roll-up patches into a new service pack. The last service pack for Win2000 was over a year ago. There are DOZENS of patches since then. There is NO excuse for this.

    17. Re:er, by Maserati · · Score: 2
      Here you go. It takes a Windows 2000/NT 4.0 network to do it, and Active Directory is needed to get the hotfixes out.

      You use a couple of utilities in combination to identify patches. hfnetchk.exe scans a network of 2K/4.0 machines and generates a report. qchain.exe allows you to apply multiple hotfixes without restarting; a batch file is created to apple each patch in sequence, with appropriate switches. Then you use ActiveDirectory to push the batch file out to be applied at the next login. I actually like doing it at logout , but I'd rather get everything applied asap instead of any aesthetic utility of applying a patch when the user is done and won't notice the extra restart.


      For bonus points, you automate running hfnetchk, gathering hotfixe files, assembling qchain batch files, and pushing them out to the right machines in AD. Hint: a lot of this data is in, or can be represented as, XML. Emailed reports are good, html statistics are good. I'm not in a Win2K shop any more, but getting this running was going to be my blackbelt project. Thank you Osama and post 911 economic nuttiness.

      --
      Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
    18. Re:er, by shani · · Score: 2

      B.S. Sun Microsystems releases patches for Solaris quite often, and we're a market leader for commercial Unix systems.

      Lord knows why though. My most recent patch story with Sun was horrible.

      In December our sysadmin foolishly applied the "Recommended Patch Set" from Sun, and our main application started leaking memory like a sieve. Since there were literally dozens of patches in the set, our sysadmin was very nervous about trying to track down which one was the problem and removing only it.

      After a few painful days of debugging, I tracked it down to resolving a hostname from a multithreaded application. I produced a 30 line program to duplicate the result, and handed it our sysadmin, who contacted Sun.

      It took Sun over a month to duplicate the result on their machines, even with the source code. When the finally did, they said "we duplicated the problem, and it's in Solaris 8 and the soon-to-be-released Solaris 9, and we're not going to fix it". My God.

      So up the chain of command the request goes, and Sun finally agrees to fix it, because one of their large American customers asked them to. Translation: when one of our customers that we care about asks us to do something, we'll do it. The hundreds of thousands of Euros we've spent over the last few years on Sun's crappy slow boxes apparently don't mean a damn thing.

      Sun is kind of the Jaba the Hut to Microsoft's Empire. They're no less evil, just less good at what they do.

    19. Re:er, by Tony-A · · Score: 2

      Maybe some malicious underground cracker already figured out how to exploit this. You don't know. It's Security Through Obscurity, and will NEVER work.
      Oh, I dunno. Seems like Security through Obscurity is working for the crackers.
      BTW, "this" is singular. Surely you don't think there's just one?

    20. Re:er, by CoolVibe · · Score: 2
      Yup, it will only work for those kind of people, not for mig multinationals in the public eye. They should know they got nothing to hide from us ;)

      Oh, of course there's probably more. Just blame my english, I'm not a native speaker. So there :)

    21. Re:er, by Tony-A · · Score: 2

      Oh, it's not your English. It's that everybody seems to be assuming that there's only ONE of them and fixing that one will solve everything.

  11. This is big news... by 3Suns · · Score: 2, Interesting

    The DOJ was pressuring MS to release it's APIs etc., in the interest of fair trade. Now MS claims that doing that would put national security at risk.

    What's the solution for the DOJ (who holds the reigns now)?? Simple: force MS to adopt open standards and open code modules in the future. Given that the MS business model is based on leveraging its "secret" elements, this could force them to abandon nearly all of their anticompetitive practices.

    --

    -3Suns

    ~~~~
    The Revolution will be Slashdotted
  12. More Lawsuits Now? by Asikaa · · Score: 2, Insightful

    If Ford were to say that they couldn't disclose their new transmission design because if they did it might get people killed, surely they would have to either redesign it, recall it or face a HUGE class-action lawsuit.

    All we need is some documented evidence of a MS exploit resulting in injury or death. :)

    --

    Asikaa
    Come in, twenty-seventy-seventy, your time is up.

    1. Re:More Lawsuits Now? by TheFlu · · Score: 2

      I'm willing to volunteer for this. I wasn't really doing anything anyway, so if somebody wants to hit me over the head really hard with a Windows box...

  13. *Yawn* I think someone from Peru said it best ... by smoondog · · Score: 5, Insightful

    (From a story posted here)

    Peruvian Congressman David Villanueva Nuñez made exactly this argument:

    To guarantee national security or the security of the State, it is indispensable to be able to rely on systems without elements which allow control from a distance or the undesired transmission of information to third parties. Systems with source code freely accessible to the public are required to allow their inspection by the State itself, by the citizens, and by a large number of independent experts throughout the world. Our proposal brings further security, since the knowledge of the source code will eliminate the growing number of programs with *spy code*.

    In the same way, our proposal strengthens the security of the citizens, both in their role as legitimate owners of information managed by the state, and in their role as consumers. In this second case, by allowing the growth of a widespread availability of free software not containing *spy code* able to put at risk privacy and individual freedoms.


    The flaw here is that for windows code to posess the powers they imply, it would need to be a state secret. Perhaps it should be illegal to distribute mission critical osc across us boundaries? Windows code a state secret? I think not, anyone can reverse compile machine code.

    Micro$oft should realize that governments do not like security threats they are not able to evaluate themselves. The NSA, for example, cannot sit and tinker with windoze's security holes the way they can with OSC (open source code)...

    -Sean

  14. Playing both sides of the fence by jackaroe · · Score: 2, Interesting

    "We'll security is our top priority (http://slashdot.org/article.pl?sid=02/01/17/02592 34&mode=thread&tid=109) but until it improves, our source is a threat to national security"

  15. National Security means... by cperciva · · Score: 5, Insightful

    I think that "National Security" here means "the NSA asked us to put xyz into our code, and they'd be unhappy if it had to be removed or became public".

    Remember: Cryptanalysis has, and will, always come in fourth place after burglary, blackmail, and bribery.

  16. DRM and national security by grung0r · · Score: 2, Insightful
    "but it would include APIs that deal with anti-piracy and digital rights managment"

    Terrorism = File Sharing

    someonce call the RIAA and tell them the great news!

  17. Ugh by BlackGriffen · · Score: 2

    There's no way, if Windows was open source, that people would be able to find the flaws for themselves and patch the code. After all, only a malicious hacker would want to look at Windows source code ;), and only a fool would try to step through that labyrinth that would make Daudalus green with envy...

    BlackGriffen

    1. Re:Ugh by Darby · · Score: 2

      Most "malicious hackers" don't browse through source code, they just use exploits discovered by others.

      This is known as a "script kiddie". A hacker who is truly malicious would own your ass so fast it would make you head spin if they were so inclined.

      Most of them wouldn't even know where to begin analyzing code, let alone understand what it does.

      That's why there have never been any real hacks?

    2. Re:Ugh by mpe · · Score: 2

      Most "malicious hackers" don't browse through source code, they just use exploits discovered by others.

      Those are the so called "script kiddies". Those who find the original exploits are far likely to look at the binary. Especially with something like Windows where you have a binary monoculture. So once you discover an explot which works you can be quite sure it will work everywhere.
      Explots are against object code, not source code, a change it compiler options could easily mean that either an explit won't work or it will simply crash the target rather than circumventing security.

  18. Wow that's bold by Kraegar · · Score: 3, Insightful
    To stand in front of not only a customer, but your Government, and declare that your product is so dangerously flawed that it could cost lives.

    If it happened in any other industry (auto, aviation, train, commerce, weaponry, etc) the Government would drop their product like a dead rat (and more probably force the manufacturer into a recall). Yet Microsoft is willing to use it as a defense?

    1. Re:Wow that's bold by Arandir · · Score: 2

      Microsoft has made so many verbal blunders in this case I'm starting to suspect that they really do want the maximum possible penalty. Their defense strategy is puzzling.

      Maybe they really do want Microsoft broken up, so all their top executives can be the Big Cheese at their own BabySoft(tm).

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  19. Fear the future... by Dr.+Bent · · Score: 5, Interesting

    Three things need to happen in order for people to start getting serious about software security and reliability:

    1) A software system with 1 or more serious _known_ flaws must be used on a worldwide scale by a government agency or large company.

    2) That software must then fail.

    3) The failure must cause thousands of deaths or hundreds of billions of dollars in loss or damage.

    The result will be like the 9/11 of software...when the world wakes up and realizes that we have become so dependent on software systems for our daily lives that we actually have to start caring whether or not they work correctly. We need to start taking an engineering approach to software and KNOW (not think) that it will operate as advertised.

    I'm actually hoping that this will occur sooner than later. The later it happens, the more catastrophic the result will be and the less time we'll have to rectify the problem before it happens again.

    1. Re:Fear the future... by sparkz · · Score: 2
      The average joe-schmoe user has never though about these issues, and doesn't know how to think about them. They have no reason to suppose that MS are any worse than anyone else. They've returned their car for product-recalls, they've updated from windowsupdate.com. They're blissful in ignorance.

      I'd be willing to bet the answer would be a resounding "Yes", especially from patriotic USians.

      --
      Author, Shell Scripting : Expert Re
    2. Re:Fear the future... by Fesh · · Score: 2
      No, I think the point being made is that it's inveitable. Like the Titanic. Business keeps cutting corners, and nobody gives a flying rats's ass until a bunch of people bite it. At which point it's a national frigging emergency of epic proportions that we must legislate out of existence now , never mind that if the corners weren't cut in the first place, those people'd still be breathing.

      Nobody cares until enough somebodies get hurt. And the only reason they care then is that the perceived risk to their own precious fannies becomes high enough for them to notice. This is the way of it. It keeps happening, all through history, and we keep on ignoring it.

      *deep breath* That's something I've needed to rant about for a while. Maturity bites.

      --
      --Fesh
      Kill -9 'em all, let root@localhost sort 'em out.
  20. unsafe at any build by EccentricAnomaly · · Score: 2

    Are Microsoft's product really so vital that national security would be impacted if their security were compromised? This sounds like the Y2K hoopla all over again. There are alternatives to any microsoft product. Even if a microsoft app were so compromised that Microsoft couldn't release a bug fix -- it would only take a week or two for any orginization to migrate to new software. Sure it would be expensive, but not a threat to national security.

    --
    There are 10 types of people in this world, those who can count in binary and those who can't.
    1. Re:unsafe at any build by ConceptJunkie · · Score: 2

      I worked at a contractor for the U.S.P.S. several years ago. At the time they were using OS/2, and when 2.0 was released, they still hadn't implemented the switch from 1.2 to 1.3.

      My recollection of the version numbers may not be right, but it describes the situation. The government, for good and bad reasons, moves very slowly on these matters.

      --
      You are in a maze of twisty little passages, all alike.
    2. Re:unsafe at any build by dbrutus · · Score: 2

      I don't know about vital but there was a documented case where somebody (they never figured out whether it was Russia or just routed through Russia) was pulling jobs off of Pentagon print queues (Windows printing), printing them and putting the jobs back in the queues. I don't know if they ever patched that particular hole...

  21. Re:not so evil? by CoolVibe · · Score: 2
    Quoteth the poster:

    > This explains why innocuous commands (like touch and finger) have easy-to-remember and provocative names, while the more dangerous ones (like ld and vi) are "secure" through their "obscure" names

    And pray tell... how exactly is vi(1) dangerous? I'd call emacs a bigger violation though, but hey, I'm biased. Heck, every editor on a UNIX system should have a "secure" name then. That logic doesn't really fly.

    Runs off, before it turns in yet another editor flamefest (which is not what I am intending).

  22. Lawsuit by unformed · · Score: 2

    Has anyone considered filing a suit due to being "hacked" ( know it's not the correct term, but it gets the message across) due to a hole in MS software.

    Sure, the license makes all warranty void, but what about when they knowingly distributed insecure software.

    This offers a perfect fact for your case.

  23. Re:Ridiculous argument! by jhoger · · Score: 2, Insightful

    Agreed... the most security on their Shared Source stuff is at the level of a non-disclosure agreement.

    I think the judge will see through this ploy.

  24. News Flash!!! by eyegor · · Score: 2, Funny

    Washington
    (NAPI)- John Ashcruft today warned that al-Qaida terrorists have infiltrated several "Learning Tree" facilities over the past few months and have obtained illicit "MCSE" certificates. "With the imtimate knowledge they now have, no one who runs the Windows Operating System is safe" quavered Professor M. Druel of the University of North Dakota at Hoople. "Given the flaws we were warned of, why didn't we listen to that guy back during the trail?" Linux users (and other users of the soon-to-be banned "open-source" software) spent the days chuckling.

    --

    Don't anthropomorphize computers, they don't like it.
  25. They must be getting desperate... by gweihir · · Score: 5, Insightful

    At least that is the only explanation I can think of. Their systems are architecturally unsound and plagued by stupid design decisions, unstable interfaces and unsound implementation. It is quite obvious if you look at all the security, stability and usability (ever reinstalled Windoes?) problems they have. In addition they are still adding features like mad, thereby making the problem more serious all the time.

    My point is that they did not say anything new by admitting the problem. However by admiting it they also admit that they don't really care about security, as they certainly could have done significantly better! This casts a very bad light on other ventures like .NET and the motivations and real goals behind them.

    So why are they admitting it anyway? In my opinion MS is scared to death that open APIs would also mean stable APIs (i.e. APIs that don't change all the time) and would enable others to make Windows compatible execution environments with relative ease. The sources are also important, because the API documentation MS would give (could?) away is not complete and correct enough. So while it takes a huge effort, competitiors would be able to really find out the complete API functionality and implement it in a way so that things that run on Windows would usually run on competing products without retesting or modifications.

    As MS is not really having a good product, just an effective monopoly (by making cloning their API difficult), reasonable documentation of their APIs could kill them. At least that is what I think they believe.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted and ignored otherwise.
    1. Re:They must be getting desperate... by malakai · · Score: 3, Interesting

      I'm curious. As someone who's been programming against the win32 API for a long time now, what precisely in your opinion is not properly documented by any of the SDK's?

      Granted I don't use all aspects of the API, so perhaps parts of it are poor, but the parts I use are highly documented, examples given, and all sorts of other goodies. This is what dragged me, and many hundreds of thousands of other developers into the MS world where we make a good living building solutions to business problems.

      -me

    2. Re:They must be getting desperate... by gweihir · · Score: 3, Insightful

      I have to admit that I am not an MS programmer, so I only have reports from friends about such problems. That Windows in many of its flavours is unstable and hard to maintain is my personal impression from the few occasions I am using it (mostly gaming).

      Perhaps the best basis for my concerns is the plans of MS to withold interfaces. In the past they have given these interfaces to selected people and not to others, so they where being used by some software. For an application developer that is not a problem unless he needs the specific API. For someone wanting to make a clone of Windows that is a killer.

      The part about the sources being needed is my own dark suspicion. But I again, I did think of somebody else tryong to offer a compatible API, not somebody just using what the documentation he has says is there.

      As an example think of MS-Office using additional API functionality that is not documented in the public documentation. While that does not bother somebody like you, this is catastrophic for somebody creating a MS compatible execution environment.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted and ignored otherwise.
    3. Re:They must be getting desperate... by greenrd · · Score: 2
      Also, you or I (well I know I could, not sure if you are a programmer or not)could build (copy, clone, duplicate) MS Office.

      I think you might find it quite hard. Look at the size of Open Office. Then consider that MS Office file formats are documented poorly or not at all, and that's the big stumbling block.

    4. Re:They must be getting desperate... by Bronster · · Score: 2

      I'm curious. As someone who's been programming against the win32 API for a long time now, what precisely in your opinion is not properly documented by any of the SDK's?

      My experience (and I haven't done that much Win32 programming - mainly OLE in Excel from Activestate Perl's Win32::OLE to automate report creation) is that every single function/method is documented in excruciatingly patronising detail (the Save method saves to a file) - has a list of 10 or so different flags that you can give it (specified by nothing but a name and or an obvious description, but not a list of the all the possible options)...

      ... then the fucking example they give says Object.Save("example.xls")

      Very useful Microsoft - the documentation is simplistic and patronising, and the example is simplistic, obvious, and not at all comprohensive.

      So yes, I have a problem with Microsoft's documentation. There's a lot of it, and it's frequently at the monkey level. Low learning curve, low max-out point. Not targetted, and definitely not comprohensive.

      ( on the other hand a lot of open source projects don't have even that - but at least you don't tend to spend as many hours wading throug patronising crap - you spend the hours wading through google hits to people asking the same question on mailing lists... if you're lucky you even find people answering those questions on mailing lists! )

    5. Re:They must be getting desperate... by bmajik · · Score: 2

      Im shocked to hear a slashdotter going on a huge tirade about how shitty programming under windows is, only to find hes not actually a windows programmer.

      In some far of dream world, random assholes who are long on opinions and miserably short on facts will stop beleiving themselves to be beyond factual reproach.

      But, this is slashdot.

      --
      My opinions are my own, and do not necessarily represent those of my employer.
    6. Re:They must be getting desperate... by dbrutus · · Score: 3, Informative

      It's been pretty clear for some time that Microsoft has backed away from its prior statements that the entire Win32 API is actually documented in those SDKs and that an ISV actually has a level playing field coding against internal MS programmers. Years ago they used to claim that there was a 'chinese wall' between the OS programmers and the App programmers and that there were no secret APIs, everything was in those $3k Universal Subscription mailings and the little guy had an even shot.

      They don't do that anymore because people have reverse engineered enough of Windows and the MS apps that run on it to demonstrate conclusively that you've been fed a big fat lie. You don't have a level playing field and you never did.

      This is a multi-billion dollar fraud and in large part it's what made Microsoft the uber-monopoly it is today (this was the grounds that the DoJ should have used to go after MS). The fact that you don't know that you've been shafted years after BillG and SteveB have admitted this in interviews leaves me speechless.

    7. Re:They must be getting desperate... by HalfFlat · · Score: 2

      If it helps, I've developed and helped to develop applications under Windows 3.1 and under Windows 9x + DirectX5/6.

      I can say honestly, coding for Windows was horrible, frustrating and suprising-never-in-a-good-way. There were API specs that lied (DirectPlay3 interface anyone?) and sufficiently often, where they weren't lying, the underlying functionality was badly bugged.

      Clearly the fact that the Windows-using world hasn't entirely choked indicates that the state of play has improved. But with first hand experience, I can state that Windows was a dog to code for in the past, especially when compared with its far-from perfect peers at the time.

    8. Re:They must be getting desperate... by Tony-A · · Score: 2

      As for MS witholding interfaces, please, show me where they did that.

      Does this count?
      During his second day on the stand, Allchin conceded that Microsoft has already identified at least one protocol and two APIs that it plans to withhold from public disclosure under the security carve-out.

      which interfaces were these? what did they control?
      How many others?
      No idea. That's the crux of being witheld.

  26. Open source and security - some references by dwheeler · · Score: 4, Informative
    Ah yes, the "our APIs and code must be secret or the U.S. will crumble" defense. This is a particularly absurd claim for application programmer interfaces (APIs) - by definition, APIs are disclosed to other developers, so the only reason to "hide" them is to prevent competition. Oddly enough, the products where source code (not just the APIs) is visible have lots of quantitative evidence that they're more secure.

    It's already been revealed that some attacker got into Microsoft's network. Also, CD's with Microsoft's source have been released for various reasons over time. I have no trouble believing that some "bad guys" already have the source code. So, how do the rest of us protect ourselves from these bad guys with the source code? And from the bad guys to come who don't have it yet... but will?

    As noted in Secure Programming for Linux and Unix HOWTO, section 2.4.2, closing off source code doesn't actually halt attacks anyway. Here's the quote:

    It's been argued that a system without source code is more secure because, since there's less information available for an attacker, it should be harder for an attacker to find the vulnerabilities. This argument has a number of weaknesses, however, because although source code is extremely important when trying to add new capabilities to a program, attackers generally don't need source code to find a vulnerability.

    First, it's important to distinguish between ``destructive'' acts and ``constructive'' acts. In the real world, it is much easier to destroy a car than to build one. In the software world, it is much easier to find and exploit a vulnerability than to add new significant new functionality to that software. Attackers have many advantages against defenders because of this difference. Software developers must try to have no security-relevant mistakes anywhere in their code, while attackers only need to find one. Developers are primarily paid to get their programs to work... attackers don't need to make the program work, they only need to find a single weakness. And as I'll describe in a moment, it takes less information to attack a program than to modify one.

    Generally attackers (against both open and closed programs) start by knowing about the general kinds of security problems programs have. There's no point in hiding this information; it's already out, and in any case, defenders need that kind of information to defend themselves. Attackers then use techniques to try to find those problems; I'll group the techniques into ``dynamic'' techniques (where you run the program) and ``static'' techniques (where you examine the program's code - be it source code or machine code).

    In ``dynamic'' approaches, an attacker runs the program, sending it data (often problematic data), and sees if the programs' response indicates a common vulnerability. Open and closed programs have no difference here, since the attacker isn't looking at code. Attackers may also look at the code, the ``static'' approach. For open source software, they'll probably look at the source code and search it for patterns. For closed source software, they might search the machine code (usually presented in assembly language format to simplify the task) for essentially the same patterns. They might also use tools called ``decompilers'' that turn the machine code back into source code and then search the source code for the vulnerable patterns (the same way they would search for vulnerabilities in open source software). See Flake [2001] for one discussion of how closed code can still be examined for security vulnerabilities (e.g., using disassemblers). This point is important: even if an attacker wanted to use source code to find a vulnerability, a closed source program has no advantage, because the attacker can use a disassembler to re-create the source code of the product.

    Non-developers might ask ``if decompilers can create source code from machine code, then why do developers say they need source code instead of just machine code?'' The problem is that although developers don't need source code to find security problems, developers do need source code to make substantial improvements to the program. Although decompilers can turn machine code back into a ``source code'' of sorts, the resulting source code is extremely hard to modify. Typically most understandable names are lost, so instead of variables like ``grand_total'' you get ``x123123'', instead of methods like ``display_warning'' you get ``f123124'', and the code itself may have spatterings of assembly in it. Also, _ALL_ comments and design information are lost. This isn't a serious problem for finding security problems, because generally you're searching for patterns indicating vulnerabilities, not for internal variable or method names. Thus, decompilers can be useful for finding ways to attack programs, but aren't helpful for updating programs.

    Thus, developers will say ``source code is vital'' (when they intend to add functionality), but the fact that the source code for closed source programs is hidden doesn't protect the program very much.

    --
    - David A. Wheeler (see my Secure Programming HOWTO)
    1. Re:Open source and security - some references by gnovos · · Score: 5, Funny

      This is a particularly absurd claim for application programmer interfaces (APIs) - by definition, APIs are disclosed to other developers, so the only reason to "hide" them is to prevent competition.

      Well, they may have a point though. Thier "hidden" APIs can be a big security risk, such as:

      BecomeRootUserWithoutNeedingPassword()
      Secretly TakeOverMachineinInvisibleMode()
      DecryptAllFilesA ndSendPlaintextViaWirelessCard()

      and, of course the one Outlook and Word uses:

      MakeProgramsRun90PercentFasterButTurnOffAllSecur it yAndGenerateVirusesWithGeneticAlgorithm()

      --
      "Your superior intellect is no match for our puny weapons!"
  27. Re:Ridiculous argument! by Rick+the+Red · · Score: 3, Funny
    Yes, but they've signed Non Disclosure Agreements, so it's OK.

    --
    If all this should have a reason, we would be the last to know.
  28. An interesting point? by binaryDigit · · Score: 3, Interesting

    Though I know the knee-jerk reaction is to scoff, M$'s statement does bring up an interesting issue. Given how porous M$ security is, just how much worse would/could it be if the source code were available? To be honest, and flame away if you must, I think that M$ does have an interesting practical point (not that I agree with how their applying it, but that doesn't make their point any less valid).

    So the obvious question arises, is Linux/BSD (and any other software that has source available) more exposed to "serious" attacks. By "serious" I mean being launched by somebody who knew enough to be able to look at the source and find security flaws, vs a script kiddie who takes a virus toolkit and modifies the virus name and subject line. Theoretcially, it should be more vunerable than a picece of closed source software that was written with a similar level of "quality".

    Again, I AM NOT DEFENDING OR SUPPORTING M$'S POSITION, only bringing up what I think is an interesting question.

    1. Re:An interesting point? by rlp · · Score: 2

      Here's what Bruce Schneier has to say about the subject. On the one hand, Linux code is open and available to the bad guys. On the other, it gets a great deal of peer review (often while still in alpha / beta). Schneier's thesis is that in general expert peer review trumps "security by obscurity". Empirical evidence tends to bear this out.

      --
      [Insert pithy quote here]
    2. Re:An interesting point? by binaryDigit · · Score: 2

      A nice feature of open source is that projects have a much broader peer review for security flaws/bugs

      this brings up another interesting thought. Suppose I was the man himself (Bill) and I've decided "enough of this buggy security swiss cheese we call software, lets start doing things right". So what I do is to say, "ya know, we've got about a gazillion programmers here in Redmond, why don't we start better utilizing a few". So what I do is to start company wide peer review of my closed source. Now obviously the breadth of eyes, even in a company like M$, is significantly less than the general programming population, but this would seem like a step in the right direction. Heck, if I really wanted to "do it right", lets say I drag in developers from my "partners" (like say Apple) to bring more eyes.

      So now that I've done this, the question is have I been successful at eliminating (or at least mitigating) the advantage that OS projects have in this regard, and still keep the other "positive" aspects of CS?

    3. Re:An interesting point? by mpe · · Score: 2

      So the obvious question arises, is Linux/BSD (and any other software that has source available) more exposed to "serious" attacks. By "serious" I mean being launched by somebody who knew enough to be able to look at the source and find security flaws, vs a script kiddie who takes a virus toolkit and modifies the virus name and subject line. Theoretcially, it should be more vunerable than a picece of closed source software that was written with a similar level of "quality".

      It is perfectly possible for someone to attack the binary. They don't need the source to do that. Also every single Windows machine is likely to be running the exact same binary.

    4. Re:An interesting point? by mpe · · Score: 2

      I would suspect that if M$ source code was opened up there would be a deluge of exploits within the first few months and then slowly taper off as the "easy holes" are plugged. This is true of nearly all open source software after its initial release.

      It could well take longer. Since there is a difference between code which was designed from the start to be open source and quite likely very well patched code which no-one ever expected to see the light of day.

    5. Re:An interesting point? by binaryDigit · · Score: 2

      It is perfectly possible for someone to attack the binary

      Yes I agree, never said it wasen't possible, the issue is whether or not it is easier since the source is available to you. Attacking a binary is a bit more arcane once you get beyond obvious things like trying to overflow buffers at interface points.

      Also every single Windows machine is likely to be running the exact same binary

      Well, sort of. Not anymore so than any particular distribution of Linux right? Don't forget that right now in the Windows camp you have people running 98,ME,NT4,2K,XP and maybe some others I've forgotten. Then you take into account various release levels _and_ patch levels and all of a sudden you have a much larger variety of binary versions you may have to deal with (of course it makes a big difference exactly what you're attacking, since any of the IE related binaries change every two days it seems like).

  29. Forgot to Mention by guttentag · · Score: 5, Funny
    ...sharing information with competitors could damage national security and even threaten the U.S. war effort in Afghanistan...
    They forgot to mention it would:
    1. reverse gravity
    2. send the tightly-controlled, stable market into a state of chaos
    3. put thousands of people out of work (how could MS pay its employees if they gave their products away?)
    4. bring back Elvis (in the form of MP3s distributed by the masses who were previously restricted by MS DRM)
    5. cause the judge's personal computer to automatically download pornography every day
    Didn't we see this in Ghostbusters?
    "He wants to shut down the protection grid, Peter."
    "You shut that thing down and we are not going to be held responsible."
    1. Re:Forgot to Mention by bmajik · · Score: 2

      Yeah, and what happened in ghostbusters, when pencil dick shut down the grid anyway ?

      When you've looked through the code in question, when you've looked at how its being deployed, and when you look at what assets are at risk, and when you consider the likelihood of a patch fixing the problem without breaking the system, and even then, getting applied in all the places necessary..

      Then feel free to take on the ghostbusters.

      Until then, you're a pencil dick, and i hope to god nobody lets you near the grid.

      --
      My opinions are my own, and do not necessarily represent those of my employer.
  30. They may argue themselves back to a breakup? by ClarkEvans · · Score: 3, Interesting

    They may just confirm Judge Jackson's assertion that any sort of compromise short of a breakup will be insufficient. Here's hoping that Kollar-Kotelly's nose is as good as Jackson's.

  31. Microsoft source code is already available... by RyanFenton · · Score: 5, Informative


    Austria already has it.

    Any U.S. University can apply for it now if they don't already have it.

    Many of Microsoft's larger customers have it

    I don't see why it would be difficult for any terrorist organization to get it. How can they legitimately argue that it may possible be keep it secret at this point? If it's a national security risk to make the code available, the damage can no longer be avoided.

    Ryan Fenton

    1. Re:Microsoft source code is already available... by dattaway · · Score: 2

      I am curious what is included with that source code. Do they include every application and driver with their distribution? Everything or just the core components?

      Do they also promptly release code with their service packs and hotfixes for reliability testing? Can the customer compile their operating system like gentoo linux? Is this option even available or what other restrictive and expensive measures does the customer have to pay for?

  32. Best Quote from Story by danmil · · Score: 5, Insightful
    In case you thought that Microsoft was serious about trying to make their products more secure, check this baby out:

    'When pressed for further details, Allchin said he did not want to offer specifics because Microsoft is trying to work on its reputation regarding security. "The fact that I even mentioned the Message Queuing thing bothers me," he said.'

    I love that! 'It pains me to admit that our software is dangerously broken, because we're trying really, really hard to convince people that the reputation we have for foisting dangerously broken software on them is totally unfounded.'

    I guess if there were trying to work on their actual security, rather than just the reputation, they might act a bit differently (like, by publishing their API's and then working with the security community to get them safe).

    -Dan

    --

    I have written a truly remarkable operating system which this sig is too small to contain.

  33. Microsoft's already endangering the U.S. by Florian+Weimer · · Score: 2

    They have exported the Windows source code to countries such as Germany, Czechia, Slovakia, Isreal, Hungary, Japan, and even Singapore. Check the list yourself.

    Maybe it's time for another trial.

  34. Ok, let's look at a trend here... by NoMoreNicksLeft · · Score: 2

    Micro$oft has always made excuses of one sort or another, about a great many things. But, so far, few have been this ludicrous.

    The first, was "it can only hurt the US economy if the debut of Windows 98 (was 98, wasn't it?) is delayed..."

    And now, "releasing source code/API's would threaten nationally security".

    Does anyone want to start taking bets what the next grand bullshit excuse will be? My wager is on "God commands thee to cleanse thy hard drive of this vile Linux". I just can't think of anything else that is on the level of the first two.

  35. all security is through obscurity by Cardhore · · Score: 2

    All security is through obscurity--even encryption. Think about that.

    "Touch" makes empty files or changes their date. You're telling me that's easy to remember, while knowing that "rm", short for remove, removes file(s) is harder? "Chmod" changes a mode is harder to remember than "finger" giving you a user's name?

  36. In other news by MongooseCN · · Score: 5, Funny

    After supporting MS's statements that all source should be closed and hidden in order to maintain national security, the US government has agreed to hide all tall buildings. All tall buildings will now be covered with large black clothes. In order to maintain national security, anyone caught talking about these buildings will be arresting. Since terrorists will be unable to clearly see and hear about these buildings, they will no longer be able to attack them. Thank you and good night.

  37. Second Best Quote by Lumpish+Scholar · · Score: 5, Funny
    "Sun's strategy of promoting '100 percent pure' Java applications discourages interoperability."
    That's right; if you write a program that runs on all computers out there, you'll have problems with all those computers being able to communicate with each other.
    --
    Stupid job ads, weird spam, occasional insight at
    1. Re:Second Best Quote by pnatural · · Score: 2

      Oh, please.

      While I don't particularly care for MS and their products, I can see the guys point. Java, by its very nature, does not interoperate with anything but Java at the process level. That's what he's talking about and he's absolutely correct from that perspective.

      And of course, anything that goes over a standard network protocol can interoperate, but if that's the case, then you sure don't need Java as any language/environment/library that implements the protocol in question would work.

    2. Re:Second Best Quote by catfood · · Score: 2

      No big deal.

      Sun's Java implementation supports Microsoft's DCOM, uh, protocol.

      You can have all that Java-to-Java interoperability using Java/RMI without giving up Java-to-DCOM.

      But the main thing is that Allchin is, yet again, defining "interoperable" as "will work with Microsoft's preferred paradigm-du-jour." Which is nearly the opposite of the word's normal meaning.

    3. Re:Second Best Quote by Delirium+Tremens · · Score: 2

      You might want to have a second look at the IIOP support in Java, or even at JNI, which allows you to call portable C code compiled on many different platforms. Or if you are into ActiveX, you can also use an OLE bridge.
      So, who says Java is not interoperable? Hmm?

    4. Re:Second Best Quote by Delirium+Tremens · · Score: 2

      Sun's Java over DCOM? You must be playing with Tiger or something because I never saw anything like that. There used to be a lot of vaporware talk about RMI-over-DCOM, but I am not aware of anybody who actually managed to implement that. Yes, it certainly can be done. No, nobody wants to do it.

    5. Re:Second Best Quote by alext · · Score: 2

      There's no point in RMI->DCOM->DCOM->RMI, you might as well do RMI->RMI. However, there are plenty of uses for Java->COM and Java->Dotnet.

  38. Re:EULA? by PepsiProgrammer · · Score: 2

    Actually, its probably already in there, just impossible to find along with everything else.

    --
    "The United States has no right, no desire, and no intention to impose our form of government on anyone else." - Bush 05
  39. Unfair to Pintos by lrc · · Score: 2, Informative

    Calling MS the Pinto of the 21st century is grossly unfair to Pintos. First, Pintos are a lot better than their reputation. The original 1600 pushrod motor is the same solid reliable block used in Cortinas (and most other English Fords) as well as having been raced for years in Formula Ford. The bottom end of that motor is used in Lotuses, as well as the Cosworth race engines (Formula Atlantic).

    The 2 liter overhead cam motor in the Pinto is surprisingly good. When I raced a friends Capri with that motor, he said that he usually shifts between 7,000 and 8,000 RPM because it doesn't make any more power beyond that, but the motor will spin over 9,000 RPM without problems.

    I've also seen Pintos win the SCCA racing class Improved Touring B, against cars like BMW 2002s.

  40. Just have to say it... by Flower · · Score: 5, Funny
    They need to make a movie with Samuel L. Jackson as a Microsoft programmer just so I can hear the line.
    Send me that service pack. It's the one named, 'Dumbass Motherfucker.'

    They can name it something like 'Patch Lola Patch.'
    --
    I don't want knowledge. I want certainty. - Law, David Bowie
    1. Re:Just have to say it... by blakestah · · Score: 4, Funny

      \

      Jules: Send me that service pack. It's the one named, 'Dumbass Motherfucker.'

      Vincent: You know what the funniest thing about Microsoft is?

      Jules: What ?

      Vincent: Its the little differences. Its got a lotta the same shit as other operating systems, but with those guys it is a little different.

      Jules: How so ?

      Vincent: For example. Another company has a bug. They fix it in like two days, and then they annouce the bug and the fix.

      Jules: Ok. And at Microsoft ?

      Vincent: At Microsoft, when someone points out a security hole, the first thing they do is threaten a lawsuit against the guy who found the hole if he says anything.

      Jules: You mean they threaten the guy who is helping them ?

      Vincent: Yup - exactly what I mean. As long as there is not a big media splash, they never gotta fix nuthin.

      Jules: So what happens if the guy opens his mouth.

      Vincent: Generally he don't. But, some 15 year old kid in Asia finds the same bug, and then releases a worm, and it chews apart all the Microsoft systems worldwide in like two days.

      Jules: No shit !

      Vincent: Yeah, and then Microsoft tells everyone about the bug, and provides a patch, but no one fixes it.

      Jules: No one !?

      Vincent: Well, smart people do, but most people just miss the message. They gotta go to Microsoft, get the patch, and half the time the fix will break something else on their system.

      Jules: So if this shit is so bad, why are so many people using it ?

      Vincent: It used to be everything on personal computers were that bad. Then, Microsoft controlled the market. Everyone else started making good shit, but it didn't matter. Microsoft made people buy their new shit so they could continue to read their own old shit. Can you believe it ?

      Jules: Man, that is some weird-ass shit. Like some idiot can't take a step back and see himself being played like that.

      Vincent: Yeah, it's kinda sad. But it makes a great market for guys to run around spending all their time patching holes after they are exploited. If Microsoft made good shit, we wouldn't have jobs.

      Jules: Good point.

  41. Class Action ? by ntsucks · · Score: 2, Insightful

    With all the money in M$ bank account, where are all the laywers? Shouldn't admitting gross negligence bring a class action lawsuit?

    --
    Those who can do. Those who can't sue.
  42. Logical Contrapositive by whovian · · Score: 5, Funny

    Microsoft's view:
    If the software has security flaws, then the code and APIs cannot be made public.

    Open source view:
    If the code and APIs are made public, then the software does not have security flaws.

    So, Microsoft, we are finally in agreement, yes?

    --
    To-do List: Receive telemarketing call during a tornado warning. Check.
  43. M$ Legal Department Watches Monty Pyhton! by HiredMan · · Score: 2

    It's clear this strategy is the coding equivalent of "The Killing Joke":

    "Here at M$ coders are only allowed to work on code a few lines at a time. The code is so fundementally flawed that if any single programmer sees an entire code block he immediately goes insane... well, the lucky ones do anyway..."

    M$ - code so bad protecting people from it is job #1!

    =tkk

  44. Who wants the source anyway? by SpinyNorman · · Score: 2

    How exactly does this undo the damage that Microsoft has done to so many companies with it's corrupt business practices?

    I'd prefer to see:

    1) Microsoft to be required to licence Windows under uniform fixed court agreed terms to all hardware vendors, with no conditions allowed on what else they sell (e.g. bare PCs, Linux), or what else they do or don't load onto their PCs (office software, browsers, ISP links)

    2) Certain file formats (office documents) to be deemed part of national commerce infrastructure, and put under control of some industry body rather than microsoft

  45. One standard to rule them all by WEFUNK · · Score: 4, Funny

    "Microsoft has invested substantial time and resources in providing great interoperability between .Net and older technologies," Allchin said. "Sun's strategy of promoting '100 percent pure' Java applications discourages interoperability."

    So, according to Microsoft, it is better to have one company provide (ie control) the degree of interoperability between systems than to have another company promote a single standard for the whole industry to use and share.

    I can't imagine that line of thinking going over very well with military officials used to building redundancy into everything.

    You might also paraphase the above statements as follows:

    "Microsoft has choosen to ignore freely available and already established standards and instead has wasted substantial time and resources needlessly reinventing the wheel by developing our own internal standards (that we won't share and that we admit are not really very good) so that we can control the degree of interoperability between our proprietary new product, and our former (and soon to be former) competitor's technologies"

    "Sun's strategy of creating and sharing a standard that encourages 100% interoperability between all systems discourages interoperability (but only in respect to our systems, because ours are made to be incompatible with the accepted standard that everyone else uses)."

    Oh boy, can I please buy your systems for my Army?

    --
    My next sig will be ready soon, but friends can beat the rush!
    1. Re:One standard to rule them all by sl3xd · · Score: 2

      The scary thing is doing things like this does sound like a government contract... It's probably been done.

      --
      -- Sometimes you have to turn the lights off in order to see.
  46. "It made a difference for that one starfish." by janda · · Score: 3, Insightful

    Get a paper copy of this testimony. Make lots of photocopies. Highlight the "interesting" parts (such bad security that releasing it would be a national security risk, etc). Send to everybody in your local government you can find, demanding that they stop using MS products until their security problems are fixed. As alternatives, there is at least OSX, all the Linux distributions, and probably other things (the resurrection of BeOS?).

    Given that MS is admitting in court that they are selling defective products, demand that your local government sue MS for fraud. Politicians don't keep up to date on every legal battle going on everywhere, but if you send them the relevant portions they at least can't claim they didn't know.

    While you're at it, forward this onto the local newspaper and tv stations. "poor security" is a big boogyman these days.

    Another thing; Send this onto the people at your company who make buying decisions, if MS is going to admit their products have the security of swiss cheese, does your company really want to expose itself to that kind of danger?

    --
    Karma: Food Fight (Mostly affected by Date Plate).
    1. Re:"It made a difference for that one starfish." by bmajik · · Score: 2

      I don't see what you're upset about.

      Lets take two statements:

      Having source code can be a significant aid in finding implementation bugs that make software incorrect.

      Windows and other Microsoft software is running on machines in security sensitive capacities, whos compromise would be bad.

      If you beleive the first two statements, then a logical consequence follows:
      Theres no reason to hand the code to the people trying to own us, otherwise we're just making it easier to get people killed.

      Now lets move on with the rest of your post:

      Please name an operating system that is secure.

      Thanks.

      The judge asks about security problems. Microsoft says "yes, we've got them. some are so bad that we shouldn't let anyone know about them"

      He's telling the truth. What are you upset about ?

      You on the other hand, very much imply that the effective security of linux, osx or beos (!!! ?) are better.

      When you have factual evidence of that, get back to me.

      Liking linux doesn't make it better. Hating microsoft doesn't make windows worse.

      Not liking a statements conclusion doesn't make it invalid.

      --
      My opinions are my own, and do not necessarily represent those of my employer.
    2. Re:"It made a difference for that one starfish." by Archie+Steel · · Score: 2

      Please name an operating system that is secure.

      If by "secure" you mean "100% secure", then you're right, there isn't. In any case, an OS is only as secure as the Administrator that sets it up.

      However, if by "secure" you mean "a lot more secure than any Microsoft OS", then I suggest you look into the NSA's Security-Enhanced Linux. And, yes, the source code is available. The fact is, MS products were never designed with security in mind, and therefore are intrinsically less secure than many other OSes, including a well-configured Linux or BeOS installation. It's not a matter of personal opinion, now: even Allchin candidly agrees!

      --

      Reminder: find a new sig
    3. Re:"It made a difference for that one starfish." by bmajik · · Score: 2

      Win 9x was never designed with security in mind.

      NT had security in mind from the onset. NT had a fleshed out security design before Linux was a gleam in Linus's eyes.

      NT infact has a much more granular, flexible, and powerful security model than unix does.

      So your claim that no microsoft OS was designed with security in mind doesn't have much to stand on.

      That many applications and system services are _implemented_ poorly has no bearing on the "security design". Eg, yeah, if IIS has a service which runs with the same security context as some other service (say SYSTEM or LocalService) than an exploit in IIS will elevate you to that credential. However unlike linux, (and unix in general), it is possible to make absurdly granular ACLs and compartmentalize IIS from being able to wreak havoc on the system at large.. eg in the near future IIS will be running as "NetworkService" which is a physically distinct account from something like Admin or SYSTEM.

      This is not possible on unix. YOu're either God or Shit, which no granularity inbetween. ((i realize patches exist that try to introduce various levels of granularity. They are not standard in any mainline unix distro)

      Linux is not at all a champion of security. Not by any stretch. The NSA's work doesn't change that. Infact, most of the attacks against linux are utterly orthoganal to what the NSA patches do. They bring linux roughly within compliance of the pre-Common criteria scheme for either C2 or B1 (i haven't really looked at which).

      Guess what. IRIX and Sun have had B1 IRIX and B1 Solaris for quite some time. The same irix that had multiple root vulns in everyday userland apps.

      The NSAs work (and most other govt-security work in commercial OSes) is about adding accountability and recovery in the face of a break in, not preventing a breakin.

      It _is_ a matter of personal opinion : Yours.

      Allchin said that there are bad security bugs in windows. This isn't a surprise to anyone. It is also not unique to windows. If you think otherwise you are hopelessly delusional.

      --
      My opinions are my own, and do not necessarily represent those of my employer.
  47. Security by surfcow · · Score: 4, Funny

    Your Honor, we at Microsoft believe that if we ever revealed the source code for MS Windows, more children would immediately start taking drugs. Husbands would start to beat their wives. Small animals would become uncontrollable, staining many expensive carpets. Certain food-groups would become more perishable. 2nd law of thermodynamics would be repealled. Finally, a giant hole would open up in space time, causing the end of the universe.

    Your honor, it is a matter or national security, no international security, no galactic security, that we be allowed to continue our profitable monopoly.

    Think she'll buy it?

    =brian

  48. Re:Don't pick on me! My software sucks! by fermi's+ghost · · Score: 2, Informative
  49. Proof that Microsoft needs to go... by sterno · · Score: 3, Insightful

    The question that has to be asked here is this: do we really want to have our country so heavily dependent on an OS that is so apparently at risk of vunerabilities? Let's analyze the threat for a moment.

    Let's say that this message queueing vulnerability that was spoken of in the article is a pretty substantial hole that could be a true threat to national security. What makes anybody think that because Microsoft refuses to talk about it hasn't already slipped out to all the wrong people. If some high level executive at Microsoft knows about it, you can guarantee that probably hundreds if not thousands of people within the orgnization know about the problem already. The more people that know about it, the better the odds that somebody nefarious will get a hold of that information.

    If I were the intelligence service of some devious foreign power you can bet I'd have a few operatives working in Microsoft. I mean if you want to fight a war with the US, what would be better than an opening shot that can harm >90% of the computers in the country. So you have a few operatives finding what holes they can and slowly relay them back. Then you just sit and wait for the day when you need a real threat in your arsenal.

    Imagine how nice it would be if you are some nefarious foreign power in tense negotiations with the US and you can walk in, and them a floppy disk and tell them to give in or else. I mean even if they find out what the vulnerability is, can they deploy a response to it fast enough that it matters? Nothing like the threat of having the electronic economy slagged to make you amicable to a bad deal.

    I think that if Microsoft's the threat they seem to imply, the judge should order them to turn over the source code to the FBI to begin dissecting these problems. Do we really want to trust a private corporation with our national security? I don't think so...

    --
    This sig has been temporarily disconnected or is no longer in service
  50. Re:Don't pick on me! My software sucks! by markmoss · · Score: 2

    Mid-air GPF anyone?

    Already happened (except it was a badly handled arithmetic overflow). European Space Agency satellite launch, Ariadne II, IIRC. The software was multiplying speed x time and adding it up to get distance traveled, or something like this, and because the II went faster than the I, eventually it overflowed. And the control system froze.

    But I don't think this was Windows or any other commercial OS...

  51. Guess what... by Sarcasmooo! · · Score: 2

    I've said this before in response to MS-FUD: When the government/economy/national security of an entire country hinges on the well-being of one company, that company might be just a little too big for everyone's own good.

  52. Some thoughts by bryan1945 · · Score: 2

    Ok, I did not read the article, so if I'm wrong on some points, you know why.

    I'm an Army contractor, and all of their critical systems are all Solaris based. Thus proving that the Air Force and Navy are just a little bit dumb. (sorry, had to jab that) Now, if any defense company said to the military that its product was so flawed that it couldn't give the gov the source code, it would be rejected and the company sued. Basically, if the gov hadn't whored themselves out to MS there would be much smackin' goin' on. This stance may just be enough to get sued just by these statements.

    --
    Vote monkeys into Congress. They are cheaper and more trustworthy.
  53. I read the article... Where's the quote? by Sivar · · Score: 2

    I read the article. Several times. Perhaps I am just not very observant today, but what was the exact quote in which a Microsoft exec stated more or less that its code is so flawed that it could result in nat'l security compromises?

    I read the following quotes in the article:

    "It is no exaggeration to say that the national security is also implicated by the efforts of hackers to break into computing networks,"

    "Computers, including many running Windows operating systems, are used throughout the United States Department of Defense and by the armed forces of the United States in Afghanistan and elsewhere."

    "Microsoft has invested substantial time and resources in providing great interoperability between .Net and older technologies"

    "Sun's strategy of promoting '100 percent pure' Java applications discourages interoperability."
    (Ha! Whatever)

    "The fact that I even mentioned the Message Queuing thing bothers me"

    Perhaps Techweb is offering a creative interpretation for the purpose of getting hits?
    Anyway, if anyone can find a source for such a quote, please let me and everyone else know as I could add it to my "Why Microsoft sucks" archive of data. :)

    --
    Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
    1. Re:I read the article... Where's the quote? by Teancom · · Score: 2

      It's a two-parter. Take this sentence (that you quoted):

      "Computers, including many running Windows operating systems, are used throughout the United States Department of Defense and by the armed forces of the United States in Afghanistan and elsewhere."

      and add in this one:

      "The protocol, which is part of Message Queuing, contains a coding mistake that would threaten the security of enterprise systems using it if it were disclosed, Allchin said."

      Combined together, you get "Computers used by the US DoD and Armed Forces are running a protocol that, if exposed, would have it's security 'threatened' (i.e., compromised)."

      There, not out of context, directly from the article. Have a nice day :-)

    2. Re:I read the article... Where's the quote? by mpe · · Score: 2

      "Computers, including many running Windows operating systems, are used throughout the United States Department of Defense and by the armed forces of the United States in Afghanistan and elsewhere."

      This tells the "bad guys" where to concentrate their efforts to introduce an exploit.

      "The protocol, which is part of Message Queuing, contains a coding mistake that would threaten the security of enterprise systems using it if it were disclosed, Allchin said."

      Assuming the black hats don't know about it anyway. Even if they don't they now have a good clue as to where to look. Unless "Message Queuing" is misinformation.

  54. Seems to me by angst_ridden_hipster · · Score: 4, Insightful

    Seems to me that either Allchin suffered some stroke or brain damage while in court, or this is all a big red herring.

    You just don't get to Allchin's level and "accidentally" let slip something like a fundamental vulnerability in a protocol. M$ officials may make mistakes, but not like this. Not in a public forum. Not in front of a judge. Not where every news medium in the world will be covering the story.

    My feeling is that this is all a distraction from something else. Every black hat on the planet is now probably checking out the Messaging protocol. My guess is that there's no smoking gun there. But maybe another protocol has problems.

    Furthermore, it just doesn't make sense. An API exposes only what you want it to. It doesn't show you the vulnerabilities that exist "under the covers" unless they're titanically, apocalyptically stupid.

    I'd like to know what it was that he's distracting us from ...

    --
    Eloi, Eloi, lema sabachtani?
    www.fogbound.net
    1. Re:Seems to me by atheos · · Score: 3, Insightful

      Or, ever more scarry...
      Maybe he made this statement knowing every black hat is going to check the Messaging protocol.
      Two days later, a major exploit is released, and Allchin says to the judge "see what I mean, THIS is exactly why we must keep it all closed"
      It could be a bullshit ploy.

  55. What about... by coats · · Score: 2, Interesting
    Then why isn't Microsoft being charged with felony computer crime for the way all of its OS upgrades surreptitiously inistall Outlook preferences over the existing mail agent preferences, in ways that are very hard to undo.

    In this pleading, Microsoft themselves admit that their stuff is widely installed on Federal Interest Computers.

    Microsoft's use of so-called operating system patches to disable user mail applications and replace them with the Outlook mail server application is unauthorized hacking of Federal Interest Computers, a Federal felony under US Code Title 18 Section 1030 (the COMPUTER FRAUD AND ABUSE STATUTE: see http://www.cpsr.org/cpsr/privacy/crime/fraud.act.t xt).

    Microsoft's pervasive practice of using their upgrade/patch excuse for hacking Federal computers and replacing relatively secure software like Eudora with nightmares like Outlook (which is itself responsible for something like 80% of the viruses and worms on the net!)is a violation by my reading of the Act (but IANAL). I think that Paragraph (b)(1)(B) ought to be applied!

    --
    "My opinions are my own, and I've got *lots* of them!"
  56. Re:EULA? by statusbar · · Score: 2

    Doesn't the typical microsoft eula specify that the software is not to be used in life critical systems anyways?

    --jeff++

    --
    ipv6 is my vpn
  57. NSAKey by yancey · · Score: 2, Funny


    If we had the source code, we might find out the true function of the NSAKey function!

    --
    Ouch! The truth hurts!
  58. This is annoying... by Danse · · Score: 2

    I mentioned this very scenario in my comment to the DOJ regarding the proposed settlement. I proposed that the oversight committee (as long as no members were appointed by Microsoft) or the court be tasked with determining whether revealing APIs or protocols would constitute a legitimate security threat. It's probably not the best answer, but it beats the hell out of letting Microsoft decide.

    --
    It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
  59. I could not believe I read this. by theolein · · Score: 2

    The only reason I can see someone from Microsoft saying this in a court of law is that they must be really, really desperate. Making wild claims about American national security and the war in Afghanistan is something that no one in the industry or the court is going to believe, and if they do many, many people are going to start to ask themselves if it isn't time that some form of government control and a change in Microsoft management is needed.

    I cannot see this benefitting Microsoft in any way. There will of course be the usual pro microsoft sites such as ZDNet that will report this verbatim (with a straight face) but, for a company that is trying to garner support for "Trustworthy computing" and it's .Net initiative in the industry, this is desasterous. Most large companies that are dependant on Microsoft software will ask themselves if it is wise to take Microsoft seriously considering the statements made by Microsoft executives in court. Technical and business reviews are going to have a field day with this one ("If it is so insecure why are we using it?", "Can a company take them seriously when they come around trying to do business claiming Microsoft superiority?"). This will make a lot of press sites, and I seriously wonder if this won't be the thing that finally tips the balance against Microsoft in the eyes of the general population or at least the general business population. Although the general press is extremely ignorant about IT things (the BBC is a brilliant example of this) even they wil be able to put two and two together that something is very wrong with this company.

    I don't know what kind of an effect this will have on foreign governments, but this will not go down well with EU even though they are just as IT-ignorant as American politicians.

    I know that if I had my own company and read through some of the statements that Microsoft have made in court I wouldn't be laughing like I am now.

  60. Whose Your God Daddy? by djmoore · · Score: 4, Interesting

    Microsoft is resorting to desperation tactics... they know they've lost.

    Actually, this is entirely consistent with MS's strategy all along: it has been arguing that it and its products are so profoundly important to the American economy and security that any remedy which interferes with its ability to act as it pleases should be struck down by the court. Otherwise, everyone will suffer at least as much as MS will.

    It's the exact equivalent of a mob boss saying that he shouldn't be imprisoned for running a protection racket, because then he wouldn't be able to protect his customers. Moreover, he wouldn't be able to provide for his innocent wife and children (even though it's been shown he abuses them as well).

    Microsoft isn't at all desperate; they're just so arrogant, and so blind to basic security principles, that they don't really see a problem with what they're saying.

    --
    In the wrong hands, sanity is a dangerous weapon.
  61. Windows is the cyberspace Corvair... by pergamon · · Score: 3, Funny

    Unsafe in any configuration

  62. Why al-Qaeda is using MSFT source code by WillSeattle · · Score: 2, Funny

    There was a reason why there were pictures of Seattle on those captured PCs that al-Qaeda were using.

    It wasn't that they were trying to make bioweapons to use on us.

    No, they got H1B visas and are coding in Redmond as we speak!

    -

    --
    --- Will in Seattle - What are you doing to fight the War?
  63. Quoting out of context by theolein · · Score: 2

    If you can do that, why can't /. ?

  64. Distraction by theolein · · Score: 2

    You may have a point. If one asks oneself what they really have to lose by disclosing all their APIs the answer might very well be that someone might find a disproportionate amount of properties, return values and methods that they recognise from elsewhere.

    1. Re:Distraction by danro · · Score: 2

      The day it is made public that windows contains "pirated" code (which a system of that size, with closed source and that kind of growth pattern almost certainly do, to some extent) is the day I am breaking out the Champange.

      I wish they could just behave sensible, though...

      --

      "First lesson," Jon said. "Stick them with the pointy end."
  65. Staggering by johnos · · Score: 4, Interesting

    Let me get this straight. The product that Microsoft's monopoly rests upon, the monopoly that they illegally maintained and expanded, is so flawed that it threatens US national security. Did someone from Microsoft REALLY say this? If so, it is clear they have gone mad in Redmond. What do they expect the millions of companies and government agencies to do? Wait until Longhorn, or whatever is ready? And hope all the holes are fixed by then?

    "Uhh, sorry Mr. President, the NSA can no longer monitor international communications. Our systems are just too vunerable to hacking to be used. Jim Allchin assured us that a comprehensive fix would be available within 18 months."

    "In other news, the US Navy has ordered all AGEIS cruisers into port indefinatley. The AGEIS computer systems were deemed too risky for combat use. The Pentagon would not comment on reports the entire US fleet would require software overhauls before any offensive combat operations could be contemplated."

    "World stock markets are today in freefall as most major international corporations raced to secure information systems based on Microsoft's Windows operating system. Some experts estimate that the expense of fixing or replacing mission critical software to provide an adequate level of security would dampen the World economy for a decade."

    This goes so far beyond a computer industry issue. Its a staggering admission of guilt. What CIO would be caught dead installing an MS system unless they have absolutly no alternative?

    There is also the legal issue. If someone has sustained an economic loss due to "flawed code", that they are using because MS illegally supressed competitive alternatives, then they have a really good case for compensation. And the hardest part, proving that MS illegally manipulated the market, is already done. And they have some tens of billions just sitting around, waiting for the right lawyer to just take away.

    1. Re:Staggering by Lysander+Luddite · · Score: 2

      You know what's interestig is all th emilitary procurements in Windows systems the past few years. If exposing Windows to scrutiny is a threat to National Security (and I don't believe it for a second) then that would mean the military is in a perilous situation that would be potentially embarassing for them and the government. Better to keep it quiet by hiding it all under a "threat to national security". BUt then secrets aren't exactly unknown to our current administration.

  66. You're looking at it from the wrong side by eddy · · Score: 3, Informative

    Umm.. I don't think the issue is so much with poor documentation where documentation exists, I think the issue is more with non-existing documentation.

    If you are looking at the whole system from the point of documentation, of course everything looks great? That's like looking at the world though a great big filter.

    Instead you will have to go the other way; check all DLL/EXEs for exports, and then see if those exports are documented. Some exports aren't even done by name, but only by ordinal, making them even harder to use.

    I'm not a win32 guy either, so I can't give any concrete examples off hand, but I'm pretty sure this is partly where the issues lie.

    You really cannot say the APIs are highly documented unless you have disassembled the code to see what it can really do, can you? Sure, there might be a hundred documented functions, but that is only impressive if there are only a hundred exports, and those exports are limited to the paramaters defined by the documentation.

    --
    Belief is the currency of delusion.
  67. Little known fact... by Futurepower(R) · · Score: 2, Funny


    Actually, there is no one called Allchin at Microsoft. Allchin is a descriptive term for All Chin, Jabba the Hutt.

    Even though he also works for George Lucas, All Chin has a long history of eating cute, squeaky animals for Microsoft, too. For example, in the December 12, 1994 edition of Computer Reseller News, page 269, column 1, fourth paragraph, he said that a software emulation patch for the Pentium floating point processor bug would not affect performance greatly. This was true, as long as customers didn't use it. If the program they were running used that part of the floating point processor, however, the processing would be far slower.

    Now he's telling us that war is a good reason for us to let Microsoft do what it wants to do anyway. To Microsoft, we are all cute, squeaky animals.

    1. Re:Little known fact... by Pig+Hogger · · Score: 2
      Now he's telling us that war is a good reason for us to let Microsoft do what it wants to do anyway. To Microsoft, we are all cute, squeaky animals.
      Why a bouncing paperclip, then?
  68. Pinto? Try Corvair. Unsafe at any MHz. by crovira · · Score: 2

    I love the quote "Microsoft code was so flawed it could not be safely disclosed." That's an honest appraisal.

    What the fuck are people doing with it then? That's like laying down in front of a bully and yelling "Kick Me?"

    I'd hate to think that it really was a matter of National Security. Luckily, its not. Nobody with something that needs a serious, secure computing platform uses Windows.

    Man, M$ are slash(dot :-)ing their own fucking throats.

    Now some people I know who were merely concerned before will install Linux on their servers for sure and try StarOffice on their desk top machines.

    What will happen to the people at bug tracker then? They'll be made redundant since almost all these "Net" bugs are M$ bugs.

    --
    MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
  69. Microsoft _can't_ fix it? by Ride-My-Rocket · · Score: 5, Insightful

    He later acknowledged that some Microsoft code was so flawed it could not be safely disclosed.

    Somehow, I think that if the US government forbade the use of any Microsoft applications within federal facilities, pending a code review by a neutral 3rd party to identify and fix potential security holes, you'd see Microsoft scramble to get their shyte in gear pretty damn quickly.

    As somebody already stated in this thread, Peru has the right idea: open source allows people to public review code for potential security flaws, which is how most bugs are caught anyway -- a fresh pair of eyes takes a peek. Ultimately, there's no way that Microsoft can compete with this code development paradigm -- since there's so much Open Source code "out there", it might spread people's attention out a bit too thinly in places, but over time one would hope that Linux apps will only more secure / stable.

  70. If you open Windows source by rossz · · Score: 2

    You only help the terrorists!

    Just think of the children!

    --
    -- Will program for bandwidth
  71. The way I see it, It's like choosing a woman. by uofa1993engrmath · · Score: 4, Funny

    One is sort of chunky and ugly, and she won't let you see her naked, and you pretty much know already that you wouldn't really enjoy it if she did. The other has a slim, beautiful body, and when she takes off her clothes and parades it around, all the men ooh and ahh over it. That's the analogy I like to use. Maybe it isn't 100% correct, but that's the impression I get when you've got MS saying "No, no, you don't want to see our source code!" and meanwhile, you've got these open source softwares that are taking it all off, and saying "hey, baby, look at THESE!" Microsoft is NOT sexy. Linux, apache, and all of those wonderful open source projects ARE. But this is just how I see it. I mean, if I was to go on a date with a woman, and she proudly told me that she has an MCSA certification, I'd probably politely nod, but secretly be planning on my escape (maybe run away after telling her I had to use the restroom). On the other hand, if she told me that she had her own php based website, and that her text editor of choice was vim, then I'd be all weak-kneed and googly-eyed, and I'd want her to have my children. But again, that's just me. I don't know how it is for other people. I mean, I may not really UNDERSTAND beautiful women, but I sure like to look at them. So, I don't think there's any action required, as in "let's get rid of Microsoft." I think that it's really just a matter of educating the masses that there's an alternative, and it looks good naked. Or as you might say, it's a lot safer because the code can be (and is) made public without compromising national security.

  72. Mod parent up (Re:Fear the future...) by MavEtJu · · Score: 2

    I never thought I would ever say this :-)

    But yeah, I've wasted enough time (and thus the company money) fighting these stupid outlook/IIS viri and we are not the only company in the world...

    --
    bash$ :(){ :|:&};:
  73. Only blamed if it's their fault by Anonymous+Brave+Guy · · Score: 2
    In the real world, it is very hard to get everyone to apply patches, and the software vendor gets blamed even when they've made the patches available months earlier; Code Red is a perfect example of this.

    MS only take the flak for this because there are so many serious bugs in their software.

    Any developer reading this knows that writing 100% bug-free code is hard, and often beyond economic viability. You get diminishing returns with your QA investment.

    OTOH, any competent software developer will write code containing only a very few serious bugs, and some more that are just irritating but not of the "data lost" or "system compromised" sort of level.

    Microsoft, the most powerful software development house in the world, is shipping disorganised crap because of good marketing, and now they are complaining that they should get cut some slack because what they're shipping is crap? Sorry, I have no sympathy. If we shipped stuff of that standard to our clients, they wouldn't pay us, end of story.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  74. The reason he mentioned it could be that by eddy · · Score: 2

    .. and this is for the paranoid out there:

    The reason he mentioned this flaw is because MS know of - or figure that there will now come to be - an exploit for said bug.

    At which time they (MS) can turn around and start crying about how talking about security problems only make things worse, and "see what we mean? We only mentioned it existed, and see what happend! Surely you can picture the horrors of opening the APIs?"

    We'll see.

    --
    Belief is the currency of delusion.
  75. War! by BurritoWarrior · · Score: 2

    What is it good for?

    Absolutely nothing, say it aga...uh, scratch that.

  76. New Anti-Microsoft Ads by jjohnson · · Score: 2, Funny

    [Head shots of teenagers against a black background, speaking directly to the camera; somber lighting; penitent tone]

    UNIDENTIFIED ACTOR: I helped murder families in Colombia.

    UNIDENTIFIED ACTOR: I just wanted to play Minesweeper.

    UNIDENTIFIED ACTOR: I helped kidnap people's dads.

    UNIDENTIFIED ACTOR: I just wanted to listen to music with Windows Media Player.

    UNIDENTIFIED ACTOR: I helped kids learn how to kill.

    UNIDENTIFIED ACTOR: I was just browsing with IE6, you know.

    UNIDENTIFIED ACTOR: I helped kill a policeman.

    UNIDENTIFIED ACTOR: I was just having fun.

    UNIDENTIFIED ACTOR: I helped a bomber get a fake passport.

    UNIDENTIFIED ACTOR: Other kids do it.

    UNIDENTIFIED ACTOR: I helped kill a judge.

    UNIDENTIFIED ACTOR: I helped blow up buildings.

    UNIDENTIFIED ACTOR: My computer, my OS.

    UNIDENTIFIED ACTOR: It's not like I was hurting anybody else.

    --
    Anyone who loves or hates any language, platform, or manufacturer, doesn't know what they're talking about.
  77. Their spokesman went on to say... by Omerna · · Score: 3, Funny

    "In response to the mass laughter we've been hearing upon admitting this, we'd just like to point out that if you were to release the source to say, Linux, it would have serious security problems too."

    Oh wait...

    --


    No sig for you.
  78. They don't know what they're getting into here by CaptainCarrot · · Score: 5, Insightful
    National security, huh? Does Gates understand that anything that must remain undisclosed for national security reasons is classified? Does he really want to have to deal with everything that entails: Security clearances and background investigations for every one of his employees, periodic audits, regulations that control how every single piece of paper and magnetic media is handled, filed, and disposed of?

    I work for a defense contractor and have had to put up with this for years. I suppose MS can go this route if they really want to. They're already bloated enough; add government security procedures to the mix and they'll become every bit as agile and responsive as any other constituent of the Military-Industrial Complex.

    Boy, that'd be a hoot.

    --
    And the brethren went away edified.
    1. Re:They don't know what they're getting into here by os2fan · · Score: 2
      And what would you make of their passing it around at schools, &c....

      --
      OS/2 - because choice is a terrible thing to waste.
  79. What happened with that? by 7-Vodka · · Score: 2

    Does anyone know what happened with that proposal? Did the peruvian congressmen vote on it yet?

    --

    Liberty.

  80. Re:Ridiculous argument! by Rick+the+Red · · Score: 2
    Was that humour or are you serious?
    That was humor, you Limey. And don't call me serious!

    --
    If all this should have a reason, we would be the last to know.
  81. Re:Yet another way of using FUD. by fok · · Score: 2

    I don't have any "boys fighting out there", so, I use free software...

    --
    \m/
  82. Squeak, squeak, boom! by leonbrooks · · Score: 2, Funny
    To Microsoft, we are all cute, squeaky animals.

    Except for those of us carrying nova bombs. Eeeyaaah! GPL'ed code! We're doomed!

    Jabba is also shown eating ugly, gronchy-sounding froggish thingies, but I don't think that invalidates your thesis. (-:
    --
    Got time? Spend some of it coding or testing
  83. Nader? by ImaLamer · · Score: 2

    I don't know if I really like him but I think we should vote for him next or someone who will just smash up MS into so many pieces....

    National Security means MS security. I guess since they have so much money and control so much of the economy they could bring down a portion of the country.

  84. Re:True, and... by Danse · · Score: 3, Insightful

    For example, if any inconvenient fact looks like it might support Creationism, there are those who immediately impugn it as being `War on Science'. (-:

    Of course the other side uses the same tactic as well. It's opportunism at its best. It takes a lot of integrity to resist using such tactics, especially when your opposition isn't reluctant to use them. I wish we could see more integrity in the world.

    --
    It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
  85. Missing the point by nemesisj · · Score: 2, Insightful

    It sounds to me like a lot of people on here are missing the point. The point isn't that Microsoft has sucky and bug prone software, the point is that Microsoft has pulled the wool over everyone's eyes again. Everyone on here immediately began laughing with glee and indignantly crying for the government to force MS to "recall" their software. Everyone is missing the point that MS will do anything to keep its advantage, which it believes lies in closed source code. Therefore, MS uses the national security copout, and wins again, all the while laughing at the nerds on slashdot who completely and utterly miss the point.

  86. Desperate Defense! by reynolds_john · · Score: 2, Insightful
    This is, pure and simple, M$'s desperate attempt to ensure that APIs simply stay out of the hands of the states - nothing more.

    Since they won't elaborate on any of the possible bugs [which by their statments might lead to Armageddon], it seems everyone must simply comply and exempt such APIs as M$ deems fit.

    I find it incredible that national security stems into Digital Rights Management (DRM). Can someone elaborate on how the two are even remotely connected? Also, are there any /. people using Message Queuing which might have some feedback on what this will do to their current plans?

  87. Alternative to Slashdot. by clinko · · Score: 2

    Please tell me an alternative to slashdot. I want news, not opinions.

    1. Re:Alternative to Slashdot. by josh+crawley · · Score: 2

      Try kuro5hin.org . It's not as good as slashdot. All you can do is VOTE ON ARTICLES, not have idiot editors reject them as the second they're sent, or have moderation on everybody. And about that moderation, it tells WHO EXACTLY modded you and what you gave them. In Voting on articles, you name is also associated wether you vote the article to front page or the bit bucket.

      Even after all these (cough) criticisms, it's not that good.

  88. I need a million bucks ... by Get+Behind+the+Mule · · Score: 3, Funny

    ... and I need a couple of clones of Britney Spears to keep around the house. If I don't get them, the war effort in Afghanistan may be endangered.

  89. Tools for Terrorism.. by mchummer · · Score: 2, Interesting

    A long time ago I had a sig line -
    __________
    Microsoft - The Number One Manufacturer of 'Tools for Terrorism (tm)'.
    __________
    This was inspired by the then almost weekly anouncements about security problems with the design of and use of Active-X, macro-viruses, IIS, etc.
    Now their lawyers have concurred.
    Guess I was right all along !

    - Mchummer
    __________
    ... I'll have grounds
    More relative than this: the play's the thing
    Wherein I'll catch the conscience of the king.
    Hamlet. Act ii. Scene 2
    __________

  90. How does this explain past viruses? by cant_get_a_good_nick · · Score: 2, Informative
    Hmmm, I don't remember that source code releases caused Nimda. Someone just probed with a long URL, caused a core dump (err, fault) realized this was from an unchecked buffer, and wrote the worm. No source needed to write the virus.


    Melissa? A combination of knowing about a way too scriptable mail client, knowing that most folks don't have extensions showing (another great MSism, don't show people what they get from unknown, untrusted folks in the mail), even though most would probably click on a .vbs file anyway. Pick up a VB book, write a virus. No source needed to write the virus.


    MS Word & Excel virii? Way too scriptable applications. Also from a VB book. No source needed to write the virus.


    Besides, the errors need to be fixed. Secuurity through obscurity hasn't really worked so far.

  91. http://jscript.dk/unpatched/ - 13 Without Source by NZheretic · · Score: 2
    "our APIs and code must be secret or the U.S. will crumble"

    20 May 2002: There are currently 13 unpatched vulnerabilities in Microsoft's Internet Explorer. The lack of source code access provides no real defense.

    See the latest issue of Bruce Schneier's Crypto-gram Newsletter

    Secrecy, Security, and Obscurity

    A basic rule of cryptography is to use published, public, algorithms and protocols. This principle was first stated in 1883 by Auguste Kerckhoffs: in a well-designed cryptographic system, only the key needs to be secret; there should be no secrecy in the algorithm. Modern cryptographers have embraced this principle, calling anything else "security by obscurity." Any system that tries to keep its algorithms secret for security reasons is quickly dismissed by the community, and referred to as "snake oil" or even worse. This is true for cryptography, but the general relationship between secrecy and security is more complicated than Kerckhoffs' Principle indicates. ...

  92. Surgeon General's Warning? by n76lima · · Score: 2, Funny

    If the M$ Code is so dangerous, maybe we can get Surgeon General David Satcher, M.D., Ph.D.
    to require warning labels on every box!

    "Warning: This product may exhibit serious security flaws and compromise National Security and cause death of US Soldiers fiting terrorism in foreign countries."

  93. yvaN eht nioJ by RelliK · · Score: 2

    yvaN eht nioJ

    --
    ___
    If you think big enough, you'll never have to do it.
  94. I told you so :P by Boiling_point_ · · Score: 2

    The NSA, for example, cannot sit and tinker with windoze's security holes the way they can with OSC (open source code)...

    If there really are nasty bugs in Microsoft Code running on millions of US civilian, government and military PCs, what's a quicker way of discovering them than resorting to the courts to open the code?

    Hey, I know, employ Howard Scmidt!! I made the point at the time that he's probably in the Whitehouse advising on just this sort of stuff.

    I'd guess your government already has a pretty good idea how brittle their national security really is...

    --
    "If you create user accounts, by default, they will have an account type of Administrator with no password." KB Q293834
  95. Re:er, no you're right... by Lumpy · · Score: 2

    BZZZT, sorry you're wrong... Don what do we have as a parting gift?

    Let's think for a moment.. Microsoft Loves to be in control... they absolutly adore getting you to run scripts of theirs as admin.. So why does this become impossible for MS administrators? Granted, Windows Admins are lacking in general computer skills let alone standard IS and IT knowlege.. but what the hell is stopping MS from making their version of up2date? I have a cron job that every friday at 3:02am runs up2date as root and automatically says yes to everything except for kernel.

    wow, I never have to think (like a MCSE) and my linux servers are all secure automagically... Granted if someone hacks redhat I'm toast.. but I'm betting that they wont get hacked.

    so again... what exactly is stopping microsoft from publishing patches and fixes every hour? what exactly is stopping them from writing an automated updating system? (I know critical update service already exists.. it's MS's fault that it isn't on everything on the planet and running right now... Hell let's change the EULA again... failure to do so invalidates the licenses and calls the BSA dogs.... your soul becomes the property of Bill Gates... oh wait, that's already in there..

    There is no excuse.. Microsoft can and should fix this stuff and get the patches in the wild ASAFP via an automated system.... how about a daily check to MS and if it get's back a 0 then everythings ok.. if it get's back a 1 then fire up and download and install...

    Unfortunately... one problem with microsoft products... most updates require a reboot... something no sane admin will allow automated on a critical server.

    --
    Do not look at laser with remaining good eye.
  96. Comment removed by account_deleted · · Score: 3, Insightful

    Comment removed based on user account deletion

  97. Re:True, and... by 1010011010 · · Score: 2

    "Creationism" is supportable by any available evidence, as long as the audience isn't capable of critical thinking. "Creationism" is a conclusion in search of supporting facts. It's the Shrink-to-Fit method; reduce the facts to fit the theory, and then hold it together with copper rivets. It's not science. It's faith. In science, no facts are "inconvenient." In religion, there are many inconvenient facts.

    --
    Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
  98. Re:ahah by mikefoley · · Score: 3, Insightful

    Actually, Microsoft has ALOT of talented engineers that are quite capable of writing excellent code.

    Unfortunately for Microsoft, the emphasis is on getting to market first (when you can't crush them otherwise with FUD or other methods). This accellerates the coding process and puts demands on quality, leading to shortcuts and an emphasis on new features over bug fixes.

    It's all finally coming to roost at Microsoft. You can't put out crap all the time. More and more people I talk to are getting frustrated. Ask anyone who understands the software environment , the only reason anyone uses Microsoft is because of the availability of apps, not because it's stable or of high quality.

    This is what's letting Linux and OSX in the door.

    --
    What's my Karma Mr. Burns? "Excellent"
  99. They control the sysadmins by Mandelbrute · · Score: 2
    In the context of system administrators who forget to patch their boxes
    MS control the education of people that become and remain sysadmins - I'm sure everyone here has heard of the fake engineering degree called the MSCE for example. MS can add a patch often mindset just by adding it to their courses, and making it so that if you don't answer questions on this and other important security questions you fail. If MS changes their security policy for the better, they can thus use their certification branch to their benefit (less bad publicity since things like code red wouldn't spread as far), and ultimately in this case to the benefit of anyone on the net. It's been made a professional qualification, so lets get them acting as professionals.

    I bet the next thing will be an MS fake architecture degree!

  100. I'd just like to see something along a B1... by Svartalf · · Score: 2

    An A1 certifiable system's grotesque overkill for most things the government does. Something along a B1 certifiable system would do nicely- something that an MS system couldn't do right now (nor, probably ever, from the looks of things at this point...).

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  101. MS Cites what????? by sallen · · Score: 2

    IF..and that's an if, Allchin was testifying accurately, then I'd say there's a real problem.

    (1) If you have 'bugs' that he sites as 'national security' reasons for not disclosing API's, you FIX THE BUG. If he is testifying truthfully, has MS notified DOD and other agencies of this potential flaw?
    (2) If accurate, it's the best case yet disclosed for open source in government.
    (3) If he thinks not disclosing it on the stand protects national security, the idiot (IMHO), just told everyone where to look. Secondly, I'd guess more than just 2 people at MS know of the flaws. He thinks if he just doesn't say anything, it won't get out? I doubt that every MS employee has government security clearances and is provided with periodic lie dectector tests
    (4) MS, if they knew about this and didn't disclose to DOD, etc, should be forced to bear the brunt financially for getting ALL government systems OFF MS software. If they've sold a single piece of software to a government agency such as DOD or NSA since knowing about it and not disclosing it should bear a HUGE legal impact. IMHO, that'd go as far as banning purchase of their software by any government agency where national security is impacted.
    (5) If anyone is going to cite national security, it should be an agency deemed as such. If MS has these concerns, then it's THEIR responsibility to notify DOD, DOJ, NSA, etc. It's the responsibility of THOSE organizations to determine if such items impact national defense and, if so, make motions before the court to preclude disclosure of certain API's etc. MS, I would hope, has absolutely NO legal footing to use a 'national defense' posture in refusing to release API's. I certainly dont' remember the Constitution saying that the government AND MS are to provide for a common defense.

    The ONLY 'one' (group) to come out smelling like a rose on this one.. the NSA. It seems the idea of a secure and hardened linux idea has been a very good move.
    This makes me furious. and it's not about MS and the antitrust.

    1. Re:MS Cites what????? by dbrutus · · Score: 2

      You missed one possibility. Allchin lied. But then again, that'd be perjury, 10 years in the federal penitentiary if they figure it out.

      Funny, perjury's the one thing I haven't seen mentioned up 'till now.

  102. I actually agree with Microsoft this time around.. by Mustang+Matt · · Score: 2

    I think they're telling the truth and they mean well.

    I only hope it convinces the rest of us to pull our heads out and realize what a monster we're dealing with.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  103. Behaviors aren't consistent, etc... by Svartalf · · Score: 3, Informative

    For example, the GDI calls aren't the same for Win95 and WinNT- API-wise, they're the same, but they don't DO the same things when called, merely similar things. Worse, if you try to PRINT the graphic you just did, the result will differ from printer to printer under NT but be surprisingly consistent for 95 for all printers. There's tons of others in that space.

    The API's declaration is consistent, but what one version of Windows DOES with the parameters may differ slightly or radically from another, supposedly identical one.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  104. Re:True, and... by EnderWiggnz · · Score: 4, Funny

    >The basic fact of religion is that God has
    >stated many times that He doesn't want to be
    >easily found--hence, no fact should be hard to
    >accept for anyone of a religious mind.

    prove that "god" "said" this.

    i'll accept *.wav's or *.mp3's or *.ogg's ... 1st person evidence please.

    --
    ... hi bingo ...
  105. Re:*Yawn* I think someone from Peru said it best . by dbrutus · · Score: 2

    The question is can they legally do security work for MS on the taxpayers dime. I bet that the legal department ruled no. Open source is different because the general public has access to their work so a technique to secure Linux or BSD can be adopted in other operating systems and thus more closely fits the character of computer security work that is in the government's charter. NSA fix MS code? Only if MS pays for it, and richly. And even then, you run into the problem of undercutting private sector code shops so the NSA still gets whacked.

    No, it isn't happening for well established legal reasons. The short version is we're not a bunch of communists.

  106. Re:not so evil? by dbrutus · · Score: 2

    Actually it's not workable. This has an obvious solution for MS, just don't fix the code and it stays secret. Why would they fix anything at that point?

  107. Re:How bad is their code? by dbrutus · · Score: 2

    My guess is that it's Netscape Communicator level bad, take it out back and shoot it bad. That's why they don't want to release it because they know their market position won't stand the gales of laughter from the wider programming community if it were made public.

  108. 25 die when "authentication" code locks out Airman by gsfprez · · Score: 3

    the NSA has come out with a no kidding, no XP rule.

    They will not allow anyone, classified or unclassified in the DOD to run XP.

    They do not plan to either.

    Believe me, its already making it "fun" to try to buy new PCs... i can't wait until 2004, when MS drops 2000 as a client OS, and then the bind we'll be in then, huh?

    A weapon system that locks up because it doesn't have the right authentication key. How cool would that be!

    fsck Microsoft. and Fsck the Air Force (where i work) - they are the stupid PHBs that didn't even concider anything else, didn 't look to anything else, and were too sheepish to try to find another solution that woudn't get us stuck in this way.

    what boneheads. I'm working on a project that is in jeopardy because the system will only run on Windows NT 4.0, and we're having a hell of a time finding sources for NT 4.0 that are legal.

    Pretty soon, we're going to just go illegal because we'll have no recourse.

    we're so stupid...

    --
    guns kill people like spoons make Rosie O'Donnell fat.
  109. My company's phone system by daviddennis · · Score: 2

    My company agreed with me when I proposed converting virtually everything our employees see to Linux, but on one thing they stood firm: They really, really wanted this phone system.

    It's called Interactive Intelligence, and it effectively converts a PC with speakers into a phone. Its great ability is that you can listen in to telemarketing conversations (vital in our business, sadly), get reams of statistics about how our people are doing, and so on.

    It has one flaw: It runs under Windows. You have to use a Windows client. It has a Windows server. And it integrates with Outlook, so everyone has to use Outlook for their email. For these reasons, I was knee-jerk against it, violently so. But I was overruled, and we bought it.

    We've had it for about a year and a half, and about a week ago, it caught a perfectly ordinary Windows worm. It apparently arrived through an email, spread through our network, and bam! Bye bye phone system.

    Our IT guy spent 72 sleepless hours cleaning up after it.

    I laughed. Well, if anyone else tries putting their phone system on Windows, now I know what to tell them. "It's not that Windows is bad, I'm as open-minded as anyone, but it sure is one heck of a security risk ..."

    D

  110. I agree with all your points but the last by daviddennis · · Score: 2

    Microsoft's own license agreement says they are not liable for anything save defective media. As long as the software installs on your computer, you're on the hook.

    And, before you say this is simply outrageous conduct, I fear it has to be that way. The viability of free software depends on the viability of near-identical clauses in the GPL, after all.

    To take a non-MS-related example, let's say my copy of Final Cut Pro just crashed and I lost an hour's worth of work. If everyone who bought the product was able to sue over problems like this, Apple simply could not afford the contingent liability associated with selling software.

    The technology simply doesn't exist to make today's increasingly complex programs 100% reliable. We can improve, yes, and we must. But our whole industry would collapse in lawsuits if companies were liable beyond the purchase price for packaged software problems.

    Of course Microsoft software is particularly notorious for this, thanks to its over-complex way of dealing with simple problems. Because of that I simply don't buy or use Microsoft software to any significant extent. I don't rely on it for my business, so it doesn't matter that it's junk.

    More people should do the same, and I hope this and similar stories will make people consider alternatives more seriously.

    D

  111. Re:True, and... by MulluskO · · Score: 2

    Leviticus 11 says hares chew cud, but do not have cloven hooves, and therefore are not kosher.

    Hares, for the record, do not have cloven hooves, but also do not chew cud.

    Like some other small herbivorous mammals they do produce a cud chewing like motion that may have fooled some Jews not quite so learned in the ways of science.

    Inconvenient fact if you're a Christian.

    In addition, Pi != 3;

    --

    Too busy staying alive... ~ R.A.
  112. This converts me fully... by BoneFlower · · Score: 2

    I used to accept the military using Windows for ease of training up system administrators to replace those killed in SCUD strikes or whatnot, and to draw on the large talent pool relative to UNIX...

    BUT, if this assertion is even partially correct, then the military needs to look seriously at alternatives. If national security is even slightly at risk from opening window information(accounting for the greater ease of fixing problems more opennness would create) then there is something seriously wrong.

    Iwould recommend Mandrake Linux to the US Military in light of this. Sure, its bloated to all hell especially in the non expert install mode. But its more secure and stable than windows, and critical bugs that could affect national security are found and fixed very quickly, and it allows the military to fix bugs itself if it wants to!

    Some of you may prefer Slackware or debian or what have you, but to get the power of linux in a military ienvironment you need ease of retraining, Mandrake is the easiest so for the military it makes the most tactical sense.

  113. People don't think that about games, video drivers by Mandelbrute · · Score: 3, Insightful
    Releasing patches often would give the average users the idea that "this software is crap, they keep finding problems with it, that little Updates thingie keeps popping up and annoying me, why didn't they get it right the first time?"
    People don't think that about games and video drivers, they just keep on patching. Perceptions change. Since people think rebooting more than once a day, let alone once a month is acceptable, why won't they accept patching once a month as being acceptable?
  114. Re:True, and... by cookd · · Score: 2, Funny

    Wow, that one is easy to handle (there are some harder ones out there -- I know, I've seen them!).

    Moses sluffed his Algebra and Zoology classes. So what? It is more than obvious that Moses screwed up from time to time. I imagine the conversation went something like this:

    God: ... And the people are not to eat the flesh of unclean animals.

    Moses: No unclean animals. Got that. So what is the definition of an unclean animal?

    God: Those that chew the cud and have cloven hooves.

    Moses Chew cud, cloven hooves. Ok, continue.

    God: Now, they must dress...

    Later that day...

    Moses: And you shall eat only clean animals, which are animals that chew the cud and have cloven hooves.

    Belligerent kid at the back of the crowd: Is this going to be on the final?

    Moses: Yes.

    Kid in the third row: Can you give us some examples?

    Moses: Cows, goats, oxen.

    Geeky kid: How about the bunny?

    Moses: No, the hare doesn't count. It doesn't have cloven hooves, see. Gotta have both.

    --
    Time flies like an arrow. Fruit flies like a banana.
  115. Re:Windows API's by shani · · Score: 2
    Now, I don't do any Windows programing myself (or rather, I stick to Perl and Python in Windows), but consider this thread:

    http://www.geocrawler.com/lists/3/SourceForge/709/ 0/8713541/
    The ZwXxx routines provide a set of system entry points parallel to some of the executive's system services. A call to a ZwXxx routine from kernel-mode code results in a call to the corresponding system service.

    Now, as Microsoft do not document the executive services, only the public WIN32 calls and the kernel-mode DDK calls, one has to rely on the ZwXXX documentation for the actual powers of these executive services. The interface should be the same when called from user-space as when called from kernel-space.

    I saw this on the User-Mode Linux mailing list this morning. A clear case of an API that only Microsoft is supposed to have access to.
  116. Re:er, no you're right... by 0xA · · Score: 2
    Unfortunately... one problem with microsoft products... most updates require a reboot... something no sane admin will allow automated on a critical server.

    Oh yeah, the reboot is the real problem with this. God knows there is no chance that an update or patch (from MS, Redhat, whoever) will have it's own list of bugs. Or won't work with "Product x". Or will just plain fuckup.

    Testing and rollback plans are for pansies and pinkos.

  117. So we have to trust anyone who *did* see the code? by gotan · · Score: 2

    That includes anyone at Microsoft, and all those folks who Microsoft showed relevant parts of code or of the API-fundamentals to. And US-security is relying on the slim possibility, that everyone of those large number of people is honouring the NDAs and won't be swayed by any sum of money or geek-status to disclose such critical information.

    This implies that Windows- (and thus US-) security relies on:
    A) everyone who did see the code honouring the NDA
    B) noone being able to reverse-engineer code/APIs
    C) noone happening accidentally over one of the huge number of security flaws and telling the wrong people

    To summarize, this "security" relies on the fact that noone tried very hard to breach it (or maybe it is already breached, and the russian, chinese and afghanistan (with their C64) spies are happily meeting in US-high-security outfits and plotting to bring the US-economy to a grinding halt by screwing up any US-corporation that relies on MS-software).

    If MS-Software is really that flawed the government should demand they fix their software until they can safely present at least their APIs, before they may go on selling any software. Considering how much depends on the security of MS-software that doesn't sound unreasonable to me. To make sure that MS follows those orders they could hold that nice stash of 'em for ransom.

    --
    "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
  118. Your Jefferson quote by leonbrooks · · Score: 2
    "History, I believe, furnishes no example of a priest-ridden people maintaining a free civil government." T. Jefferson

    Thomas Jefferson needed only to look at the pre-Roman Irish, Scots and Welsh in Britain (largely wiped out, while unarmed, in a single cold-blooded massacre by the soldiers of the Roman Church), or at the Ti-Ping movement in China (wiped out by the Manchu at the incitement of the Roman Church), or the the pre-Goan-Inquisition Saint Thomas Christians (wiped out by...?), or any one of a large number of other examples.

    The problem was not priests, per se, but priests who thought that God wasn't good enough to sort out the leadership by Himself. They're as bad as Atheists who opine that Darwinism is too slow and take it upon themselves to hurry things along. Think Stalin, Hitler, Mao, Pol Pot, Amin...

    And yes, it would be nice to see a little integrity about the place. Creationists generally don't call presumptions to evolution `War on Science' but something along the line of `running ahead of the facts'.
    --
    Got time? Spend some of it coding or testing
  119. Re:bizarre argument by markmoss · · Score: 2

    if you had source, would you be able to find instantly exploitable backdoors that would give you full root?

    It doesn't seem to be too hard to find those backdoors _without_ source, considering that new exploits occur at a rate of about one a week.

  120. Kerckhoffs' Principle by Martin+Spamer · · Score: 3, Informative

    Perhaps this Guy should have read this months (May 15, 2002) CRYPTO-GRAM by Bruce Schneier. The headline article is 'Secrecy, Security' and Obscurity' and covers the work of Auguste Kerckhoff, who in 1883, Yes 1883! demonstrated what has become know as Kerckhoffs' Principle, security by Obscurity is no security at all.

    To quote Schneier: "Any system that tries to keep its algorithms secret for security reasons is quickly dismissed by the [cryptographic] community, and referred to as "snake oil" or even worse."

    http://www.counterpane.com/crypto-gram.html

  121. Re:What if ... by Tony-A · · Score: 2

    If their code does get "opened", what are the odds that someone will find a really dangerous hole and exploit it?
    Very high. About the same odds that someone will find a really dangerous hole and exploit it if they do not release the source.
    What's different is the odds of the code being corrected and the corrected code actually being installed.

  122. Re:25 die when "authentication" code locks out Air by mpe · · Score: 2

    A weapon system that locks up because it doesn't have the right authentication key. How cool would that be!

    Maybe someone should design a system, based on Windows, which holds some bombs on a plane and then flys it over Microsoft's HQ/capital...

  123. Re:Microsoft - more security knowledge than the NS by Tony-A · · Score: 2

    their ad saying that their servers stay up for days without attention.
    That's an acomplishment???
    I'd expect a RedHat Beta to do better than that.
    I'd expect the kernel du'jour to do better than that.
    I'd expect an automated FeeBSD-Current to do better than that.

  124. They want it both ways. by Dr.+Manhattan · · Score: 2
    Actually, this is entirely consistent with MS's strategy all along: it has been arguing that it and its products are so profoundly important to the American economy and security that any remedy which interferes with its ability to act as it pleases should be struck down by the court.

    And there's the parallel strategy of claiming that they are just another company and don't have a monopoly so they don't deserve any special attention from antitrust laws...

    --
    PHEM - party like it's 1997-2003!
  125. Re:I could make a vacume cleaner that blows by eam · · Score: 2

    Quite a few vacuum cleaners are devices which both blow and suck.

  126. Re:So we have to trust anyone who *did* see the co by schon · · Score: 2

    If MS-Software is really that flawed the government should demand they fix their software until they can safely present at least their APIs, before they may go on selling any software.

    No, what the government should do is immediately switch to open source.

    "Your software is THAT insecure? My god, we must stop using it IMMEDIATELY."

  127. Re:Windows API's by ceswiedler · · Score: 2

    The Win32 API is not the kernel API, at least not for the NT derivatives. The Win32 API was written for something akin to "cross-kernel" portability (Win95/98 to NT to CE). It's a good idea and wasn't originally meant to obfuscate or hide the underlying APIs, but to provide a standard API across kernels.

    It's very similar to the glibc API, which hides the underlying Linux system calls.

  128. Re: Scientific method by Black+Parrot · · Score: 2


    > I believe the "Creation Scientists" are generally using anything but science to butress their case, I do think that they provide an important service. They harp on problems within the current set of theories that are taught, theories which are presented in schools with little or no rebuttal.

    Alas, the creationist is yet to be born who understands any theory of science well enough to point out problems in it. (For that matter, it's doubtful that one in 10,000 creationists even know what a "theory" is.)

    FYI, many scientists make careers of debating the problems with their own theories. Creationists have never added anything to the debate. (They're fond of pointing out errors like Piltdown man, but they always forget to mention that the frauds and mistakes they like to point out were invariably discovered by scientists rather than by creationists.)

    > For example, the systematic lack of transitional forms in the fossil record is one which calls into question the gradualistic evolution that was taught when I was in school...

    Browse talk.origins sometime and you'll notice that the one thing creationists never let themselves be pinned down on is the definition of "transitional". They incessantly assert that no such things exist, but won't even define the term. Whenever someone cites an example the creationists just handwave it away with "that's not transitional".

    > Can teenagers be hurt by being presented both the pros and cons of the various theories in a balanced way?

    No, I don't suppose it would hurt. But creationists have never pointed out any pros or cons of biological theories -- neither in a balanced way nor otherwise. Also, I'm curious why you seem to think that gradeschoolers should get the full dosage of "outstanding problems in evolution". In physics, mathematics, computer science, and in areas of biology other than the theory of evolution, that is generally reserved for grad school. Why the special treatment for the theory of evolution? Other than the fact that it offends a lot of people's religious beliefs?

    --
    Sheesh, evil *and* a jerk. -- Jade
  129. Re: True, and... by Black+Parrot · · Score: 2


    > God didn't change his mind about creating the earth. The Man that God created went off and became wicked, and God cried over them as a parent cries over the bad choices of a child. (Of course, most parents don't go kill their kids and start a new family when the first one doesn't go so well, but that is another problem to explain... I would be here all night!)

    Give it your best shot. Be sure to tell us how many infants drowned in the flood.

    There's no excusing the inexcusable.

    Also explain why an omni*ent god applied a fix that didn't work: the ground was hardly dry before his champion of righteousness got drunk and showed his peepee, and of course the world is brim-full of wicked people right now. What did the flood accomplish?

    --
    Sheesh, evil *and* a jerk. -- Jade
  130. Re: True, and... by Black+Parrot · · Score: 2


    > The core Truths of "Religion" never change. However, Man's understanding of them will always be limited, and the application of the core Truths will change according to environment.

    IOW, "The core 'truths' of religion are in constant flux."

    The key difference between science and religion is that science is guided by evidence and religion is guided by tradition + a dash of this week's social views.

    --
    Sheesh, evil *and* a jerk. -- Jade
  131. You see, it's like this... by Anonymous+DWord · · Score: 2

    Like that?

    --
    "If he thinks he can hide and run from the United States and our allies, he's sorely mistaken." Bush on bin Laden
  132. Re:True, and... by Planesdragon · · Score: 2

    Ok, then. If that's our standard of evidence, prove that, oh, the United States of America rebelled from Great Brittain. First person evidence only, please. ;)

  133. Take a look at what is hidden in windows... by Polo · · Score: 2

    Here's an interesting look at purposefully hidden files under windows. It's amazing if you look through it all. Your browser history doesn't go away, etc... Stuff like "show all files" and "find" have been purposefully written to ignore this stuff.

    http://sillydog.org/mshidden.html

  134. Demonstration time! by leonbrooks · · Score: 2
    That's the problem with believing in something that you can't reasonably demonstrate. You often end up having to set aside logic and rationality, and that leaves you vulnerable to becoming a blind follower. You learn not to ask for proof or evidence because that shows that you lack faith.
    I've often wondered why so many evolutionists are reluctant to question their foundations. Thanks for clearing that up for me!

    The only difficulty with `demonstrating' God is that most people try to `demonstrate' their mental model of Him instead. If you're looking for reproducible results, you're looking for a God who is in essence completely under your control, and what use would that be? OTOH, if you're looking for things than only make sense from a God-based worldview, start with a large polystratic fossil and work out from there. There are many other starting points, but that's a nice, clear, scientific, even geologic one for you.
    --
    Got time? Spend some of it coding or testing
    1. Re:Demonstration time! by Danse · · Score: 2

      I've not seen or heard of anything that requires a god to explain its existence. There is much that we don't know, but the fact that we don't understand, and may never understand, certain things, does not mean that it must be attributed to some deity. Let alone a deity that would have anything at all to do with human religions.

      --
      It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
  135. Homer Simpson's Prayer by leonbrooks · · Score: 2
    Dear Lord: The gods have been good to me. For the first time in my life, everything is absolutely perfect just the way it is. So here's the deal: You freeze everything the way it is, and I won't ask for anything more. If that is OK, please give me absolutely no sign. [pause] OK, deal. In gratitude, I present you this offering of cookies and milk. If you want me to eat them for you, give me no sign. [pause] Thy will be done. [crunch, crunch, slurp, slurp]

    Spot the deliberate mistake. It's worth noting that Marge is at this point trying to tell Homer that she's pregnant. For a detail analysis of Homer's prayer, I recommend this book (and read the reviews, too!).

    Now have another look at polystratic fossils (there are many other examples, this is one of the nice simple ones). These fossils penetrate several rock layers, typically to the tune of `tens to hundreds of millions of years' worth of deposits. Some large trees strike vertically through tens of meters of rock, and there is no sign of reworking, no turbulence in the rock, such as there would have been if the tree had been somehow thrust down through the rock; and there are many examples which are much too frail (with extensive branching etc) to have survived any kind reworking.

    Name the tree which will stay intact for hundreds of millions of years while it is buried. AFAIK, not even wandoo will survive more than a few hundred years of exposure, and that is incredibly hard wood (wandoo weighs about twice as much as jarrah, which is hard wood to start with). Now revise your answer to account for a complete lack of weathering, a common feature of these fossils.

    Now, the requirement for supernatural intervention here is this: if the rock surrounding a polystratic fossil did not take hundreds of millions to put into place, but at most years (or more likely hours or minutes), and there are many polystratic fossils (there are) this is pretty direct evidence that most if not all rock formed very quickly.

    Sorry if this sounds pedantic, but you seem to have let the point escape you in the previous post.

    Now, evolution as a theory of how-we-got-here is simply impossible; there is no way to even approach the biological structuredness we see around us no matter how much time you allot to the purpose. However, this requires technical knowledge to illustrate and understand.

    If polystratic fossils can so simply and clearly show that the millions of years postulated for evolutionary development are imaginary, it does not take a technical mind or a great deal of imagination to see that, with naturalism's only viable explanation dead, an alternative is required.

    END-OF-POINT MARKER

    Now, on a different but related topic, it happens that a lot of ancient records from all over this world mention an event ideally suited to emplacing polystratic fossils - and incidentally accounting well for many other features of geology such as the `Cambrian Explosion' - and this event does not require millions of years. Many accounts attribute weeks, months, a year or a few years' duration to it. Is it hard to figure out what I'm alluding to?
    --
    Got time? Spend some of it coding or testing
  136. What? An intelligent response...? by leonbrooks · · Score: 2
    Well, knock me down with a wheatstalk! (-:

    While I myself would argue that an example such as this does not necessitate a "God-based worldview" I admit that that item is up for debate.

    Excellent! I'm eagerly waiting to hear about a worldview which encompasses non-intrusive, non-weathered large-scale polystratism, but is not at least supernatural. (-:

    I think I can say with certainty that it does not require [...] any other god that has been created by man.

    Agree, an artificial God is utterly pointless, for by definition it has no more power or use than that bequeathed upon it by the hand of its creator. The basis for Christian, Muslim or other dieties is a separate question and should not be rolled into your statement as an implied assertion, when in reality it is a question which has apparently not been examined in enough detail to provide any conclusive or even substantial answers.

    any attempt to convince me that you have any idea what that thing looks like or what its motiviation are is well ... silly.

    I reiterate, a God that you could completely understand (and so, in principle, control) is by definition a useless one.

    Thankfully, we don't need to either have a description in hand, control, or even basic understanding of a putative creator in order to know that one is required in order to explain the existence of nature as we see it today.

    Once you have escaped the trap of materialism, that is, once your reasoning can encompass naturalistic asymptotes, you can begin to look for more detailed explanations than `life as we know it required drastic supernatural intervention of some kind'. IMHO, such details are available to science.
    --
    Got time? Spend some of it coding or testing
  137. Foundations, polystrata, three stars, a question by leonbrooks · · Score: 2
    I've often wondered why so many evolutionists are reluctant to question their foundations. Thanks for clearing that up for me!

    Maybe I can clear it up a little further.

    Or not....

    "Questioning my foundations" is what led me to reject creationism, and favor evolution, in the first place.

    And so what happened? You seem to have either stopped questioning too early, or to have based your conclusion on the strength or weakness of some individual's position, rather than on the strength or weakness of the available evidence itself.

    I started my thinking life as an evolutionist. I upset Mum badly one day (but she didn't show it then or ever) by mentioning some one-line wisdom I'd heard to her in a 'phone conversation: `a man needs religion like a fish needs a bicycle.' She started praying for me that day (and asked her church to as well), said nothing to me, and within two months I was studying the Bible, history and science with a variety of people and within six months was a committed Christian - although in such a completely different branch of Christianity to hers that I think Mum died not completely convinced that her prayers had been answered.

    One advantage that I've had is in directly witnessing several supernatural events, through my association at the time with a `white' witch (the basic difference is in purpose, not in methods). One of those takes a while to describe, involved two other sober people, and was deeply shocking. Another was watching some books leap out of a book-case unaided (I checked the book-case and books (and wall) all over, inside and out, carefully, and made sure that there was no mechanical trickery here) and several meters across the room. Even without that advantage, you can turn to one of the very many events which were clearly supernatural, witnessed by many people, and well documented (Lloyds subsequently came back at $500 PA and extended coverage to Guyana).

    I suspect that such events are not more prevalent today for several reasons, foremost among which are (1) any diety interested in wholehearted allegience would probably want it to depend on that nature of that diety, rather than on a `sugar-daddy' stream of miracles, and (2) there is apparently more than one source (direct or indirect) of supernatural effects, which opens the field more widely to fraud.

    I'd presumed upon the millions-of-years thing myself, and polystratic fossils are one of the more graphic and convincing observations which overturned that presumption for me. Of course, sans millions of years, materialism doesn't even give the appearence of being in the running.

    For example: the Yellowstone trees (so often cited as evidence of life over millions of years) combined with dendrochronology (also so often cited as proof of excessive amounts of time) are actually a fairly clear witness to the absence of those years, for the Yellowstone fossils are not only polystratic and bedded on different strata but also grew contemporaneously and show strong symptoms of having been emplaced by a mechanism essentially identical to that observed in Spirit Lake after the eruption.

    There are many, many other good polystratic examples to
    hand, including inclined trees, and also many half-hearted attempts to explain them away. One of the common `counterexamples' is a set of lycopods with root systems; an examination of the available samples indicates that these trees grew floating, or at least on an extremely spongey substrate, so it is reasonable to expect them to be disturbed and embedded complete with roots. Even ignoring this, it is still most unreasonable to expect even relatively short (1.2m, in the worst case) stumps to be fossilised upright and intact in an evolutionary scenario.

    It is the height of arrogance to assume that someone is closed minded just because they have reached a conclusion different from yours.

    Yah, and the height of stupidity as well. Given the number of viewpoints in the world, simple arithmetic tells you that most or all of your (and my) opinions are globally wrong in some way. (-:

    ...and don't get me started on `contextually wrong'! (-:

    After all, if we hold a view, it's usually because we think it is correct. Each side would do well to remember that this is true of the other side as well. I can't count the number of times I've been guilty of this error myself.

    If I was a Wemmick, I'd give you at least three stars for that statement. (-:

    Food-for-thought time.

    Five-year-old Mary was obliged to undergo an operation, and lost so much blood that it was necessary to resort to blood transfusion. The blood of thirteen-year-old brother Jimmy was found by test to match exactly the little patient's. "Will you give your sister some of your blood, Jim?" asked the doctor. Jimmy set his teeth. "Yes, sir, if she needs it." He was prepared for the transfusion. In the midst of the drawing of the blood, the doctor observed Jimmy growing paler and paler. "Are you ill, Jim?" he asked. "No, sir, but I'm wondering just when I'll die." "Die?" gasped the doctor. "Do you think people give their lives when they give a little blood?" "Yes, sir," replied Jimmy. "And you are giving your life for Mary's?" "Yes, sir," replied Jimmy.

    Mary and Jimmy are pseudonyms, but the story is true. If you had been Jimmy, would you have done the same?
    --
    Got time? Spend some of it coding or testing