Slashdot Mirror


New Vista Random Numbers to Include NSA Backdoor?

Schneier is reporting that Microsoft has added the new Dual_EC-DRBG random-number generator to Vista SP1. This random-number generator is the same one discussed earlier that may have a secret NSA backdoor built into it.

269 comments

  1. Really... by 2names · · Score: 5, Funny

    I guess it's not so secret then, is it?

    --
    "I'm just here to regulate funkiness."
    1. Re:Really... by I_Heat_Sexylaid · · Score: 0


      "The men don't know, but the little girls...understand..."

      --
      Slashlight! (Can't find the funk) kewl base part
    2. Re:Really... by Jeremiah+Cornelius · · Score: 1

      Veracity
      Integrity
      Security
      Trust
      Assurance

      What's not to like?

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    3. Re:Really... by Anonymous Coward · · Score: 0

      Tag sensationalism, please.

    4. Re:Really... by nickyj · · Score: 1

      Wait... couldn't you just add something to the random number? Or perhaps shift the digits over? or just do anything to the number generated and then *poof* no backdoor? Or am I not understanding this?

      I know in Perl's rand function you can seed it with whatever you like. I'll admit I'm not a cracker.

      --
      Causing Chaos Everywhere,
      Nik J.
      The strange world of a loner, in a populous city, drowning in society
    5. Re:Really... by Anonymous Coward · · Score: 0

      No Performance?

    6. Re:Really... by sexconker · · Score: 0, Offtopic

      Mod parent troll - that damned datamining site again.

    7. Re:Really... by MadUndergrad · · Score: 0, Offtopic

      What the hell is that site? Asshat's been spamming that in every story lately.

    8. Re:Really... by Applekid · · Score: 3, Insightful

      What you're essentially proposing is encrypting the same data twice, first with the questionable algorithm, then with another algorithm of your choice. If that's the case, you might as well just encrypt it with the second algorithm, hopefully more complicated than just shifting and adding. ;)

      --
      More Twoson than Cupertino
    9. Re:Really... by yo_tuco · · Score: 5, Informative

      "Wait... couldn't you just add something to the random number? Or perhaps shift the digits over?"

      You can do what TFA said:

      "It's possible to implement Dual_EC_DRBG in such a way as to protect it against this backdoor, by generating new constants with another secure random-number generator and then publishing the seed. This method is even in the NIST document, in Appendix A."

    10. Re:Really... by The+Ultimate+Fartkno · · Score: 2, Informative

      Datamining? I thought it was just another of those stupid online games that encourages you to spam everywhere.

    11. Re:Really... by Feyr · · Score: 1, Funny

      it's an OS for women, they dont need nor want performances, unless it's a hamlet play

    12. Re:Really... by Gregb05 · · Score: 1

      I've come up with a wonderful algorithm. What you do is keep a 'sum' number, and randomly generate a 'shift' number by shifting the original bits n times, then add this number to the 'sum' number. It can be repeated as many times as you want, with randomly generated n's. I was trying to come up with a good name for it, and all I thought of was my daughter, Multi...

      --
      --
    13. Re:Really... by hax0r_this · · Score: 2, Interesting

      What is the point of plugging the output of a secure random generator into a non-secure one? Why not just use the secure one?

    14. Re:Really... by cgenman · · Score: 1

      Really? My limited understanding is that the default numberset isn't a seed so much as controlling the method of randomization. But that the result may be predictable if one knows the encrypted number which pairs with the default numberset. In other words, if you change the default numberset to ANYTHING else, even a static number, you've effectively thwarted anyone who may have a key pair.

      It's not randomizing the data twice. It's simply changing the default numberset to a different numberset and thus thwarting the potential issue.

    15. Re:Really... by caluml · · Score: 2, Funny

      The secure one goes up to 11 (3).

    16. Re:Really... by HiThere · · Score: 1

      One reason might be disguise. If it's disguised as something encoded with an insecure encryption, then it won't attract as much attention...but if they *do* happen to get curious about it, there's the inner layer to prevent them from actually cracking it.

      You can plug lots of different "you"s and "them"s into that approach, it's not a sword with just one edge. Think of it as using steganography inside a tgz file. The tools for handling the png & tiff files need to unpack the file just to determine that it's a picture. THEN they get to check it for hidden messages. (Yeah, that's a pretty easy approach. It's common which is why I picked it.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    17. Re:Really... by PacketScan · · Score: 1

      I know right.. I just wish i could have some privacy.. wait i do i don't use winblows.

    18. Re:Really... by Thorwak · · Score: 0

      Nor is it very random :P

      --
      Connection closed by foreign host.
    19. Re:Really... by mystran · · Score: 1

      And since we can expect Microsoft to know how to do that, we could also expect that instead of NSA, it's Microsoft that holds the backdoor to the generator in Vista. No?

      --
      Software should be free as in speech, but if we also get some free beer, all the better.
    20. Re:Really... by Xformer · · Score: 1

      After removing everything that Vista doesn't offer, we're left with V (we are talking the product and not the company, after all). Does that mean, then, that Microsoft is populated by a bunch of biped lizards that see the world only as something to consume?

      --
      All I want is a kind word, a warm bed and unlimited power.
    21. Re:Really... by Jeremiah+Cornelius · · Score: 1

      That's an icke thought!

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
  2. Section Tag by solar_blitz · · Score: 1

    Wouldn't this go under "Your Rights Online"?

    1. Re:Section Tag by backbyter · · Score: 3, Funny

      What Rights Online?

    2. Re:Section Tag by naapo · · Score: 5, Funny
      Don't know about our rights online, but I gladly noticed that this was tagged quite appropriately

      ahhjeezenotthisshitagain
      It was not exactly a dupe, but clearly an "ahhjeezenotthisshitagain".
  3. Conspiracy theorists come forth! Now it the time.. by Recovering+Hater · · Score: 0

    To regale us with the myriad ways in which government plots are about to unfold with this. But sincerely, this is ripe for negative speculation. There is no good reason for something of this nature. Sure, some will say it's for the kids and what about the terrorists being thwarted before they can act and all, but I still say this is BS. Closed source buffoonary if you ask me.

    --
    My humor is probably your flamebait
  4. From the article by tieTYT · · Score: 3, Insightful

    "It's not enabled by default, and my advice is to never enable it. Ever."

    1. Re:From the article by Smidge204 · · Score: 5, Interesting

      It's not enabled by default ... until the next Automatic Update rolls around.

      =Smidge=

    2. Re:From the article by Daimanta · · Score: 1

      That's what I think about Vista.

      And if you really want to be secure, you can throw Windows on the same heap.

      --
      Knowledge is power. Knowledge shared is power lost.
    3. Re:From the article by Anonymous Coward · · Score: 1, Informative

      Except that windows update doesn't do that.
      Seriously, it doesn't.

    4. Re:From the article by Stray7Xi · · Score: 2, Funny

      Windows update doesn't update that now, there will be an update to make windows update update this though.

  5. Given the known problems of Dual_EC_DRBG by morgan_greywolf · · Score: 5, Interesting

    Given the known problems of Dual_EC_DRBG, which, from the Bruce Schneier article, include the fact that's slow, that it's got an obvious backdoor, and that it was inexplicably pushed for the NSA for seemingly no reason, why would Microsoft add it to Vista SP1?

    Now adding the algorithm itself isn't really a backdoor per se, because no one is forcing you to use that particular random number generator. But it is also interesting to note that this isn't the first time Microsoft has been accused of inserting backdoors for the CIA or the NSA. Of course, Microsoft vehemently denies such allegations, but I would assume that they would. Given what the telcos did for the NSA, would anyone be surprised if it really did come out that the NSA actually forced Microsoft to put backdoors in Office or Windows?

    1. Re:Given the known problems of Dual_EC_DRBG by RightSaidFred99 · · Score: 5, Informative
      I know this is crazy talk, but maybe there's a simple explanation. Microsoft put it in the OS as an option so that people who want to use it (hmm...government contracts?) can if they so choose. So maybe Microsoft sees the NSA as a "customer" and decided they were important enough to include it for their use and for other government use.

      Insane - I know, they must be "out to get us".

    2. Re:Given the known problems of Dual_EC_DRBG by CastrTroy · · Score: 2, Informative

      because no one is forcing you to use that particular random number generator
      That's hard to say. What does Vista use this RNG for internally. Does it use it for generating keys for use in SSL communications in Internet Explorer? Does it use this RNG to generate random keys for connecting to a VPN? Does it use this RNG to create a salt when storing your passwords? Does it use this RNG to generate the keys for BitLocker? There's many places where one may be using this RNG without even knowing it.
      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    3. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0

      Given what the telcos did for the NSA, would anyone be surprised if it really did come out that the NSA actually forced Microsoft to put backdoors in Office or Windows?

      I guess the surprise would be why wouldn't the CIA just use any one of the wide-open front doors?
    4. Re:Given the known problems of Dual_EC_DRBG by morgan_greywolf · · Score: 1

      According to TFA, this was added in SP1, so my guess to all of those would be "no", unless these components were updated by SP1 to use the Dual_EC_DRBG.

    5. Re:Given the known problems of Dual_EC_DRBG by davidsyes · · Score: 1

      Maybe it's because mshaft are in bed with the NSA? After all, the various US intel agencies (and probably those of many governments) want to decrypt ANYthing they think is important enough to them, and they want QUICK not painstakingly-slow access to the plain text.

      By including the back doors, mshaft can further differentiate itself from Open Source, maybe to marginalize OpenSource (I wonder what Novell will say in this regard) and try to make companies and governments think OpenSource/Linux applications and operating systems are somehow tools of terrorists, anarchists, activists and so forth. After all, this IS msoft we're talking about. They don't like competition that is REAL competition.

      --
      Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
    6. Re:Given the known problems of Dual_EC_DRBG by secPM_MS · · Score: 3, Insightful
      Sorry to deflate the conspiracy theorists. Certain governmental customers wanted the ECC random number generator. MS provided it. This random number generator is not used by default. The default random number generator is CryptGenRandom, which was revised to deal with the issues that have been discussed with rather more sensationalism than was warranted.

      Customers who want to use the ECC generator can choose to use it. This is rather like turning on FIPS mode.

      As for backdoors, anybody who is paranoid about this issue will ignore or disbelieve me when I say that there is no backdoor that I am aware of. The Common Criterial evaluators look for such issues and submit issues for fixing if and when they find them. Other governments are not going to be willing to buy a system with a NSA backdoor. From a more practical demonstration point of view, if there was a backdoor, governments would not need to get warrants for inserting hardware keyloggers or custom malware on systems to access system information. Governments both in the US and elsewhere do this, which suggests that no backdoor is available.

    7. Re:Given the known problems of Dual_EC_DRBG by morgan_greywolf · · Score: 1

      I wouldn't go that far. The NSA did develop SELinux, after all.

    8. Re:Given the known problems of Dual_EC_DRBG by CastrTroy · · Score: 1

      That's not the point. The point is, is that using this RNG may actually be unavoidable in any number of instances. It may not be used in the instances I pointed out, but there could be many uses of this RNG in the OS, and it would be hard to avoid it. Who's to say they didn't update the previously used RNG to just call this one?

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    9. Re:Given the known problems of Dual_EC_DRBG by morgan_greywolf · · Score: 5, Insightful

      Who even says that at an RNG has to be at the OS level? If NSA or its customers want to use Dual_EC_DRBG, there is nothing stopping them from doing so on Vista or any other OS.

      As another poster said, where in the OS is this used? Do you know? Does anyone but Microsoft?

    10. Re:Given the known problems of Dual_EC_DRBG by Dr_Marvin_Monroe · · Score: 1

      To follow up on the poster's point, I've believed that there's been collusion between MS and the Government since GWB's quick settlement of the anti-trust case, and my "tin-foil hat" is not looking so silly any more. At the same time he's wrangling with the telcos to get access to domestic phone records and calls (as the NYT points out, almost immed. after he enters office), he's most likely wrangling with MS to get back doors installed. At least that's what I'd do, and I'm possibly of "normal" intelligence. It's an obvious thing to do...step 1: get access to all communications by legal means or not, step 2: make sure that the OS that runs +90% of computers has a back-door that you can easily get to.

      Being the very shrewd "son-of-a-lawyer" that Bill Gates is, I'm pretty sure that he offered up back-doors in exchange for the government getting off MS's back. Quid-pro-quo.

      Now that this stuff is coming out, the NYT should start digging here too. Remember that the British government PUBLICLY asked for one (back-door to BK? I can't recall exactly)... but they didn't have any leverage to force MS to respond. US had the conviction in hand and was ready to proceed, that would have caused Bill Gates to respond, especially after his poor performance on the stand.

      Yep. Now we just need to find the smoking gun...

    11. Re:Given the known problems of Dual_EC_DRBG by morgan_greywolf · · Score: 5, Insightful

      This random number generator is not used by default. Prove it. Oh, that's right, you can't because you don't have the source code. Unless maybe you're astroturfing. Even then you'd be under an NDA anyhow.

      Other governments are not going to be willing to buy a system with a NSA backdoor. And other governments have replaced Windows with custom Linux distros due to the potential of this very problem. This is a fact that cannot be denied.

    12. Re:Given the known problems of Dual_EC_DRBG by Haeleth · · Score: 1

      From a more practical demonstration point of view, if there was a backdoor, governments would not need to get warrants for inserting hardware keyloggers or custom malware on systems to access system information. Governments both in the US and elsewhere do this, which suggests that no backdoor is available.
      If you think that kind of argument is going to convince a conspiracy theorist, you're more nuts than they are. Clearly the governments only go through the motions of getting warrants in order to make people think there isn't a backdoor. Why else would they deny it?

      Bearing in mind that the bill to pay off all the people involved in the moon landings hoax is decreasing every year now they've started to die off, it's likely that the US Dept of Coverups has plenty of budget to spare for this kind of thing now.
    13. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0

      The NSA has two essential mandates: to protect America's information security, and to undermine other countries'. SELinux is part of the first. This is part of the second. It has worked well, too. SELinux is only used by people who need it and know about it. Also note that SELinux is an ACL mechanism, and has little to do with random numbers or encryption.

    14. Re:Given the known problems of Dual_EC_DRBG by morgan_greywolf · · Score: 1

      You're right. And there's no way to know unless you have the source. And, well, let's just say Windows Vista ain't exactly open source.

    15. Re:Given the known problems of Dual_EC_DRBG by Hymer · · Score: 1

      I dont get this... NSA is active SE Linux developer. Why would they require a backdoor to Windows ?
      That may make them untrustworthy as a development team/partner... is there a backdoor in SE Linux too ?
      I can't imagine NSA would be interested in that...

      NSA got probably most raw computer power in the world, their building uses more electric power than a small city, they shouldn't need backdoors. I think it is DOJ/FBI requirement.

      I wondered btw. why my 8 years old firewall supports AES encryption (for VPN) with 2048 bits strength but no currently available products supports more than 256 bits.

    16. Re:Given the known problems of Dual_EC_DRBG by secPM_MS · · Score: 3, Insightful
      I don't have to prove it. Not only that, but you wouldn't believe me if even if the code was released - after all, how do you know that the code corresponds to the actual binary?

      Look at the FIPS and CC documentation. Governments do use these systems in security critical environments, but they configure them very carefully. There is configuration data available on how to configure system for security critical environments. Selecting your random number generator is one of the things you can do.

      The staff working on this are noted cryptographers who do know what they are doing. I have been working with the cryptographers at Microsoft for some time and I have been working in crypto related areas for > 20 years.

    17. Re:Given the known problems of Dual_EC_DRBG by Applekid · · Score: 1

      I disagree about making snooping warrants obsolete. Prosecutors love (and, many times, need) redundant evidence to make sure the accused it put away for a long time.

      --
      More Twoson than Cupertino
    18. Re:Given the known problems of Dual_EC_DRBG by rjhubs · · Score: 1

      I sure hope our government isn't encrypting their information with a RNG with a known backdoor. That seems pretty stupid. It would seem the reasonable explanation is the government is out to get us.

    19. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0

      "why would Microsoft add it to Vista SP1?"

      When one part of the Federal Government hampers one's clearly illegal business model by slapping a five-year antitrust watchdog on one and another part of the Federal Government says "Do this for us and we'll replace the watchdog's teeth with dentures" -

      The NSA didn't force anyone to do anything. The directors of Microsoft keep their money in banks insured by the Federal Government, their stock shares (and the timing of the granting and exercising of same) are regulated by the Federal Government, their homes, cars, bank accounts and lifestyles are all easily seizable and auctionable by the Federal Government (never mind guilt or innocence) for a variety of apparent or real crimes, from victim-laden (securities fraud) to victim-less (taking a hit on a joint in the privacy of their own home, or even overseas on vacation, even MERELY VIEWING PORNOGRAPHY ONLINE {still a crime on the US Federal books}). Their golfing buddies all run those banks, trade those stocks, own shares of the telcos, hold open doors to no-bid government contracts and tap shoulders to meet the movers and shakers.

      Play along, and you can find any number of backers for your next venture, and your retirement fund is ensured.

      Don't play along, and you can easily find yourself retiring to a trailer in the Painted Desert, career over.

      The same holds true for the directors of the telco companies, and their executive officers.

      No one is FORCING consumers to choose Time Warner Cable in Ohio, either. No one is FORCING consumers to subscribe to ridiculously expensive cellular plans, No one is FORCING consumers to buy the latest and greatest and most expensive technological toy either.

      Never mind that there's no place left in the world to go to start a new nation, no place left in the wireless spectrum and what IS available is ridiculously expensive, no other local cable provider, etcetera.

    20. Re:Given the known problems of Dual_EC_DRBG by dvice_null · · Score: 4, Insightful

      > As for backdoors, anybody who is paranoid about this issue will ignore or disbelieve me when I say that there is no backdoor that I am aware of.

      I can believe that you don't know, but would they really tell you if there were such backdoors?

      > Governments both in the US and elsewhere do this, which suggests that no backdoor is available.

      If you had a backdoor which allows you to access remote computers anywhere would you
      a) Tell everyone that you can do it
      b) Use some dummy keyloggers and malware to suggests that you can't do it

    21. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0

      "I wondered btw. why my 8 years old firewall supports AES encryption (for VPN) with 2048 bits strength but no currently available products supports more than 256 bits."

      If it is a US product, then possibly it is because the US puts a "speed limit" on encryption for products that get exported. So if a US vendor wants to sell their product elsewhere and keep it the same, they need to be wary of export control restrictions.

    22. Re:Given the known problems of Dual_EC_DRBG by dpninerSLASH · · Score: 1

      But it is also interesting to note that this isn't the first time Microsoft has been accused of inserting backdoors for the CIA or the NSA. Of course, Microsoft vehemently denies such allegations, but I would assume that they would.

      So if Microsoft denies an allegation against them, it's inherently true? Sounds just a weeeee bit suspect.

      My feelings toward Microsoft are not incredibly warm, but this is silly. I read the linked blog post and the author himself goes out of the way numerous times to point out that he had no way of knowing whether such backdoors existed or not.

      The best way to "dethrone" Microsoft (if that's what you happen to live for) is to focus on the positive aspects of its competitors products, not obsess over imagined shortfalls in their's.

    23. Re:Given the known problems of Dual_EC_DRBG by calebt3 · · Score: 1

      I wouldn't go that far. Microsoft might. You never know.

      The NSA did develop SELinux, after all. The public does not know that.
    24. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0

      If you trust the common criteria to actually catch *ANYTHING* useful or innovative, you're a bigger fool than the NSA for trying to sneak this in...

    25. Re:Given the known problems of Dual_EC_DRBG by adolf · · Score: 1

      I could make the same argument about anything:

      Who even says that a GUI has to be at the OS level? If the NSA or its customers want to use graphics, there is nothing stopping them from doing so on Linux or any other OS.

      Or:

      Who even says that a filesystem has to be at the OS level? If the NSA or its customers want to use files, there is nothing stopping them from doing so on *BSD or any other OS.

      Or even:

      Who even says that a TCP/IP stack has to be at the OS level? If the NSA or its customers want to use Teh Intarwebs, there is nothing stopping them from doing so on Vista or any other OS.

      So, thus shown that there is no reason to ever include anything in an OS, might you care to show some reason why an OS shouldn't include one or more RNGs? Nobody's forcing anyone to use it. It's just another tool.

      It seems to me that MS is simply doing what the Unix people have been asking MS for all along: Unlike DOS, modern incarnations of Windows can actually provide useful and consistent APIs to application developers to program against.

      And speaking of application developers, I'd guess that it's approximately one fuckload easier to get an Dual_EC_DRBG-compliant product to market if it uses the (already-certified) Dual_EC_DRBG code in the OS, than if each developer were required to seek such certification independently, which is clearly a competitive advantage for Windows over other operating systems if Dual_EC_DRBG support is a factor (for the NSA, or for anyone else that needs it for whatever reason).

    26. Re:Given the known problems of Dual_EC_DRBG by VertigoAce · · Score: 2, Informative

      No it's not open source, but any company with 1500+ SA seats of Windows gets access to the source at no additional cost for debugging and security/privacy audit purposes. State and local governments appear to have access provided that they are in certain geographical areas (it's not entirely clear, but it looks like the 1500+ seat requirement doesn't apply). National governments also get zero-cost read-only access to the source code for Windows and Office.

    27. Re:Given the known problems of Dual_EC_DRBG by NothingMore · · Score: 1

      A few governments will know where this code is used at in vista sp1 (microsoft does allow select country's to view the source). Not only do we have to worry about the US government using a backdoor we have to worry about anyone who has there hands on the source using it as well.

    28. Re:Given the known problems of Dual_EC_DRBG by VeteranNoob · · Score: 1

      ... if there was a backdoor, governments would not need to get warrants for inserting hardware keyloggers or custom malware on systems to access system information. Governments both in the US and elsewhere do this, which suggests that no backdoor is available.

      I wouldn't dismiss the possibility solely on this reasoning. For all we know, the government will not require warrants for blanket digital eavesdropping in the near future. It has already happened with international calls, requiring only a presidential "signing statement." Now I don't want this any more than the next guy. Unfortunately neither I or the next guy is feeding the politicians' pockets (not to say politicians are even required with these obviously undemocratic signing statements).

      I generally agree with your post and wouldn't quite strike the inclusion of the algorithm up to nefarious reasons. But I'm not convinced that there is no backdoor.

      --
      Adapt, adopt, or get out of the way!
    29. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0
      I don't have to prove it.

      And I don't have to prove you show up at my house every morning to kiss my ass.

      But it's true.

    30. Re:Given the known problems of Dual_EC_DRBG by gnasher719 · · Score: 1

      A few governments will know where this code is used at in vista sp1 (microsoft does allow select country's to view the source). Not only do we have to worry about the US government using a backdoor we have to worry about anyone who has there hands on the source using it as well. If you had read, and possibly understood, the previous article about this, then you would know that

      1. Nobody knows for sure that a backdoor exists. The backdoor _could_ have been created at the time the constants in the algorithm were defined. If it didn't happen back then, then no backdoor exists and no backdoor can be created anymore.

      2. The source code doesn't give any information whether the backdoor exists, and if it exists, how it works. 3. If the backdoor exists, then it seems most likely that the US government has it, and nobody else.
    31. Re:Given the known problems of Dual_EC_DRBG by Burz · · Score: 2, Insightful

      I have been working with the cryptographers at Microsoft for some time and I have been working in crypto related areas for > 20 years. A dubious distinction. Microsoft is almost criminally negligent when it comes to encryption and most other security issues. Between that and your obvious conflict of interest here, why should anyone believe you?

      I'll heed Schneier's concerns over your schilling any day. I'd set his words to music before accepting that soiled "expert opinion" you're pushing, because at the very least you are deranged for smearing those concerns as "paranoid" against the backdrop of massive government spying we see today.
    32. Re:Given the known problems of Dual_EC_DRBG by Kidbro · · Score: 1

      I don't have to prove it. Not only that, but you wouldn't believe me if even if the code was released - after all, how do you know that the code corresponds to the actual binary?
      You don't need to trust the binary if you have the source. You compile your own, and use that one. I know we're going off on a tangent here, but this is exactly why closed source software can't be trusted when open source software can.

      I'm not arguing any other point you make though.

    33. Re:Given the known problems of Dual_EC_DRBG by xocp · · Score: 1

      "Never ascribe to malice, that which can be explained by incompetence." - Napoleon Bonaparte

    34. Re:Given the known problems of Dual_EC_DRBG by secPM_MS · · Score: 2, Interesting
      That is not good enough. The attack can be in the compiler or other tools in the build environment. Such attacks have been demonstrated. That is why I mentioned the CC issue. The evaluation laboratories have access to the source, have competent security staff, and are "trusted" by both the customer and the manufacturer to accurately represent what they have found.

      For all the talk about closed source, a rather large number of customers, including numerous governments, has read access to the Windows Source code. Don't assume that only MS employees examine it. The number is far broader than is generally supposed.

    35. Re:Given the known problems of Dual_EC_DRBG by ConceptJunkie · · Score: 1

      Bearing in mind that the bill to pay off all the people involved in the moon landings hoax is decreasing every year now they've started to die off, it's likely that the US Dept of Coverups has plenty of budget to spare for this kind of thing now.

      Clearly you're forgetting about the bill to pay off all the people involved in the 9/11 cover-ups, which is much bigger than the Apollo cover-ups ever required.

      --
      You are in a maze of twisty little passages, all alike.
    36. Re:Given the known problems of Dual_EC_DRBG by secPM_MS · · Score: 1
      In the early days, MS focused upon features more than security, as that is what the customers responded to. About the same as the current "Web 2.0", which is essentially untrustworthy by design.

      Once security problems became a customer concern, MS moved on it. Indeed, MS is being subjected to considerable criticsm in Vista and Server 2008 for overinvesting in security with respect to neat new features. There is always the feature / security tradeoff. You can configure your system for security, minimizing the attack surface at the cost of reduced functionality. Consumers want the neat features. I run in secure mode and accept the reduced functionality.

      The Secure Development Lifecycle process that was introduced a few years ago has a cryptographic portion that requires crypto usage to conform to reasonable standards, which are adjusted in light of the current crypto state of the art. This has allowed the cryptographers to clean up usage of crypto in MS products.

    37. Re:Given the known problems of Dual_EC_DRBG by a_n_d_e_r_s · · Score: 1

      Well everybody - except Microsoft of course - knows that the GUI don't have to be in the kernel.

      What should be in the kernel is the code for handling the hardware and give those resources to programs in a secure way. Nothing more nothing less.

      --
      Just saying it like it are.
    38. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0
      As for backdoors, anybody who is paranoid about this issue will ignore or disbelieve me when I say that there is no backdoor that I am aware of.

      Lessee -- your opinion -- Bruce Schneier's opinion.

      OK, after careful consideration, I've decided Schneier's more likely on top of the facts.

    39. Re:Given the known problems of Dual_EC_DRBG by pizpot · · Score: 1

      ...Governments both in the US and elsewhere do this, which suggests that no backdoor is available.

      If you ignore reality then yeah. Try thinking "spy first, warrent later" and you will be in the right league. Trolling has become too important to give up.

    40. Re:Given the known problems of Dual_EC_DRBG by pantherace · · Score: 1

      People should read some history: focus specifically on Windows and the NSA.

      Hint: SP5

    41. Re:Given the known problems of Dual_EC_DRBG by terrahertz · · Score: 1

      I don't have to prove it. Not only that, but you wouldn't believe me if even if the code was released - after all, how do you know that the code corresponds to the actual binary? There's a funny thing about open source software: nobody cares what's in any binary other than the one they compiled. Strange concept, eh?
      --
      Slashdot? Oh, I just read it for the articles.
    42. Re:Given the known problems of Dual_EC_DRBG by Burz · · Score: 2, Interesting

      Indeed, MS is being subjected to considerable criticsm in Vista and Server 2008 for overinvesting in security with respect to neat new features. Certainly if you count the performance-killing DRM features as "security". Most of us here are talking about the users' security, not Hollywood's.

      Of course, the presence of DRM itself throws their crypto incompetence into high relief.

      The Secure Development Lifecycle process that was introduced a few years ago has a cryptographic portion that requires crypto usage to conform to reasonable standards... I know of one MS systems architect who thinks that SSL is broken (but of course, no evidence is ever forthcoming). They are FUD-spewing charlatans, and you believe in them.

      Do tell us more about Microsoft's reasonable "standards". Is it anything like what they are doing with kerberos or OOXML?
    43. Re:Given the known problems of Dual_EC_DRBG by waveman · · Score: 1

      > Other governments are not going to be willing to buy a system with a NSA backdoor.

      If something has *already* happened, then it is possible that it *could* happen. After WWII, the US sold copies of the german crypto machines to governments all over the world and proceeded to read the "encrypted" traffic. This machine, the enigma machine, had of course been broken.

      Never underestimate stupidity, especially of governments.

      Maybe secPM is not as much of an expert as he claims to be. Or maybe he is trying to mislead us.

    44. Re:Given the known problems of Dual_EC_DRBG by SpaceLifeForm · · Score: 2, Informative

      They have no way of knowing that the source the can review
      actually matches any binaries provided via Windows Update.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    45. Re:Given the known problems of Dual_EC_DRBG by CodeBuster · · Score: 1

      I think the grandparent has seen one too many episodes of the X-Files. Perhaps we should ask him whether the moon landings were a hoax as well? Or then again, perhaps not, we might deserve the answer just for asking.

    46. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0

      after all, how do you know that the code corresponds to the actual binary?
      Well you see people who have experience with source code can do this amazing thing called COMPILING it.

    47. Re:Given the known problems of Dual_EC_DRBG by rtechie · · Score: 1

      Prove it. Oh, that's right, you can't because you don't have the source code. Having the source code wouldn't help, because you couldn't be sure the binary you have wasn't modified. You could compile it yourself, but that's pretty impractical.

      Of course, you could just do a memory dump or run it through a debugger. Hell, you can go in, DELETE the code, and then see if Windows still tries to use it.

      And other governments have replaced Windows with custom Linux distros due to the potential of this very problem. This is a fact that cannot be denied. I'll deny it. Name one. China specifically DID NOT develop Red Flag Linux due to security issues, but more because they wanted to develop their own version of Linux catering to the Chinese market. The Chinese government makes extensive use of Microsoft technology.

    48. Re:Given the known problems of Dual_EC_DRBG by caluml · · Score: 1

      Dual_EC_DRBG is my password :( And now I find it all over the Intarwebs.

    49. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0

      after all, how do you know that the code corresponds to the actual binary? um, because when I compile it, I get an equivalent binary that can be compared to the one in Windows to see if you provided the same source code as was compiled into the released version of Windows.

      This has been another episode of simple answers to simple questions.
    50. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0
      Not only that, but you wouldn't believe me if even if the code was released - after all, how do you know that the code corresponds to the actual binary?

      If you have to ask that question, your >20 years of work in "crypto-related areas" has been for nought.

    51. Re:Given the known problems of Dual_EC_DRBG by Pie-rate · · Score: 1

      How do you know you can trust your compiler binary?!?!?!?

    52. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0

      Oh yeah? Well, I write my own assembler directly in machine code. I then write my own C/C++ compiler/linker directly in assembly. I'm hardcore! Grrr!

    53. Re:Given the known problems of Dual_EC_DRBG by Your.Master · · Score: 1

      Huh? Your post doesn't make any argument against anybody. Unless...Is this random number generator in the kernel???

      I don't see it in TFA, though I admit I didn't look too closely.

    54. Re:Given the known problems of Dual_EC_DRBG by jayp00001 · · Score: 1

      Well everybody - except Microsoft of course - knows that the GUI don't have to be in the kernel.

      What should be in the kernel is the code for handling the hardware and give those resources to programs in a secure way. Nothing more nothing less.

      offtopic but...

      This is the same argument that's been going on for the last, what, 30 years or so. Should the kernel provided a minumum of features and let the programmer have at it or should it provide a full set of features. I would think that by now folks would have realized that the market has declared the latter to be the design of choice.
    55. Re:Given the known problems of Dual_EC_DRBG by teg · · Score: 1

      If you had a backdoor which allows you to access remote computers anywhere would you
      a) Tell everyone that you can do it
      b) Use some dummy keyloggers and malware to suggests that you can't do it

      c) use it in a very limited manner, making sure you the obtained information is not disclosed directly in any way - just used to keep tabs on e.g. foreign nations or to point discreetly at other sources of information
    56. Re:Given the known problems of Dual_EC_DRBG by wirelessbuzzers · · Score: 2, Insightful

      As for backdoors, anybody who is paranoid about this issue will ignore or disbelieve me when I say that there is no backdoor that I am aware of. The Common Criterial evaluators look for such issues and submit issues for fixing if and when they find them. I don't think you understand the issue here. Nobody is claiming that this represents a backdoor in Microsoft's code. The issue is that the approved parameters for the algorithm Dual_EC_DRBG could be a back door.

      Essentially, Dual_EC_DRBG is a public-key encryption algorithm* disguised as a random number generator. The NIST parameters are a public key. The generator has some painfully-generated random internal state. It steps by encrypting* using the internal state as a parameter. It outputs the ciphertext*. It sets the plaintext* as the next state. To recover the next state, or even to distinguish the next state from random*, is equivalent to breaking the encryption algorithm. EC-DH is a pretty well-respected algorithm, so probably nobody is going to break it. This would imply that the DRBG is secure, i.e. nobody else can distinguish it from actual random numbers.

      *Not quite accurate, but a full explanation would be an automatic TL;DR.

      Unless, of course, the government (or someone else) has the private key (the "back door") corresponding to that public key. They probably don't, but they almost certainly can't prove it. Since Dual_EC_DRBG is slow, only paranoid people would recommend it anyway. Because of the potential back door, no cryptographer thinks you should use it, but Microsoft has included it anyway. This is probably to say they meet some government standard, but it's causing a tempest in a teapot, possibly because it reminds people of the whole _NSAKEY mess.

      And yes, I am a cryptographer.
      --
      I hereby place the above post in the public domain.
    57. Re:Given the known problems of Dual_EC_DRBG by Captain+Segfault · · Score: 1

      I wondered btw. why my 8 years old firewall supports AES encryption (for VPN) with 2048 bits strength but no currently available products supports more than 256 bits.

      Because 256 bit AES is believed secure. Even 128 bit AES is secure unless we find some fairly major attacks -- 2**128 is HUGE. 2**256 is 2**128 times larger than *that*. If you turned the entire planet into a gigantic (conventional) computer you could break 128 bit AES but not 256 bit AES. 256 bit AES would likely be unfeasible if you had the power of a large *galaxy*. A small city isn't going to cut it.

      A quantum computer might do it, but if one would be much help then a 2048 bit AES key would be not much harder than a 256 bit one.

      Thus, you don't see current products with more than 256 bit AES. If you see someone pushing larger key sizes for AES right now I'd be reluctant to trust them -- they probably do not know what they're talking about!

    58. Re:Given the known problems of Dual_EC_DRBG by hughk · · Score: 1

      It takes a very small patch to change a secure system into an insecure one, or even worse, selectively insecure. Any component that is implemented at a higher access level can potentially compromise the system as a whole. This is true for any system, whether Windows, Linux. With a vendor built system there are fewer eyes and even though QA may be good, it can never check every possible item. As for independent testing labs, well we know they certify a given baseline of a system, that is all. Do they then verify every patch?

      We know that Microsoft remains weak on QA. They are weak on basic engineering (it is a business decision of Microsoft as good engineering is very expensive). Having worked at companies with a strong process (i.e., real time process control), proper project and quality management costs time and resources. In the case of would not be difficult to ship a clean system and then to ship patches that interact with the baseline to compromise the security gates.

      The question here isn't about open source or the open source QA process, but given the number of eyes on the system, the number of people compiling from source (and with different compiler versions) it does appear that problems get spotted sooner.

      --
      See my journal, I write things there
    59. Re:Given the known problems of Dual_EC_DRBG by morgan_greywolf · · Score: 1

      So how's the job at Microsoft going, anyways?

      You'll know that Dual_EC_DRBG is not yet a FIPS standard, and even if NSA is pushing it, that doesn't mean it's going to be.

      So how much do you get paid to astroturf?

    60. Re:Given the known problems of Dual_EC_DRBG by SEMW · · Score: 1

      Who even says that at an RNG has to be at the OS level? ... As another poster said, where in the OS is this used? Presumably, at the many places where encryption exists at the OS level. NTFS file encryption (EFS), Bitlocker drive encryption... Hell, even Readyboost shares (i.e. using flash drives as a superfetch cache) are encrypted in case someone steals the flash drive. Good encryption isa pretty important ability for a modern secure operating system.
      --
      What's purple and commutes? An Abelian grape.
    61. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0

      Prove it. Oh, that's right, you can't because you don't have the source code. Unless maybe you're astroturfing. Even then you'd be under an NDA anyhow. That is easy use the RNG implementations in Vista. This is easily done using BCrypt, which is nicely documented on MSDN. Try out the default PRNG, it might be from SP 800-90 but it is not the EC DRBG. MS has no reason to lie with regards to this. It was probably implemented for the NSA to use in their systems, since Suite B is far more restricted then FIPS 140 (or any other information security standard).

      And other governments have replaced Windows with custom Linux distros due to the potential of this very problem. This is a fact that cannot be denied. Are you sure this was the reason they switched? Do you work for every government that has performed such a switch? Exactly how many world governments have moved en masse away from Windows? You think Linux is that much more secure, why because it uses OpenSSL? Remember OpenSSL had one FIPS 140-2 cert revoked and has had their RNG de-listed as approved on their current cert because it is non-compliant. Oh, and there was the Bleichenbacher signature forgery that it was vulnerable to. Yeah, OpenSSL is real secure.

      Seriously, everyone is enjoying the jump on MS about this, but they ARE NOT the only people who have implemented this RNG.
    62. Re:Given the known problems of Dual_EC_DRBG by Anonymous Coward · · Score: 0

      I am not a security expert, so please correct me if I am wrong. I think Bruce Schneiers point is that unless you have personally created the constants describing the elliptic curve then you also don't know if there is a skeleton key to the ECC generator.

    63. Re:Given the known problems of Dual_EC_DRBG by Jonner · · Score: 1

      Schneier seems to be saying that the backdoor definitely exists, but he doesn't know who, if anyone, has the key to it. Even if no one currently has the key, if it were somehow discovered, everyone using the standard would be wide open.

    64. Re:Given the known problems of Dual_EC_DRBG by jc42 · · Score: 1

      They have no way of knowing that the source the can review actually matches any binaries provided via Windows Update.

      This is one of the standard points in any meaningful security guidelines.

      Brief summary: You don't run any binaries from anyone else. If you don't have the source, you don't run the software. You have people that can study and analyze the source. And you compile it all yourself. With a compiler from a different vendor.

      Then there's Ken Thompson's famous (in some circles) Reflections on Trusting Trust article, which is required reading for anyone with serious security interests. It gives you some ideas about how to deal with the compiler itself. Actually, it mainly gives you some good questions, which you might want to try answering, just for the experience of dealing with an infinite regress of trust.

      Most of Microsoft's customers will simply use the binary code. In an organization that does this, there's no point whatsoever in discussing the possibility of a backdoor. The management has already demonstrated that they don't care, because their security is only for show.

      (Note that this isn't Microsoft bashing. The same applies to any system, including one that's open source. If you run a binary from an outside source, you have no idea what's in it, and you have to meaningful security. People have on several occasions managed to sneak backdoors into releases of linux and other open-source systems. Granted, they might have been caught quickly and fixed, but this tells you nothing about that binary that you're downloading right now.)

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    65. Re:Given the known problems of Dual_EC_DRBG by mr_mischief · · Score: 1

      The kernel doesn't have to handle anything but scheduling and loading device drivers and the application programmer can still have plenty of features. There's this little set of things called shared libraries, and another called user-space device drivers. The OS being a microkernel or a monolithic kernel has little to nothing to do with the OS offering a full set of features. The kernel, after all, is not the whole OS.

    66. Re:Given the known problems of Dual_EC_DRBG by secPM_MS · · Score: 1

      Understood. One of the cryptographers who published the attack against the ECC RNG was a MS cryptographer. As I said, the default RNG is NOT the ECC RNG, which was included because various governments wanted it.

    67. Re:Given the known problems of Dual_EC_DRBG by adolf · · Score: 1

      Yep. But I wasn't talking about kernels; I was talking about operating systems.

      The kernel is not the OS, but just one part of it.

      If you'd like to talk about kernels instead of operating systems, please allow me to point out that all Unix kernels employ some form of software RNG, in the forms of /dev/random and /dev/urandom.

      Furthermore, after very careful consideration, I feel that in the context of this particular discussion (Microsoft's inclusion of a particular RNG in the SP1 release of their Vista operating system) your point is rather void.

      Thank you for your time.

  6. Well... by $RANDOMLUSER · · Score: 1, Redundant

    I worry more about the 0-day backdoors in Vista than I do about the NSA backdoors.

    --
    No folly is more costly than the folly of intolerant idealism. - Winston Churchill
  7. n-th sensationalist headline of the day by leonbloy · · Score: 1

    Boy, this is getting tiring.

    1. Re:n-th sensationalist headline of the day by syntaxeater · · Score: 1

      I'd have to agree. It's starting to make me wish there was more "top 10 of 2007" articles out there.

  8. Concerned About Security... by Nom+du+Keyboard · · Score: 4, Funny

    You're concerned about security, and you're using WINDOWS VISTA???

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
    1. Re:Concerned About Security... by rucs_hack · · Score: 2, Funny

      You're concerned about security, and you're using WINDOWS VISTA???

      Thats because is is an hero..

    2. Re:Concerned About Security... by $RANDOMLUSER · · Score: 1

      Well yeah. It IS the "Most Secure Windows" EVAR. Says so right on the box.

      --
      No folly is more costly than the folly of intolerant idealism. - Winston Churchill
    3. Re:Concerned About Security... by Aqualung812 · · Score: 1
      Assuming the poster is being forced to use Windows, then yeah, DUH!

      There are many features in Vista (such as Bitlocker) that are great security improvements over XP. Yes, Vista is a slow, buggy P.O.S. compared to XP, but it is MORE secure than XP.

      --
      Grammer Nazis - I mod you "troll" unless you actually add something on-topic. Yes, I know I have mispellings in my sig.
    4. Re:Concerned About Security... by ConceptJunkie · · Score: 1

      Well yeah. It IS the "Most Secure Windows" EVAR. Says so right on the box.

      And you know what? It's actually true.

      But the "most secure Windows ever" is kind of like the "most stylish haircut Bill Gates has ever had" or "most evolved species that Steve Ballmer resembles".

      --
      You are in a maze of twisty little passages, all alike.
    5. Re:Concerned About Security... by Anonymous Coward · · Score: 0

      With wireless keyboard no doubt.

  9. What does Microsoft say about it? by Anonymous Coward · · Score: 0

    Are they touting is as secure? Do they mention the NSA backdoor? Do they have a response to it?

  10. Much Ado About Nothing by Anonymous Coward · · Score: 0

    Some US government agencies REQUIRE the ability to use this PRNG algorithm, so anyone who wants to sell a product to those agencies (IBM? RedHat? Sun?) is going to have to provide that algorithm.

    And, this algorithm is NOT the default.

    So... ??? This article is simple FUD.

    1. Re:Much Ado About Nothing by Kadin2048 · · Score: 4, Insightful

      Agreed. The only interesting thing about this whole story is that the NSA apparently reviewed the PRNG function and rubber-stamped it, missing the critical vulnerability. Since the vulnerability really isn't that good of a backdoor, and doesn't seem to have been all that subtle, I think this is far more likely to be incompetence rather than malice on their part.

      As an American, that doesn't make me feel a whole lot better -- in some ways, I'd really like to have the secret agencies of so many spy movies rather than the massive bureaucratic pile that I know exists in reality -- but disappointment in government is something I've gotten used to. You don't last long in Washington without it.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    2. Re:Much Ado About Nothing by ashridah · · Score: 0

      Okay, have you actually studied cryptography at even a basic level?

      It's basically impossible (read, an NP-hard problem at least) to *prove* that a particular cryptosystem is unbreakable. If it's an obvious flaw, then sure, give whoever missed it a thorough kicking, but in my experience, 'obvious' is just another form of scapegoating, and is just a way of passing the buck from the guy who cut testing short, to the mathematician who did the testing.

      The reality is, cryptography requires years of research and peer review to be reasonably sure that it's right. Look at all of the cyphers in the past that have suddenly been broken after N years of production use. Now also consider that government standards cost hundreds of thousands of dollars to create, and probably as much again to update. Then you need to consider that if you want to play in that market, you need to adhere to those standards, no matter how boneheaded. And since they cost so much to make and change, they don't change often, so they lag behind cryptographic science.

      I'm pretty sure you can find this particular random number generator in other places, if you really try.

      ash

    3. Re:Much Ado About Nothing by Gideon+Fubar · · Score: 1

      in some ways, I'd really like to have the secret agencies of so many spy movies rather than the massive bureaucratic pile that I know exists in reality

      Have you actually paid attention to the collateral damage in your average Bond movie? I think a mass of bureaucrats are a reasonable alternative to that..

      --
      http://www.xkcd.com/354/
    4. Re:Much Ado About Nothing by wirelessbuzzers · · Score: 1

      Okay, have you actually studied cryptography at even a basic level? Have you? Because I have.

      It's basically impossible (read, an NP-hard problem at least) to *prove* that a particular cryptosystem is unbreakable. It's not NP-hard, it's much worse. It (almost always) requires proving that P != NP. There's a million-dollar bounty on that problem.

      For block ciphers and hashes, you instead prove that the algorithm is resistant to large, known families of attacks. You justify its design. You get rid of "magic constants" which could be back doors. Then you and a hundred of your cryptographer friends try to break it for a long time. If they can't break it, you hope it's secure.

      For other systems, you prove that your system is secure assuming that a certain problem is hard. For instance, you can prove that a certain block-cipher-based PRNG is secure if the underlying block cipher is secure. This is practically a requirement these days: people generally won't use your algorithm unless you "prove" that it's secure when correctly implemented. ("Prove" is in quotes because the hard problem might turn out not to be hard, or the "proof" might be wrong, or your key might be too small, or P might equal NP, etc.)

      The problem with Dual_EC_DRBG is that it's (mostly) secure, under the assumption that the (well-respected) "Elliptic Curve Decision Diffie-Hellman Problem" is hard, for randomly-chosen parameters. For any set of parameters (P,Q), there's a back door, but the back door is hard to find. This is built in to the design of the system. Now, NIST claims that they generated their parameters randomly, and that nobody has the key to the back door. But they can't prove it. They (or the NSA, or someone else) might have generated the parameters maliciously, so that they know the back-door key. There's pretty much no way to know.

      The reality is, cryptography requires years of research and peer review to be reasonably sure that it's right. Look at all of the cyphers in the past that have suddenly been broken after N years of production use. Now also consider that government standards cost hundreds of thousands of dollars to create, and probably as much again to update. This is a relatively new spec. Nobody's using it, because of the threat of a back door, because of a different minor flaw, because it's slow, and because there are older specs that don't have these problems. It would be relatively easy to change the parameters to something where NIST can "prove" (as above) that they don't have the back-door key. But they haven't, which makes people suspicious.

      I'm pretty sure you can find this particular random number generator in other places, if you really try. I'm pretty sure you can't. It's very slow. It's not something a non-cryptographer would think of. And if you came up with it anyway, you'd generate the parameters yourself, rather than trusting some other person to generate them for you.
      --
      I hereby place the above post in the public domain.
  11. it's true by circletimessquare · · Score: 5, Funny

    i seeded the dual_EC-DRBG with the following ASCII strings the and got the following output in ASCII:

    missionaccomplished -> LOL

    waterboard -> buckshottotheface

    osamabinladen -> loofahnotfalafel

    iraq -> vietnam

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  12. No surprise here by Anonymous Coward · · Score: 2, Interesting

    No surprise, really. After all, Microsoft did this a long time ago (remember the whole "NSA KEY" fiasco?)

    http://en.wikipedia.org/wiki/NSAKEY

  13. Is this "feature" back-ported to XP SP3, too? by denis-The-menace · · Score: 2, Interesting

    Is this "feature" back-ported to XP SP3, too?
    SP3 is supposed to have some of Vista's most useful features as well as all previous bug fixes.
    Would a shame to ruin a good service pack that speeds up XP by 10%.

    --
    Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    1. Re:Is this "feature" back-ported to XP SP3, too? by Anonymous Coward · · Score: 0

      Actually.. I believe it is. They updated the Crypto API for XP SP3, so it probably adds the new algorithms including this one.

    2. Re:Is this "feature" back-ported to XP SP3, too? by ATucker · · Score: 1

      XPSP3 just adds support for SHA2 to both the core crypto and certificate validation APIs. It does not add support for ECC or for the ECC PRNG. The RNG on XPSP3 is virtually unchanged from XPSP2.

      --
      /* Andrew */
    3. Re:Is this "feature" back-ported to XP SP3, too? by Anonymous Coward · · Score: 0

      Andrew muthalovin' Tucker! What up dawg?! The Tuckmeister! Tucklicious! Tuck Central baby! Booooo-yah!

      You rock man! You ROCK!

  14. Big Deal. by Anonymous Coward · · Score: 0

    I implemented this on my Linux box. Does this mean that all of Linux now has a back door too?
    Slashdots anti-Microsoft alarmist bullshit is so boring.

  15. Clever! by spun · · Score: 5, Insightful

    I see what you did there. You implied that anyone who criticizes the US or Vista is a paranoid loony. Now why would you do that? Do you just assume that people will criticize the US? Is the US that worthy of criticism that you have to defend it preemptively? I know that's a popular tactic these days, but is it entirely necessary? Nice how you posted AC, too. You sir are an all-around class act.

    --
    - None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
    1. Re:Clever! by Bill,+Shooter+of+Bul · · Score: 2, Insightful

      No, he said there are some paranoid people here "who rant about how U.S. is a fascist state and how Vista is the new 'evil'"

      Thats true. That does not imply what that any criticism is paranoid. It is possible for a subject to be criticized legitimately by some people, and delusionaly by others. He's referring to those who always lose arguments due to godwin's law.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    2. Re:Clever! by spun · · Score: 1

      Ah, well, that's completely true. Nutters on all sides of any issue, eh?

      --
      - None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
  16. Correct me if I'm wrong but... by KillzoneNET · · Score: 1

    ... can't they just include their own list of secret numbers in order for the generator to be semi-secure? The NSA has the numbers that generate the random numbers in the base code but even they say to make your own reference numbers if you are to use the code. So if Microsoft were to ultimately use the numbers the numbers would probably end up being both random and not known to anyone in the development team if they so wanted.

  17. Why... by Basilius · · Score: 3, Funny

    ...does every article about Vista make me less likely to ever use it? Aren't things like this supposed to _improve_ with time?

    1. Re:Why... by plague3106 · · Score: 1

      Why would this matter to you at all, if you never enable it?

      More to the point, why do /.ers continually say MS can't do anything right, then don't think at all MS could have screwed up the algorthm or backdoor?

    2. Re:Why... by Teisei · · Score: 1

      If it's Microsoft, no.

    3. Re:Why... by Gadgetfreak · · Score: 1

      because this is Slashdot! Did you really expect a "Vista is GREAT" article? Not that they exist.

      --
      "No fair, you changed the outcome by measuring it!" - Professor Hubert J. Farnsworth
    4. Re:Why... by Deanalator · · Score: 1

      sensationalist pseudo-journalism?

      If you want an informed opinion about vista, slashdot is not the place to get it. Microsoft was in a tough place for this release. The more mandatory access controls they implemented, the more it broke legacy code. In the end they decided security was more important than backwards compatibility in most cases.

      It's not perfect, and I'm not switching away from linux anytime soon, but at least microsoft is trying.

    5. Re:Why... by Anonymous Coward · · Score: 0

      I agree. I always say Microsoft is trying.

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

      Well, you gotta admit, Linux is looking better and better...

  18. More important question by Thelasko · · Score: 1
    The posted Microsoft website states:

    The Dual Elliptical Curve (Dual EC) PRNG from SP 800-90 is also available for customers who prefer to use it. How does Joe User know if he is using it or not? Is it a setting in the control panel? Why would anybody want to use it?
    --
    One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
    1. Re:More important question by Anonymous Coward · · Score: 0

      How does Joe User know if he is using it or not? Is it a setting in the control panel? Why would anybody want to use it? Easy, Joe User will just look through source code for Windows and any other application he uses to see which RNG is being used.
      Oh... wait...
  19. OK, this is just stupid. by rrkap · · Score: 4, Insightful

    So, let's review:

    1. Government introduces a new cryptography standard (which it will presumably require for some applications) that requires that systems provide a choice of 4 random number generators, one of which MAY have a flaw.
    2. Manufacturers implement the new standard.
    3. Grand conspiracy!!!

    Come on, could it just possibly be that Microsoft wants to be able to claim to be NIST 800-90 compliant for customers who want that kind of thing and that the NSA likes the idea of there being a variety of random number generators available? The only way that making this function available is a risk is the NSA also has control of the application and can force it to call this random number generator without properly seeding it. If they have that level of control, they have enough control to do whatever else they want in a much more direct way.

    --
    I like my beverages with warning labels!
    1. Re:OK, this is just stupid. by reikoshea · · Score: 1

      Why use constants if they want it to be the standard. That just doesnt make sense. There will always be a key, but why have a back door key available as well.

      It just makes no sense. I think the 'fear mongering' is justified cause this is just a stupid practice to implement.

    2. Re:OK, this is just stupid. by SL+Baur · · Score: 1

      Why use constants if they want it to be the standard. That just doesnt make sense. Actually, it makes a whole lot of sense. Consider the history of the DES. When it was first being proposed, the NSA suggested some changes to the internal constants used. It wasn't until over a decdade later that it was discovered that the particular choice of constants made DES resistant against a certain block cipher cracking technique (the Wiki page is at least accurate on this account - http://en.wikipedia.org/wiki/Data_Encryption_Standard) that was widely unknown at the time the standard was made.

      Some of the suspicions about hidden weaknesses in the S-boxes were allayed in 1990, with the independent discovery and open publication by Eli Biham and Adi Shamir of differential cryptanalysis, a general method for breaking block ciphers. The S-boxes of DES were much more resistant to the attack than if they had been chosen at random, strongly suggesting that IBM knew about the technique back in the 1970s. This was indeed the case -- in 1994, Don Coppersmith published the original design criteria for the S-boxes. According to Steven Levy, IBM Watson researchers discovered differential cryptanalytic attacks in 1974 and were asked by the NSA to keep the technique secret.
    3. Re:OK, this is just stupid. by letsief · · Score: 2, Interesting

      You're actually missing one of the funny parts of the review. Neils Ferguson, a researcher at Microsoft, is one of the people that found the potential security flaw. It was probably Microsoft's decision to implement the RBG that caused him to start looking at it.

    4. Re:OK, this is just stupid. by Anonymous Coward · · Score: 0

      one of which MAY have a flaw.
      No, it DOES have a flaw. It's just the authors MAY have an exploit.
    5. Re:OK, this is just stupid. by Anonymous Coward · · Score: 0

      1. Government produces a faulty algorithm, possibly by incompetence, or possibly with malice.

      2. Vendor implements said KNOWN DEFECTIVE algorithm.

      Why on earth would anyone deliberately cripple the security with a know defective algorithm? This is not the "good" old days of ActiveX, where any moronic idea would be implemented. Microsoft actually cares about their *image* when it comes to security, and tries their best to look like they are trying to improve. They have worked hard on this, and they are not going to just let that image be washed away by *appearing* to implementing a backdoor for the government, unless forced by said government to do so (because the back door is real).

    6. Re:OK, this is just stupid. by rrkap · · Score: 1

      You do realize that this isn't the standard random number generator, but one of several available random number generators that you can use for specific purposes (such as, you know, meeting a customer specification). As for implementing a "KNOWN DEFECTIVE" algorithm, there are plenty of them. Think of, for example, WEP.

      --
      I like my beverages with warning labels!
  20. Trust Us, We're From the Government by Doc+Ruby · · Score: 2, Funny

    What kind of commie doesn't just trust the NSA? I mean, we've got a FISA to protect us from the government and from corporations cooperating with rogue regimes, right?

    --

    --
    make install -not war

  21. Block filtration by category by Anonymous Coward · · Score: 0

    I assume by not putting in any category, the editors get to bypass a users filtration by preferences selections.

    1. Re:Block filtration by category by Anonymous Coward · · Score: 0

      It's a Slashdot back door!

  22. Re:Conspiracy theorists come forth! Now it the tim by hey! · · Score: 4, Insightful

    I disagree.

    This has absolutely nothing to do with open or closed source. A completely open source random number generator would have precisely the same vulnerability, because the problem isn't potential skulduggery by the vendor, it's potential skulduggery by the people who designed the standard.

    What Microsoft has done is to implement a questionable standard. It makes no sense in this case to blame them for its shortcomings, especially since developers have alternative standards they can use.

    Now when it comes to application software using a random number generator, then there actually is a closed/open source argument to be made. Do you know which random number generator is used by the software you use? With closed source, almost certainly not. With open source, programmers can undo the choice of the dodgy elliptic curve RNG and replace it with a more solid, equally standards compliance alternative. And get a speed boost too. You also know that you might not want to trust the source for your software if they use the inferior algorithm.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  23. Use the output in reverse. by Anonymous Coward · · Score: 0

    My understanding is that you need 32 bytes of consecutive output.

    Why not populate a buffer with the PRNG output.
    Create an index to the end of the buffer. (Assuming an array)
    Then.

    Use as output the byte at this index value.
    Decrement the index by one.
    Subtract the byte value at the index, from the index value.
    Use the byte value at the index as the second output value.

    Keep doing this stepping backwards through the buffer in this manner, when you role off the start of the buffer repopulate the buffer with new random data.
    Set the index value for the repopulated buffer to the buffers length minus the absolute value of the currently negative index.
    Or simply add the buffers length the index.

    Have fun.

    1. Re:Use the output in reverse. by Anonymous Coward · · Score: 0

      Your algorithm is trivially reversible and as such provides no more cryptographic obfuscation than the original.

    2. Re:Use the output in reverse. by Anonymous Coward · · Score: 0

      No its not, the attacker does not have the whole content of the buffers only the odd byte.

      You need consecutive bytes to attack the prng.

      Try thinking about it again..

      Have fun.

  24. Secret Back door code is pretty easy!! by spineboy · · Score: 5, Funny

    Maybe the NSA could have thought a little harder at entering a back door code. Secret sources have revealed the NSA back door code to be.

    up, up, down, down, left, right, left, right, B, A

    --
    ..........FULL STOP.
    1. Re:Secret Back door code is pretty easy!! by nottoogeeky · · Score: 1

      Was that not the sonic the hedgehog or mortal kombat cheat on the megadrive?

    2. Re:Secret Back door code is pretty easy!! by aesiamun · · Score: 2, Informative

      Contra on NES.

      But i think other konami games used it as well.

    3. Re:Secret Back door code is pretty easy!! by krack · · Score: 2, Informative

      It is the Konami Code, made famous by its use in Contra. It was used in many other games and has since passed into gamer lore.

      (not a shill, just love thier stuff) http://www.pennyarcademerch.com/pat070051.html
      and
      http://en.wikipedia.org/wiki/Konami_Code

      --
      Just because you are not paranoid does not mean they are not out to get you.
    4. Re:Secret Back door code is pretty easy!! by cromar · · Score: 1

      Just be careful to use the L & R buttons when engaging the mega-powerup. If you use the normal left and right thrust controls, the spaceship will explode.

    5. Re:Secret Back door code is pretty easy!! by Your.Master · · Score: 1

      I believe the Sonic one was:

      Up Down Left Right A B B A A+C+Start

    6. Re:Secret Back door code is pretty easy!! by r_jensen11 · · Score: 2, Funny

      Soo, the NSA has unlimited lives?

    7. Re:Secret Back door code is pretty easy!! by Quato · · Score: 0

      It's known at the Konami Code... there's even a wiki. http://en.wikipedia.org/wiki/Konami_Code

    8. Re:Secret Back door code is pretty easy!! by Anonymous Coward · · Score: 0

      Damn, if only that worked with my girlfriend!

    9. Re:Secret Back door code is pretty easy!! by ssstraub · · Score: 1

      No, only 30 lives per person.

  25. Re:Fuck You AmeriKKKa! by rrkap · · Score: 1, Insightful

    I'm 24 years old. I don't want to go through the next 50 years of my life living in an international air of worry and uncertainty. I don't want to live in a permanent state of fear, generated by a megalomaniacal American government taking advantage of the majority low IQ populous' capacity for being brainwashed.

    Can I suggest you up your meds? Your current dosage isn't doing its job.

    --
    I like my beverages with warning labels!
  26. There is no truth to the existence of a back door by WillAffleckUW · · Score: 1

    Just as it is untrue that the US used printers (small 68000 series computers) to disrupt the Iraqi networks and sniff traffic, and they are not diverting telephone cable Net traffic at the main connection sites in San Francisco and other locations.

    And, I never was in the shack at Yakima, and we never listened to your long-distance phone calls and made fun of you going kissy-kissy with your wife overseas.

    Really.

    Pay no attention to the curtain, nothing is behind it. Really. And get that dog away from it!

    --
    -- Tigger warning: This post may contain tiggers! --
  27. tee hee by DrNASA · · Score: 1

    finally, Microsoft is taking it in the backdoor - about freaking time.

    --
    ReaLemon is yummy
  28. Re:Conpiracy theorists.... by Deadfyre_Deadsoul · · Score: 1

    Yet one more reason I am glad I still use Xp and not the malware that is MS/NSA Vista Now, it begs to question, will SP3 for Xp have this same new random number generator with backdoor?

    --
    ~DF
  29. Re:funny by cthulu_mt · · Score: 0

    I think this "backdoor" story would be an appropriate time for the Goatse link. Where is that dude with the ASCI picture?

    --
    Virginia is for lovers. EVE is for griefers.
  30. Re:Fuck You AmeriKKKa! by DrNASA · · Score: 1

    Your options:

    1. Hard Liquor
    2. Pills
    3. Step 1 followed by Step 2
    4. Step in conjunction with Step 2
    5. See Slashdot poll for today - make friends will billionaire space pilot - relocate to the moon. Die when oxygen runs out.

    --
    ReaLemon is yummy
  31. Could be a problem! by Anonymous Coward · · Score: 1, Funny

    I hope the NSA thought to put a screen door on their backdoor, what with all the bees in the internet

  32. Re:Fuck You AmeriKKKa! by Jackie_Chan_Fan · · Score: 1

    I'm with ya... America sucks... and i'm American. Sigh.

    We're doomed.

  33. there must be a ulterior motive by wherrera · · Score: 1

    ...because this one seems too obvious. So, perhaps the NSA crypto folks have a couple of found back doors in some of the other algorithms, and this is a bit of misdirection to keep people from noticing what they really intend to use... :)

  34. Does anyone who uses Vista... by gillbates · · Score: 4, Interesting

    Have any expectation of privacy or security in the first place?

    IIRC, some of the key SCOTUS decisions regarding the Fourth Amendment have centered around a person's expectation of privacy. They've argued:

    • That someone doesn't have a reasonable expectation of privacy regarding their garbage.
    • That email doesn't have a reasonable expectation of privacy...
    • That a person's car is subject to Fourth Amendment protection.

    That said, the government could persuasively argue that someone who runs Windows, especially Vista, has no expectation of privacy in the first place:

    • More malware and trojans run on Windows than Mac and Linux combined. In fact, there are more viruses available for Windows than there are editors - even applications - for Linux.
    • Microsoft has continued a trend of introducing software with gaping holes for that past 10 years. No OS vendor in the last decade has produced a less secure OS than Microsoft. Surely the user must be aware of this, and have accepted the risk.
    • Users accept the Windows EULA, which, among other things, allows Microsoft to remotely check Windows for proper activation - so they already have given up their privacy to a corporation.

    Now the sad thing is that this does come across as a troll, but sadly, it's true. And it needs to be addressed. For some reason, the /. crowd thinks it is acceptable that a majority of the population uses an OS which is horribly less secure than the ones we ourselves use (Linux, Macs, etc...). We're supposed to be the technical ones who have the solution to these problems, and yet, most /.ers just choose to blame the victim and whine about Microsoft being evil. Granted, we already know that.

    Is it really acceptable that our collective rights are surrendered because a major corporation finds more profit in insufficient design and testing of its software? I realize that most of you loathe Windows, but unless we actually do something to fix the social barriers to the adoption of Linux, we can expect that, because Windows is so insecure, our government will be able to convince SCOTUS that a computer user has no "reasonable expectation of privacy".

    It doesn't matter so much that this PRNG is insecure. A knowledgeable cryptographer isn't going to trust the OS for random numbers, anyway - unless it is in compliance with some standard to which their code must comply. What matters is that Vista is full of holes, and we're talking about a PRNG which no software of cryptographical consequence is going to use anyway.

    Instead, we ought to worry that Windows itself is easily compromised by the government. That is the real problem. Why would you break the PRNG when you can rootkit even a fully patched Vista box with an email?.

    --
    The society for a thought-free internet welcomes you.
    1. Re:Does anyone who uses Vista... by Chris+Burke · · Score: 1

      That email doesn't have a reasonable expectation of privacy...

      Afaik, this issue has only reached the federal appeals court level, and they ruled that email does have a reasonable expectation of privacy.

      The reason, as us techie guys so often forget, is that the "reasonable expectation" has nothing to do with the technical feasibility of someone violating your privacy. It has much more to do with social norms, the intent of the user, and active steps being taken by the privacy-violator. It doesn't mean that you can reasonably expect that your privacy can't be violated, it means you can reasonably expect that nobody who is not malicious will.

      Plain-ol' email is easy as pie for anyone with access to your packets to read, since they're in plain text. Much like a letter in an standard envelope is pretty trivial to read by holding it up to a light. In both cases the expectation comes from the fact that the letter is intended by the sender to only be read by the receiver, accepted by social norm as something meant to be private, and finally that anyone who wishes to violate your privacy must take active steps in the form of a packet sniffer, or holding your letter up to the light.

      This is why you don't have a "reasonable expectation of privacy" in a public place, because how can you reasonably expect people to not hear you? With your garbage, you are demonstrating that you don't consider it your private possession anymore because you are sending it to be dumped into a landfill.

      So it's fine and dandy to say that we should get people to use more secure OSes -- this is important for protecting yourself from those malicious people I referred to earlier, who don't give a rat's ass about your expectation. But that's besides the point, because the "reasonable expectation of privacy" standard is about limitations on surveillance by law enforcement, and when a warrant is required and when it isn't.

      Which means the important thing is to not let the feds change the legal standard into being one of technical feasibility instead of the current standard. Because there's nothing that says that some exploitable hole doesn't exist or won't exist in [insert favorite software here], and by accepting their altered standard you're allowing them to argue that the existence of such a bug is ipso-facto legal permission for them to exploit it.

      No. My computer and my data packets are private and the government must acquire a warrant before reading either, regardless of what buggy insecure POS software I choose to run.

      --

      The enemies of Democracy are
    2. Re:Does anyone who uses Vista... by Vegeta99 · · Score: 1

      I can have my car (and pretty much any Ford before about 1998) unlocked and started in less than 30 seconds with a screwdriver and a slimjim, and I don't have to get anybody to click "Yes" to do it. Not only that, but I could put it all back together with no damage! Furthermore, most cars are built like this.

      Why, if we use your logic, is my car protected?

    3. Re:Does anyone who uses Vista... by LaskoVortex · · Score: 2, Insightful

      > For some reason, the /. crowd thinks it is acceptable that a majority of the population uses an OS which is horribly less secure than the ones we ourselves use (Linux, Macs, etc...).

      You haven't done a survey so you don't know the usage. I'd imagine more than half of the /. crowd are gamers and thus satisfy their guilty pleasures on a vista box. There is a lot of complaining about vista here simply because that is the major OS of /. Your points are valid, but they are largely falling on ears deafened by the explosions of "Quake" or whatever the kids are playing these days.

      --
      Just callin' it like I see it.
    4. Re:Does anyone who uses Vista... by Burz · · Score: 2, Insightful
      I agree with the overall thrust of your post, BUT:

      unless we actually do something to fix the social barriers to the adoption of Linux ...seems to imply the problem mainly lies with society in general. But the problem is basically within the Linux community: You are trying to sell people on nothing. At least nothing they can grasp, being non-sysadmins and non-programmers.

      Contrast the product structure of "Linux" with more successful FOSS projects like Firefox and OpenOffice, and learn the lesson well... or be content watching MS not only rebound in desktop share, but use that to eventually kick FOSS out of the server space as well. MS already has the cooperation of governments to standardize on Active Directory for Internet/Web logins! Think about that.

      In short, by referring to "Linux" as anything more than a kernel, you are leading all sorts of people (even programmers from the end-user application space) into a great deal of unexpected confusion, denying them a stable computing platform in the process... a platform that could have been a viable alternative to Redmond's greedy mendacity. It as if we all started referring to any browser or other program with Gecko in it as "Firefox", and millions of people put those "Firefox" distros on the shelf intending to switch over "someday".

      The Linux geekdom think they are so intelligent; In truth they've yet to learn even how to speak. Count me off that bandwagon.
    5. Re:Does anyone who uses Vista... by turing_m · · Score: 1

      "Contrast the product structure of "Linux" with more successful FOSS projects like Firefox and OpenOffice, and learn the lesson well..."

      What lesson is that? That it's better to be an application rather than an operating system?

      Adoption of linux does not depend on whether someone on /. discusses "linux" as opposed to "Ubuntu" or "Mandriva" or anything else.

      It depends on whether there exists a base of people installing and maintaining a distro with a linux kernal, those people managing the transition in an intelligent way (e.g. getting them accustomed to the applications they will be using rather than 10 new applications all at once, etc), and everything working well enough that they don't get pissed off and go back to XP or Vista.

      That's got to be at least an order of magnitude harder than getting someone to download firefox and doubleclick a file, especially when they understand most of the idioms already (address bar, etc).

      My experience has been that Ubuntu does almost everything I want, everything I need, and has a very newb friendly web forum. It is improving at a very rapid rate, and there is a new Long Term Service release coming out in a few months. I expect that there are many people like myself who have held back from installing Gutsy on friends' machines so that they can install Hardy, with the expectation that it will be more stable, somewhat more featureful, and "just work" for a long time (i.e. low maintenance).

      It is gaining one user at a time, and retaining more of them than any other linux distro I have seen. And that is what progress looks like. Back when the home computer market was dominated by the C64 and the Amiga, the change to MS and IBM compatibles was not overnight. It involved lots of informal and unpaid training, command line hacking, and experienced users telling the newbs to RTFM (nevermind that they didn't even know where to get the manuals from). Yet, the change still happened somehow.

      Most people referred to the new IBM compatible computers running MS DOS as an operating system as "PCs" or "IBM compatibles", yet this widespread confusion in nomenclature did not stop adoption.

      --
      If I have seen further it is by stealing the Intellectual Property of giants.
    6. Re:Does anyone who uses Vista... by noamsml · · Score: 1

      or whatever the kids are playing these days. Said like a true Linux user.
    7. Re:Does anyone who uses Vista... by Anonymous Coward · · Score: 0

      Windows can be run securely, but no one wants to spend that kind of time configuring it as such. It's so much less annoying to just run it as an administrator.

    8. Re:Does anyone who uses Vista... by dave1791 · · Score: 1

      This is the most refreshingly insightful thing I've read on slashdot in ages.

    9. Re:Does anyone who uses Vista... by Burz · · Score: 1
      As is almost always the case in these discussions, your pro-"Linux" argument falls apart when you look at the history of OS X, which is an operating system.

      You won't get that critical core of intermediate users installing distros if those intermediates are left bewildered. "Linux" has no coherent product with which most users and techs can get on the same page; One set of instructions for getting a shared printer working on one "Linux" can be entirely different on another distro, and after setup the functionality will often differ to boot. Same with installing software, as with almost every other critical feature that users are immediately aware of.

      I use and like Kubuntu myself. But Canonical are making the same old mistake: Letting other derivative products use the Ubuntu moniker.

      Distro vendors aren't even smart enough to emphasize that you must check for hardware compatibility before trying to switch. And there is no comprehensive, easy way to check before buying hardware. There is widespread denial that Linux' reverse-engineered hardware support is a poor substitute for genuine (even if closed) Wintel compatibility, so the "Linux" purveyors set users' expectations up to unrealistic levels.

      Most people referred to the new IBM compatible computers running MS DOS as an operating system as "PCs" or "IBM compatibles", yet this widespread confusion in nomenclature did not stop adoption. They all used the same OS. Not very confusing, esp. when on the hardware end everyone were already tripping over themselves to offer compatible products; That is all a side-effect of IBM's clout in the early 80s.

      Anyway, forget my earlier Firefox comparison. The Gimp would be much more appropriate.
    10. Re:Does anyone who uses Vista... by xhrit · · Score: 1

      We are playing Quake Wars nowadays. On linux.

    11. Re:Does anyone who uses Vista... by xhrit · · Score: 1

      >They all used the same OS. Not very confusing...

      IBM compatable machines ran the operating system known as DOS. Would that be MS-DOS, PC-DOS, DR-DOS, PTS-DOS, FreeDOS, OpenDOS, AmigaDOS, AMSDOS, ANDOS, Apple DOS, Atari DOS, Commodore DOS, CSI-DOS, DOS/360, ProDOS, or TRS-DOS?

      You are either a Shill or a luser.

    12. Re:Does anyone who uses Vista... by Burz · · Score: 1

      Name-calling aside, that is not a very bright thing to say.

      "PC Compatible" and "IBM Compatible" meant one thing: An x86 system with a clone BIOS and MS-DOS. Otherwise you had A) an IBM with PC-DOS, or B) something that would never be formally tested with the software you were trying to use with it.

      Why harp about the PC Compatible term, anyway? It doesn't even cover "Linux" systems.

  35. Re:funny by Amouth · · Score: 1

    i can't see how i got a troll for that - i was posting that with the unnoted refrence to my sig... i mean this "back door" isnt' even confirmed - it is jsut someones idea that it "might" exist.. without proof though you don't know - so MS is using it - sure give them bad press if it is "known to have" a "back door" but really without proof what do you have other than random people trolling about nothing..

    come to think about it my comment isn't any better than the rest of the people's here.. feel free to read my sig and troll away..

    --
    '...if only "Jumping to a Conclusion" was an event in the Olympics.'
  36. This is not Trivial... by deweycheetham · · Score: 3, Informative

    Supporting Information from Original Author:

    |Cryptanalytic Attacks on Pseudorandom Number Generators

    J. Kelsey, B. Schneier, D. Wagner, and C. Hall

    Fast Software Encryption, Fifth International Workshop Proceedings (March 1998), Springer-Verlag, 1998, pp. 168-188.

    ABSTRACT: In this paper we discuss PRNGs: the mechanisms used by real-world secure systems to generate cryptographic keys, initialization vectors, "random" nonces, and other values assumed to be random. We argue that PRNGs are their own unique type of cryptographic primitive, and should be analyzed as such. We propose a model for PRNGs, discuss possible attacks against this model, and demonstrate the applicability of this model (and our attacks) to four real-world PRNGs. We close with a discussion of lessons learned about PRNG design and use, and a few open questions. | http://www.schneier.com/paper-prngs.html

    If you have been keeping up with computer security, everyone should be aware of the weakness of Random Number generators and it's vast effects over large sections of the computer world. This is not trivial...

  37. Re:Fuck You AmeriKKKa! by DrNASA · · Score: 2, Informative

    "Children so stupid they think America invented the Internet, computer, motor car, light bulb, telephone etc ad infinitum...."

    Hmmm.....America invented the:

    Internet.....check
    Computer.....check...holy crap...modern computing actually has it's roots in TEXAS of all places (see the integrated circuit)...so DOUBLE check
    Motor Car....check again...lol - who would have thought, surely SOMETHING on this list was not invented by America
    Light Bulb....check again, wow
    Telephone.....and....wait for it.......check

    --
    ReaLemon is yummy
  38. Worth Noting by Anonymous Coward · · Score: 2, Interesting

    The talk referenced by Schneier in his essay as being the one that publicly disclosed the backdoor was given by two Microsoft researchers. So all the "OMG micro$oft iz so stoopid" posts might be a bit .... misdirected.

  39. Actually it is by p3d0 · · Score: 1

    There is known to be a backdoor, but nobody knows what it is. That's the part that's secret.

    --
    Patrick Doyle
    I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
  40. So... by jav1231 · · Score: 1

    The obvious joke here is that its a lot of trouble to go after the 12 people still using Vista. Baddump-bump!

    But seriously, this is a continuation of Microsoft's vendor-first, consumer-second approach.

  41. "may have" by Anonymous Coward · · Score: 0

    So it "may have" a top-secret magic NSA backdoor. I hear it also "may have" a portal to the magical world of Stupidia, and also "may have" a contest where the winner gets adopted by Bill Gates.

    I've also heard any version of Lunix using the GPLv3 "may have" a secret program which will turn us all into robotic mutant drones in the service of Richard Stallinman.

    Why, oh why, do teh FOSSies continue posting rumors, speculation, and insane conspiracy theories as news?

    1. Re:"may have" by civilizedINTENSITY · · Score: 3, Informative
      Well it *does* have a backdoor, the only question is does anyone have the constants? FTFA:

      What Shumow and Ferguson showed is that these numbers have a relationship with a second, secret set of numbers that can act as a kind of skeleton key. If you know the secret numbers, you can predict the output of the random-number generator after collecting just 32 bytes of its output.
      Also FTFA:

      The researchers don't know what the secret numbers are. But because of the way the algorithm works, the person who produced the constants might know; he had the mathematical opportunity to produce the constants and the secret numbers in tandem.

  42. Re:Fuck You AmeriKKKa! by Anonymous Coward · · Score: 3, Informative

    Germany invented the car.

    An automobile powered by an Otto gasoline engine was built in Mannheim, Germany by Karl Benz in 1885 and granted a patent in January of the following year under the auspices of his major company, Benz & Cie. which was founded in 1883.

    Although several other German engineers (including Gottlieb Daimler, Wilhelm Maybach, and Siegfried Marcus) were working on the problem at about the same time, Karl Benz is generally acknowledged as the inventor of the modern automobile.[5] In 1879 Benz was granted a patent for his first engine, designed in 1878. Many of his other inventions made the use of the internal combustion engine feasible for powering a vehicle and in 1896, Benz designed and patented the first internal combustion flat engine.

    Approximately 25 Benz vehicles were built and sold before 1893, when his first four-wheeler was introduced. They were powered with four-stroke engines of his own design. Emile Roger of France, already producing Benz engines under license, now added the Benz automobile to his line of products. Because France was more open to the early automobiles, more were built and sold in France through Roger than Benz sold in Germany.

    Daimler and Maybach founded Daimler Motoren Gesellschaft (Daimler Motor Company, DMG) in Cannstatt in 1890 and under the brand name, Daimler, sold their first automobile in 1892. By 1895 about 30 vehicles had been built by Daimler and Maybach, either at the Daimler works or in the Hotel Hermann, where they set up shop after falling out with their backers. Benz and Daimler seem to have been unaware of each other's early work and worked independently.

    Daimler died in 1900 and later that year, Maybach designed a model named Daimler-Mercedes, special-ordered by Emil Jellinek. Two years later, a new model DMG automobile was produced and named Mercedes after the engine. Maybach quit DMG shortly thereafter and opened a business of his own. Rights to the Daimler brand name were sold to other manufacturers.

    Karl Benz proposed co-operation between DMG and Benz & Cie. when economic conditions began to deteriorate in Germany following the First World War, but the directors of DMG refused to consider it initially. Negotiations between the two companies resumed several years later and in 1924 they signed an Agreement of Mutual Interest valid until the year 2000. Both enterprises standardized design, production, purchasing, sales, and advertising--marketing their automobile models jointly--although keeping their respective brands. On June 28, 1926, Benz & Cie. and DMG finally merged as the Daimler-Benz company, baptizing all of its automobiles Mercedes Benz honoring the most important model of the DMG automobiles, the Maybach design later referred to as the 1902 Mercedes-35hp, along with the Benz name. Karl Benz remained a member of the board of directors of Daimler-Benz until his death in 1929.

  43. Re:funny by Anonymous Coward · · Score: 0

    8======> (_O_)

  44. Re:Fuck You AmeriKKKa! by Anonymous Coward · · Score: 0

    Yes, Germany invented the car, America developed the assembly line production of cars... (Which is why many people somehow believe the car was invented here.... when in actuality the building process was just streamlined)

  45. Re:Conspiracy theorists come forth! Now it the tim by internic · · Score: 1

    This has absolutely nothing to do with open or closed source. A completely open source random number generator would have precisely the same vulnerability, because the problem isn't potential skulduggery by the vendor, it's potential skulduggery by the people who designed the standard.

    I agree that the vulnerability of this particular PRNG has nothing to do with closed vs. open source, but I think there is some relevance to the larger issue. Namely, in a closed source OS it seems (at least naively) that there are lots of ways to insert various sorts of back doors. If one is so worried about the government twisting MS's arm to put in a back door, it seems like a publicly known PRNG algorithm with known vulnerabilities is really the least of your worries.

    I'm not one of the people who thinks all software must be open source, but it seems like there are strong arguments in favor of open source as far as avoiding back doors from powerful interests.

    --
    "You call it a new way of thinking; I call it regression to ignorance!" -- Operation Ivy
  46. You might want to check your facts. by Anonymous Coward · · Score: 0

    Internet: Only one on the list that is really US made.
    Computer: Charles Babbage, England
    Motor Car: Karl Benz, Germany
    Light Bulb: Lots of people had working but impractical incandecent light bulbs for nearly 100 years before Edison, but Alexander Nikolayevich Lodygin of Russia would be the earliest inventor of "Edison's" style of light bulb, not Edison.
    Telephone: Either Bell, a Scot invented it in Canada, or Antonio Meucci, an Italian invented it in the US.

    1. Re:You might want to check your facts. by Anonymous Coward · · Score: 0

      We-ee-ell... the WWW is probably synonymous with the "Internet" for most people, and Tim Berners-Lee was an Englishman working in Switzerland.

    2. Re:You might want to check your facts. by Anonymous Coward · · Score: 0

      Dumb people don't change the facts. The web is not the internet. And the internet was created in the US.

    3. Re:You might want to check your facts. by DrNASA · · Score: 2, Interesting

      Lol - you know, I actually had a line about Babbage, but deleted it, figuring that there was no need to point out the distinction between what the op was referring to and what Babbage actually designed (but never created).

      I think the argument could be made that Bell was in America when the telephone was invented - not conceived.
      Regarding the lightbulb - toss up in my opinion. Edison built the first functional working model. Again, the difference between concept and function.

      Point taken on the auto's, so I'll submit to Benz, but one also has to look at the timeline / functionality of Selden and the Duryea's vs. the first model of Benz.

      Actually, the Internet is the one on the list that I had the most doubt about because there was a lot of work in England as well, even though we mostly recognize ArpaNet as the Internet's birth. Thanks for the reminder to never count on my memory ;)

      --
      ReaLemon is yummy
    4. Re:You might want to check your facts. by mjwx · · Score: 1

      If I just had mod points.

      A lot of Americans tend to forget just how much of these American inventions were conceived and designed in Europe and other places especially when their first production took place in the US. Where would modern computing be without Japan and what would the Internet be like without Sir Tim Berners-Lee, an Englishman (I don't doubt that ARPAnet was instrumental in creating the Internet but its still only half of what makes up the Internet today). Most modern inventions were joint efforts and what helped the US instrumentally was being a great place for foreign scientists to learn and work, Einstein and Von Braun were Europeans who made their breakthroughs in America (shame that this kind of thing is being killed by the recent wave of Xenophobia in the US).

      The first Automobile was invented by a Frenchman, Nicolas-Joseph Cugnot in 1769 whist Karl Benz produced the first petrol (gasoline for the Americans) powered Auto in 1885 in Mannheim, Germany.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    5. Re:You might want to check your facts. by Anonymous Coward · · Score: 0

      And don't forget his companion, Robert Cailliau, the Belgian guy! (Now that Belgium is still around, I figured we ought to mention it)

  47. Re:Fuck You AmeriKKKa! by hyades1 · · Score: 1

    The U.S. isn't doomed, but there is certainly a huge, deep pile of shit to be shoveled if it's going to get back to what it was.

    --
    I've calculated my velocity with such exquisite precision that I have no idea where I am.
  48. Re:Conspiracy theorists come forth! Now it the tim by miffo.swe · · Score: 1

    If you have read any recent history about modern US foreign and domestic actions things like this arent conspiracy theories, its just a likely conclusion. The terrorist thing is just a continuation on the soviet angle that was rendered useless for controlling the masses when the cold war ended. Encryption is the biggest threat to big brother society. Its just natural that US govt try to get their own backdoors in.

    The thing is, real terrorists arent so stupid that they use the POTS or the internet. Its you and me they are after.

    --
    HTTP/1.1 400
  49. All your seeds belong to us by Anonymous Coward · · Score: 0

    how are you gentlemen?

    I always use Pi as a random seed and haven't had anyone waste the computer time yet to... whoops

  50. Re:Fuck You AmeriKKKa! by Jerry+Rivers · · Score: 3, Informative

    Telephone was the culmination of the work of several people, and so the nationality of the inventor is in dispute. Bell did most of his work on the telephone in Canada.

    The first computer was a German invention (Konrad Zuse's Z3 in 1941).

    The first automobile was a French invention (1881).

    The light bulb had already been invented by several people, mostly European, before Edison perfected it.

    --
    The pursuit of absolute tolerance leads to the most rigorous and ludicrous intolerance. - REX MURPHY
  51. Re:speaking of backdoors... by gazbo · · Score: 2, Insightful
    Wait a minute...so the wife has to quit her job due to cock-based time constraints, and also the husband has to clean each and every cock.

    Well surely that implies he'll not have time to work either? So who's going to earn money to feed them and pay the mortgage? I assume it's the African-Americans mentioned in the story - if so, why not mention this benevolence in the story - surely it's a mitigating factor? Frankly, I'm beginning to suspect the telling of this story has a racist bias.

  52. Stop the Senseless Moderation! by mpapet · · Score: 2, Insightful

    Let's walk through these expert comments one step at a time:

    Anybody who is paranoid about this issue

    Did you see what just happened there? This is a clever sleight of words used to disparage and marginalize anyone who questions his premise. Disagree? Put on your tin foil hat and go to the psych ward. There's no room for discussion or even consideration of alternatives. Based on my direct, but very distant experience, Bruce is right in calling the backdoor.

    The Common Criterial evaluators look for such issues
    They do? Really? Anyone that has undergone EAL evaluation knows it's a giant tree-killing documentation project above all. I don't want to bore anyone with the details of CC evaluation, but it's not a creditable rebuttal to the issue. The meat of the matter from wikipedia "Higher EAL levels do not necessarily imply "better security", they only mean that the claimed security assurance of the TOE has been more extensively validated." http://en.wikipedia.org/wiki/Common_Criteria

    As another post so insightfully states, there's no reason why, IF some project actually needs the feature, they can't install it as a library. Just like we all do for openssl on windows.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    1. Re:Stop the Senseless Moderation! by secPM_MS · · Score: 1
      EAL is not about security features, it is about assurance levels. In the case of EAL4, the evaluators have access to the source code and design docs and they go through looking for issues and devising tests that the evaluation lab can use to ascertain that the code behaves as expected. The reason I mentioned CC is that the CC evaluation lab has source level access to the system, not that the CC evaluation raises the security functionality. Indeed, in general you will find that the evaluated configuration of a system typically has reduced functionality. This reduces the attack surface of the system as well as the cost and time of the evaluation.

      Following such an approach, I am running Windows Server 2K8 on my notebook, running as a normal user, with IE7 in enhanced security mode (which among other things, disables javascript, plugins, and most downloading). It also does not have media player. Reduced attack surface and defense in depth buys you a lot.

      Doing random number generation well is far harder than expected if you don't want to heavily load the system when the rng is hit heavily, as it can be on server.

  53. Wait... by Anonymous Coward · · Score: 0

    Aren't you the same one who told us that about some security hole that XP wasn't vulnerable to it like 2K was because you knew the "very smart" people working on it? And then we turned around only to find out that it was vulnerable in the next news release? I'm the same AC who didn't really believe you in that Slashdot story, either.

    Well, I'll believe that you work for Microsoft. But I won't trust the code until it's been audited.

  54. Random fun in the old days of computing by Bones3D_mac · · Score: 1

    This kind of reminds me of the old days of computing where random number generators simply cycled through a fixed series of values that would be repeated over and over each time you powered up the computer. One fun exploit of these early random number generators was to place two identical computers on the same circuit, then flip the switch causing both machines to boot simultaneously. Assuming the factors were reasonably identical, you could simultaneously launch any program that used random numbers and use one computer to predict the results of the other with 100% accuracy.

    For example, using this technique on a pair of Apple IIs (same series/configuration), you could load up a stock trading game on both machines and play one machine normally to see which companies were going to increase/decrease in value, then pour all the funds into the companies on the first computer that increased into those same companies on the second computer.

    Near as I can tell, the random number generator (at least on the Apple II) would only change state when a new value was requested from it... otherwise it simply sat idly by waiting for the next request.

    --


    8==8 Bones 8==8
  55. Re:Fuck You AmeriKKKa! by sherpajohn · · Score: 4, Informative

    Computer.....check...holy crap...modern computing actually has it's roots in TEXAS of all places (see the integrated circuit)...so DOUBLE check

    Bzzzt, wrong! Even though he is dead, his guy: http://en.wikipedia.org/wiki/Konrad_Zuse would argue with that.

    Motor Car....check again...lol - who would have thought, surely SOMETHING on this list was not invented by America

    Wait another dead guy wants a chat - http://en.wikipedia.org/wiki/Karl_Benz - says he invented the automobile.

    Light Bulb....check again, wow
    Um, better check your's again, I think its a bit dim if not burnt out. If you refer to Edison, he was not even close to the first to demonstrate what is now known as the incandescent light bulb. http://en.wikipedia.org/wiki/Lightbulb

    Well, 2 out of 5 ain't bad right? Well, the telephone is not a sure thing, so lets make it 1.5.
    --

    Going on means going far
    Going far means returning
  56. Re:Article summary follows by Fractal+Dice · · Score: 5, Funny

    "Don't worry, our Chinese contractors assure us there are no NSA backdoors"

  57. hackers NSA by Essequemodeia · · Score: 0

    Big deal. Hackers are already reading my emails and trying to steal my identity. Why not the NSA as well? Why don't I just mount a cloned monitor on my front door so people I *do* know can read it too!

  58. Updated for 2007: by leoxx · · Score: 1

    Trust us, we're from a multinational corporation!

  59. If true... by TheNetAvenger · · Score: 1

    If true, do you really think Microsoft would 'want' to do this? They have been pretty strong privacy advocates, especially Gates, denying even backdoor access for Bitlocker in a fight several years ago when bitlocker was demonstrated to the FBI.

    If the government is FORCING MS to do this, then we should be calling our representatives and not sitting around speculating or smacking on Microsoft.

    The whole big brother NSA thing is very much a Republican/Bush/Neo-con era mechanism, and Gates and lots of others at Microsoft vote democrat, even when it was NOT in their best interest as during the DOJ trials of the 90s.

    (Look up contributions, MS by far gives to Democratic canidates, and ironically companies that we think are on the side of the little people are ones shoving money toward pro-corporate/authoritarian canidates.)

  60. Re:Fuck You AmeriKKKa! by Yold · · Score: 1

    "invented the computer" is ambiguous. Many people, Babbage, Turing, etc. worked on the analytical model, and dozens if not hundreds of engineers worked out the details.

    http://en.wikipedia.org/wiki/Von_Neumann_architecture#History

    An American did however invent the concept of the modern computer.

  61. Re:Fuck You AmeriKKKa! by Anonymous Coward · · Score: 2, Interesting

    Wait another dead guy wants a chat - http://en.wikipedia.org/wiki/Karl_Benz - says he invented the automobile.
    But that's disputed. Actually, http://en.wikipedia.org/wiki/Siegfried_Marcus started to construct cars a few years earlier. But since he was a jew, the nazis were keen to hide this fact and declared Benz the inventor. They even tried to destroy Marcus' car in the museum. (But the museum staff was quicker, and had already built a wall around it, so it does still exist today.)
  62. Re:speaking of backdoors... by Anonymous Coward · · Score: 0

    Teh way the story started, i thought they were going to make the guy their sex slave and rape him every time he came to the gym. But the bit about th e wife was an interesting twist to tthe plot. Maybe they make the husband quit his job and pimp him to patrons at the gym, like in the sauna or something, and he earns a living that way.

  63. Re:Fuck You AmeriKKKa! by jdigriz · · Score: 2, Informative

    Internet: Yeah, we did.
    Computer: Arguable, depends on your definition of what constitutes a computer. Take a look at the work of Konrad Zuse. Yes, the US invented the integrated circuit.
    Motor Car: No, Benz, Daimler and others invented the car. However, an American, Ford, was the first with an affordable mass-produced car.
    Light Bulb: Edison may not have invented the light bulb but he did significantly improve it and mass produced the first long-lived incandescent.
    Telephone: Given that telephone is the name of a specific invention by Alexander Graham Bell, yeah, we did. Other inventors claimed to have transmitted sound over wires contemporaneously or nearly so. The courts stood by Bell's patent. Bell was a naturalized citizen of the US so we get to claim him.

  64. please mod parent down ... by redzebra · · Score: 1

    He's neither informative or interesting since his arguments only consist of shouting and words like holy crap,lol,...

    Informative or interesting would be a timeline for each invention.

    internet : http://inventors.about.com/od/istartinventions/a/internet.htm
    computer : http://inventors.about.com/library/blcoindex.htm
    car : http://inventors.about.com/library/inventors/blcar.htm
    lightbulb : http://inventors.about.com/od/lstartinventions/a/lighting_2.htm
    telephone : http://inventors.about.com/od/bstartinventors/a/telephone.htm

    Strictly speaking that gives him a 2 out of 5 (internet+telephone) and
    actually confirming the original statement

    Now watch how people will start coloring the facts to fit their agenda...

  65. Not against MSFT but the design by Anonymous Coward · · Score: 0

    As a cryptographer I've seen the EC-DBRG spec already and immediately dismissed it as completely stupid. From a practical stand point it's too slow to be useful, and from a statistical standpoint it's no better than say a hash in CTR mode (e.g. hmac'ing a counter).

    I know why MSFT added it [e.g. blind compliance with some spec, which from MSFT sounds odd to be honest...] but I don't agree with using the design.

    As I recall NIST specifies other hash/cipher based PRNGs which are also standard so I don't think that the EC approach is really "required."

    Tom

    1. Re:Not against MSFT but the design by ATucker · · Score: 1


      Read the details, Tom. The AES CTR_DRBG from SP 800-90 is the default PRNG and the ECDRBG is an optional PRNG that can be configured by the user or selected by the calling application.

      So why does MS have both if you "know" they only added it for "blind compliance" with the spec?

      --
      /* Andrew */
  66. You're doing it wrong by Nazlfrag · · Score: 1

    The talk referenced by Schneier in his essay as being the one that publicly disclosed the backdoor was given by two Microsoft researchers. So all the "OMG micro$oft iz so stoopid" posts might be a bit .... misdirected. Shhhh! That's not the way to bash Vista! Regardless, I was wondering when this little fact would spring up, and lo and behold it is by an AC after hundreds of 'stupid microsoft' quips.

    Let us all eat a large slice of humble pie.
  67. It's more akin... by gillbates · · Score: 1

    Well, let's extend your analogy: Suppose you bought a Jeep. Would you expect the contents in the back to be safe from theft, or inspection by law enforcement? Vista is that Jeep - it exposes your personal life to anyone who wants to have a look, breaks down a lot, costs a lot to maintain, and leaves the user exposed to anything hostile coming its way.

    --
    The society for a thought-free internet welcomes you.
  68. Re:Fuck You AmeriKKKa! by Jerry+Rivers · · Score: 1

    ""invented the computer" is ambiguous. Many people, Babbage, Turing, etc. worked on the analytical model, and dozens if not hundreds of engineers worked out the details."

    Fair enough.

    --
    The pursuit of absolute tolerance leads to the most rigorous and ludicrous intolerance. - REX MURPHY
  69. a question... by The13thSin · · Score: 1

    interesting, and I'm very inclined to believe you. I think it's great to hear from someone in MS that has relevant knowledge on these kind of subjects. (ie: I think most of MS related articles on Slashdot have some rather obvious "anti" written all over them.) So my question is, why do you "hang out with the slashdot crowd" so to speak? I know if I were working for MS I would've gone away long ago before I need a daily dose of Prozac. Seriously, I want to know.

    --
    "This should be fun, and by fun, I mean a wholly depressing insight into the cognitive ability of some grown adults."
    1. Re:a question... by secPM_MS · · Score: 1

      I try and provide a reasonably knowledgable and balanced response to the frequently unreasonable claims and responses. Clearly I will not have any impact on the true believers, but with luck I will have some impact upon those willing to consider the issues. I joined MS 4 years ago and have worked in security the entire time, assisting the Vista security effort for the past few years and I have some involvement with the crypto efforts. By background, I was more of a BSD'er than anything before I joined MS, having started on "modern" systems on VAX Ultrix and moving on to OpenBSD based appliances.

    2. Re:a question... by The13thSin · · Score: 1

      Thank you for your response, good to hear some balancing forces are here on slashdot as well... ...and just a warning: don't start with the prozac man... it's bad for you, trust me! ;P

      --
      "This should be fun, and by fun, I mean a wholly depressing insight into the cognitive ability of some grown adults."
  70. Re:Fuck You AmeriKKKa! by pizpot · · Score: 1

    The U.S. isn't doomed, but there is certainly a huge, deep pile of shit to be shoveled if it's going to get back to what it was.

    Nice try, keeping your chin up, positive attitude and all that. Showing you are real and not a nut. Well now try realizing that you've only learned the tip of the iceberg.

  71. If MS could make the best program ever. by milsoRgen · · Score: 1

    Once I saw a college kid tap into the FSB on his Xbox1 to get some serial number* or what not, I then realize that we as consumers, at least in this very narrow field, have some recourse for the actions of the powers that be... Just imagine how hard it would be for Microsoft to successfully include a back door in its most popular products that would escape the scrutiny of a million not so dumb users along with the actions and specific setups of millions pretty dumb users. It would be the single greatest program ever made. *Honestly I forget the specifics/goals of the project but it was nuts.

    --
    I'm sick of following my dreams. I'm just going to ask where they're goin' and hook up with 'em later.
  72. Re:Conspiracy theorists come forth! Now it the tim by SpaceLifeForm · · Score: 1

    Exactly. This is why it is the NSA and Microsoft involved.
    We already know the NSA is spying, it's just the methods are
    supposed to be secret. Obviously, they are not really secret,
    but they want to maintain the air of plausible deniability.
    NSA is doing the spying on everyone with the help of Microsoft.
    It is no surprise therefore, that Microsoft is attacking FLOSS.

    --
    You are being MICROattacked, from various angles, in a SOFT manner.
  73. Bitchslapping the retarded by jmorris42 · · Score: 1

    > From a more practical demonstration point of view, if there was a backdoor, governments
    > would not need to get warrants for inserting hardware keyloggers or custom malware on
    > systems to access system information. Governments both in the US and elsewhere do this,
    > which suggests that no backdoor is available.

    You made a fairly convincing argument until you spouted this idiocy. It is so error filled I'm uncertain where to begin the disection but since I must pick one....

    1. A backdoor gives no LEGAL right to collect information from a system thus anything obtained in such a manner would be inadmissable. A court approved keylogger, etc. yields admissable evidence.

    2. The existance of such a backdoor, if it existed, would be one of the US government's most treasured secrets, not to be squandered collecting inadmissable evidence on some petty crimelord or terrorist. I doubt it would be considered 'worth it' to bag UBL and his top ten minions. It probably wouldn't be worth giving up (and enduring the shitstorm from the Kostards) to prevent another 9/11 scale attack.

    Here one should reflect on history to see how such a resource would be used, and examine the rules that governed actionable intelligence gathered via Ultra. Unless a plausible alternative method can be shown where a piece of intelligence COULD have been obtained (even if they had to use other Ultra derived info to fake things) such that the enemy would not conclude that a break in Enigma was the ONLY way the allies could have known a fact, then it could not be used. England was willing to allow an entire city to be firebombed to preserve the Ultra Secret.

    3. Just because the NSA doesn't make public use of things pulled from the ultimate backdoor doesn't mean they aren't using it or wouldn't use it in some future crisis. And it doesn't mean someone else might not discover it and instead of publishing, ferret out a way to themselves activate it. (unlikely given the nature of public key crypto)

    Personally I'd like it if we someday learned the NSA had such a backdoor since it would prove they still knew how to 'spy hard' but sadly I doubt they have the chops for that sort of caper anymore, content instead to just sit in their lair and listen to signals.

    --
    Democrat delenda est
    1. Re:Bitchslapping the retarded by xhrit · · Score: 1

      If one should reflect on history to see how such a resource would be used, one could come to the conclusion that it would not be used for security or keeping the USA safe. no.

      The backdoor would only be used for industrial espionage like Echelon.

      http://news.zdnet.com/2100-9595_22-521985.html

  74. You are wrong. by Anonymous Coward · · Score: 0

    yes, but hte emphasis is on semi. In this cryptographic application, the number in question must be the product of two primes. There are 2 possibilities --- either the NSA multiplied the two primes, and has a theoretical chance of compromising something that uses the random number generator and poor security, or that they approved the number because they haven't factored it. Since this security standard is used by the US government to protect the US government, the odds of the second are much higher then the first.

    The FIPS standards aren't really for other people; they're published so the federal government can buy hardware/software combos that meet the FIPS standards. However, other people are free to use them, as they're one thing that the government hasn't stolen from the people, unlike ANSI and ISO standards, many of which are written by the government, made into an ISO standard, and then you have to pay the copyright fee for something your government wrote. That's a real travesty.

  75. "might know" by Anonymous Coward · · Score: 0

    the person who produced the constants might know

    "might know"

    Again... baseless and idle speculation. This is why FOSSies always get pwned by Microsoft: because they are always half-baked, and have nothing to present to anyone (especially prospective customers) aside from a whole lot of anti-MS FUD and their never ending hatred of all things MS.

    Reality Check: only 0.0000000001% of software customers (and that may be overly generous) will give two shits about being able to see your source code. You would be better off giving them a book written in a foreign language. At least that might look good sitting on their shelf or coffee table.
    1. Re:"might know" by aproposofwhat · · Score: 2, Informative
      No - it's not baseless and idle speculation, it's just good security practise not to knowingly use a method that has a documented insecurity.

      Whether the NSA have the second set of numbers or not is immaterial - the fact that they might have them is sufficient to make this implementation insecure.

      Now with OSS, we can change the set of numbers used to one of our own choosing, and use the algorithm with a reasonable expectation of security.

      With Vista? Sorry, mate, but there's no way to change the numbers.

      Hope that explains why people are concerned about this.

      --
      One swallow does not a fellatrix make
  76. Another FUD. by jacekm · · Score: 0

    Software generators, such as one build into Vista are only pseudo random. They rely on clever algorithms to generate sequences that in short series seem to be random but they are not in reality. Only hardware generators based on thermal noise or some other physical random process are capable to produce true random sequences. Therefore Microsoft product has "back door" just like every other software "random" number generator. This is another anti Microsoft FUD.

    JAM

    1. Re:Another FUD. by Anonymous Coward · · Score: 0

      finally, someone with a clue. Sorry to see you get modded down but that's what happens around here when you don't join the MS bashing party.

      I get a kick out of watching all the clueless cryptographers discuss issues like these. Is seems the NSA has been very successful into fooling all of them exactly as they wish to.

      Having personally seen Schnier in action before I wonder who pissed him off this time?

  77. Let me guess... by cepler · · Score: 2, Informative

    The constants were:

    4, 8, 15, 16, 23, & 42

    Hmmm...

  78. Re:Fuck You AmeriKKKa! by Anonymous Coward · · Score: 1, Informative

    Well, the telephone is not a sure thing, so lets make it 1.5.

    Well it is 1 out of 5 because Antonio Meucci, who originally developed his invention in Italy, was recognized as the inventor by Congress in 2002 under resolution 269:

    http://en.wikipedia.org/wiki/Invention_of_the_telephone#Antonio_Meucci

  79. Re:Fuck You AmeriKKKa! by hmccabe · · Score: 1

    However, Texas did give us the Dairy Queen with a quarter acre of floorspace. That's got to count for something.

  80. Calling it. by Hangly+Man · · Score: 0

    "Why use linux unless you have something to hide?"

  81. I don't believe it by Anonymous Coward · · Score: 0

    Bruce Schneier could produce literally truck loads of evidence, however, I would just deny it all. Sorry, but I can't help myself. I am just mimicking the masses of sheeple who will just cry Baahhhhh Bahhhhh.

  82. Re:Conspiracy theorists come forth! Now it the tim by Anonymous Coward · · Score: 0

    Yeah, they're coming for you because you're the special intellectual elite. I'm sure.

    Go read Catcher in the Rye and check your perimeter traps again, tinfoil boy.

  83. You're a fucking moron. by sid0 · · Score: 1

    > What matters is that Vista is full of holes

    I don't see any evidence for this. How do you say that? AFAIK OS X has had more security patches than Vista this year. And don't give me BS about "proving that Vista does not have security holes" -- you can't prove a negative.

    > you can rootkit even a fully patched Vista box with an email?

    I'm not sure exactly what you're talking about. If I send you an email with some sort of file, and you're stupid enough to go ahead and execute it, then I don't see what any OS can do to stop you. So you can basically rootkit even a fully patched OS X/Linux box with an email. User intervention is required in each case.

  84. Fine... by Organic+Brain+Damage · · Score: 1

    But what have you done for me lately?

  85. Sorry, I missread by Anonymous Coward · · Score: 0

    SCROTUMS

  86. Made for Microsoft... by tsbiscaro · · Score: 0

    From TFA: "It's too slow for anyone to willingly use it. And it makes no sense from a backwards-compatibility perspective"

    No wonder why MS is using it...

  87. why not upgrade to vista by hesaigo999ca · · Score: 1

    another reason why no one should upgrade to vista...please just put it out of its misery already.
    Bring out behind the shed and shoot it, let the penguin get caught holding the gun!

  88. Re:Fuck You AmeriKKKa! by Neil+Jansen · · Score: 1

    Relax, parent is an ancient troll: http://yro.slashdot.org/article.pl?sid=04/05/21/1339237

  89. Ummm, mods? Parent s/Informative/Funny... by SEMW · · Score: 1

    I really don't think the parent was going for "Informative"....

    --
    What's purple and commutes? An Abelian grape.
  90. Obligatory quote by base3 · · Score: 1

    Anyone who considers arithmetical methods of producing random digits is, of course, in a state of sin.

    John Von Neumann, 1951

    --
    One CPU cycle wasted on digital restrictions management is ONE TOO MANY.
  91. Re:Fuck You AmeriKKKa! by Anonymous Coward · · Score: 0

    "The first computer was a German invention (Konrad Zuse's Z3 in 1941)."

    Depending on your definition ENIGMA might have been the first - but that wasn't American either....

    "The light bulb had already been invented by several people, mostly European, before Edison perfected it."

    All Europeaqns, and Edison did not perfect it - he just copied their existing work. Welsbach and Hannamann were the inventors of the 'perfected' tungsten bulb

    But the one I always like is the idea that the Wright brothers 'invented' the airplane. Not only did they not invent something which had been technically specified for over 100 years before by Sir George Cayley, their sum contribution to the American aircraft industry was to tie it up in legal wrangling so that when WW1 came we had no world-class aircraft at all and had to buy them from the French!

  92. The linked technet article by Anonymous Coward · · Score: 0
    Anyone else notice the image half-way down the linked technet article?

    Reliabiliy and Performance Improvements
    Hmm... welcome to the operating system of the future, where nothing can *possibliye* go wrong...
  93. Stop Moving the Target by mpapet · · Score: 1

    EAL is not about security features, it is about assurance levels

    Your initial post suggest EAL would magically expose the back door. It will not. That is not how an CC review works.

    CC evaluation lab has source level access to the system

    As if source code access would expose the back door? It would not. Source code needs to agree with the documentation provided. Period. Back doors to a cryptographic algorithm are way outside the scope of CC certification.

    I am running Windows Server 2K8
    Don't get me started on Microsoft's elaborate blame-shifting system (Are you sure?) that's difficult to use. Maintaining a mixed environment of 2000/2003/MSSQL is extremely difficult. I can't keep a single cluster node at 99.999 uptime. Meanwhile, my Linux servers are running at 99.999% uptime.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    1. Re:Stop Moving the Target by secPM_MS · · Score: 1

      As I said in my first post, the ECC RNG is not on by default. CryptGenRandom is the default RNG. A study of the configuration settings and code, such as that done by a CC evaluation team, will definitely reveal that.

  94. Re:Conspiracy theorists come forth! Now it the tim by Anonymous Coward · · Score: 0

    Why not use your own algorithm then?

    For example, use an azerty keyboard (or a Dvorak) and encode everything using EBCDIC.

  95. Yet another reason to avoid Vista... by Anonymous Coward · · Score: 0

    ...as if we really NEEDED another reason...