Slashdot Mirror


Dual_EC_DRBG Backdoor: a Proof of Concept

New submitter Reliable Windmill sends this followup to the report that RSA took money from the NSA to use backdoored tech for random number generation in encryption software. From the article: "Dual_EC_DRBG is an pseudo-random number generator promoted by NIST in NIST SP 800-90A and created by NSA. This algorithm is problematic because it has been made mandatory by the FIPS norm (and should be implemented in every FIPS approved software) and some vendors even promoted this algorithm as first source of randomness in their applications. If you still believe Dual_EC_DRBG was not backdoored on purpose, please keep reading. ... It is quite obvious in light of the recent revelations from Snowden that this weakness was introduced by purpose by the NSA. It is very elegant and leaks its complete internal state in only 32 bytes of output, which is very impressive knowing it takes 32 bytes of input as a seed. It is obviously complete madness to use the reference implementation from NIST"

53 of 201 comments (clear)

  1. Bah by colinrichardday · · Score: 2, Interesting

    Who can you trust?

    1. Re:Bah by MobSwatter · · Score: 2

      Trust is a weakness for the world of spooks, not everyone lives in their world, but everyone seems to be a target for their affections at any cost...

    2. Re:Bah by Anonymous Coward · · Score: 3, Funny

      Ghostbusters!

    3. Re:Bah by plover · · Score: 2

      Your argument makes no sense. You say that Snowden wouldn't have access, yet he clearly had access to hundreds of thousands of TOP SECRET classified documents. And suspicions were raised around Dual EC_DRBG was raised by Bruce Schneier and other cryptographers about 5 years ago, long before Snowden leaked a byte.

      The backdoor remains an undemonstrated weakness, as nobody's actually published the key secret numbers that prove it can be exploited. But I am given to understand the math that points to the holes in the origin is pretty damning. Less convincing is "proof" that RSA took money from the NSA to support this algorithm. But given the other documents released by Snowden, and from other glimpses of the security snooping apparatus surrounding us (the reverse engineering of Stuxnet and related malware), there is nothing but support for these arguments.

      --
      John
    4. Re:Bah by davidhoude · · Score: 3, Insightful

      If I am not mistaken, Snowden did not have clearance to access these documents...making your point moot. He used stolen credentials to access the documents, credentials he was able to get due to his role as a sysadmin.

    5. Re:Bah by HalAtWork · · Score: 2

      Not Bob and Alice I guess!

    6. Re:Bah by 1s44c · · Score: 3, Interesting

      Theo de Raadt.

      OpenBSD is trustworthy but you have to be suspicious of the BIOS it runs under and every network it connects to.

    7. Re:Bah by 1s44c · · Score: 2

      Only we can't know that. It's entirely possible that all this and more had been stolen from the NSA countless times before Snowden made their crappy internal security an undeniable fact.

      If the Russians, Chinese, or who knows who else already got knowledge on how to exploit this weakness they would be quietly using it and we would never know.

    8. Re:Bah by LoneWolf · · Score: 2, Informative

      That "stolen credentials" story seems to be widely circulated but not much anchored in evidence. In fact, probably was originated from some NSA insider to discredit Snowden. A more detailed report to what happened comes from an article from Ars Technica. A very good read, by the way:

      The National Security Agency’s oversharing problem
      http://arstechnica.com/information-technology/2013/12/the-national-security-agencys-oversharing-problem/

    9. Re:Bah by jafiwam · · Score: 2

      I don't trust the article for one. I'm as paranoid as everyone else around here, but I don't think the NSA cooperated with RSA to put in a backdoor here, no matter how much Saint Snowden claims. If they NSA had such a backdoor it would be an extremely well kept secret and not left around where any low level junior contractor like Snowden would stumble across it.

      Go back and re-read how Snowden got to the position he did.

      The "Darnbob" version for you folks that won't bother to learn anything: Snowden was a network admin / security guy. Therefore had access to lots of stuff as his job was about the security of those things not about those things.

  2. Another view on teh RSA / NSA thing... by QuietLagoon · · Score: 5, Informative
    RSA doesn’t quite deny undermining customers’ crypto

    Reuters reported on Saturday that the NSA had secretly paid RSA Data Security $10 million to make a certain flawed algorithm the default in RSA’s BSAFE crypto toolkit, which many companies relied on. RSA issued a vehement but artfully worded quasi-denial. Let’s look at the story, and RSA’s denial....

    1. Re:Another view on teh RSA / NSA thing... by thue · · Score: 4, Insightful

      You need to read it like a lawyer. Take the first claim for example

      > Recent press coverage has asserted that RSA entered into a “secret contract” with the NSA to incorporate a known flawed random number generator into its BSAFE encryption libraries. We categorically deny this allegation.

      Note what is not denied:

      * It is not denied that the contract existed
      * It is not denied that they set Dual_EC_DRBG as default as a result of the contract
      * It is not denied that the contract was secret (they do later deny that their relationship with NSA in general was not secret, which is correct, but does not preclude one contract from being secret)

      They only thing they deny is that they knew that Dual_EC_DRBG contained a backdoor when they made the secret contract to set it as the default.

      The same with their other non-denials.

    2. Re:Another view on teh RSA / NSA thing... by gargleblast · · Score: 3, Insightful

      They didn't make a "non-denial." It appears to be quite explicit.

      The only thing explicit is that RSA denied a bunch of highly specific scenarios. Let me highlight one word:

      Recent press coverage has asserted that RSA entered into a “secret contract” with the NSA to incorporate a known flawed random number generator into its BSAFE encryption libraries.. We categorically deny this allegation.

      Now change that one word to from "known" to "unknown". Did they deny that?

      Plausible deniability. The only truth with a hole in it!

    3. Re:Another view on teh RSA / NSA thing... by WaywardGeek · · Score: 5, Insightful

      The crypto email list discussed this at length. People chimed in who remember when this happened. Here's my take away: EMC had just bought RSA, and was looking for profits, and many of the best and brightest at RSA had left. The NSA offered $10M to make their RNG the default in BSAFE, and no one at RSA could offer EMC management any compelling argument as to why they should not take the money. RSA issued a press release about it. There was no secrecy. Competitors thought it was foolish to take money from the NSA, and at the same time wondered how they could get onto this gravy train.

      This is a case of typical incompetence. The response RSA published is slimy lawyer crapola. The lawyer sucks as bad as the incompetent EMC management. The good news is that there was no secret deal that RSA agreed to with the NSA to compromise all our security. The NSA did their job well. RSA didn't. I'll just point out that only crypto ignoramuses would accept closed-source un-auditable stuff from anyone when it comes to encryption, IMO. Money corrupts this industry.

      --
      Celebrate failure, and then learn from it - Nolan Bushnell
  3. Re:YES! by Anonymous Coward · · Score: 2, Informative

    Someone creates an angry blog post and someone else submits a petition to change.org. Then nothing.

  4. So just like xorshift64 then by Anonymous Coward · · Score: 2, Interesting

    xorshift64 is a simple random number generator with a period of 2**64 - 1 (you cannot use 0).
    The 64 bit random number that it produces is the same as its complete state.

  5. Amish by Anonymous Coward · · Score: 5, Funny

    shun anything electronic, or electric for that matter. Substinance farm and read dead-tree books for leasure.

    1. Re: Amish by hoifelot · · Score: 2

      Trees are the new black!

    2. Re:Amish by Em+Adespoton · · Score: 2

      shun anything electronic, or electric for that matter. Substinance farm and read dead-tree books for leasure.

      Only read illuminated books though, not printed books. Otherwise, you're no better than the Luddites (who, while known for destroying printing presses and automated looms, weren't actually against the technology, just against it only being in the hands of the rich and powerful, to the detriment of the working class).

    3. Re:Amish by cold+fjord · · Score: 5, Interesting

      shun anything electronic, or electric for that matter. Substinance farm and read dead-tree books for leasure.

      Spooked by NSA, Russia reverts to paper documents
      Kremlin returns to typewriters to avoid computer leaks

      Only one of the many "benefits" from the leaks, not to mention:

      Snowden revelations lead Russia to push for more spying on its own people

      --
      much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
    4. Re: Amish by Anonymous Coward · · Score: 2, Funny

      Trees are the new Red-black!

      FTFY!

  6. Good article by Okian+Warrior · · Score: 5, Informative

    The link above is a very good introductory article on EC cryptography. If you know a little math but have no background in elliptic curves, this is a good introduction. Well worth reading.

    Clearly explained at an introductory level, with Wikipedia links for the assumed terms.

    Topical, singular (ie - it's the first one currently, a news "scoop" if you like), technical, and important.

    Lots to like here - Slashdot needs more articles like this.

    1. Re:Good article by neokushan · · Score: 3, Informative

      Just to add to this, if you want a good primer on Elliptic Curve Cryptography in general (and not just this exploit), this article from Cloudflare is pretty great even if you don't have a mathematical background. It also explains RSA quite well, so it's a good general crypto primer:

      http://blog.cloudflare.com/a-relatively-easy-to-understand-primer-on-elliptic-curve-cryptography

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    2. Re:Good article by Em+Adespoton · · Score: 5, Funny

      Too bad I've already given up on Slashdot and left. Really, I'm not here. You don't see me.

      Weak are your Jedi powers, my son.

  7. Re:is RSA soon an open vault? by gnasher719 · · Score: 4, Informative

    It seems to me that anything we thought were encrypted and could be, and was, considered secure in that embodiment, is soon subject to revelation. I'm no expert, but I'm losing faith in these algorithms. Please tell me it's going to be okay. PS: if you are NSA, I don't need your reassurances.

    Don't worry. It was known for quite a while that this algorithm _might_ have been backdoored. There are basically three possibilities:

    1. The NSA didn't know that it could be backdoored when they created it. So there is no backdoor, and the NSA is kicking themselves for that missed opportunity, or for the embarrassment. 2. They knew about it, but intentionally didn't create a backdoor. 3. They knew about it and created a backdoor.

    From looking at the algorithm, we cannot possibly know which one is the case. Obviously it would be totally insane to use this algorithm. But that _was_ known for quite some time.

  8. FIPS by sunderland56 · · Score: 4, Informative

    FIPS is a large group of standards - literally, the Federal Information Processing Standards. Any requirement is not "mandated by FIPS", it is mandated by one particular standard - which may or may not apply to any contract.

    FIPS 140-2 Annex C, for one, lists quite a few acceptable random number generators; for that standard, I see no requirement for Dual EC DRBG.

    1. Re:FIPS by Anonymous Coward · · Score: 5, Informative

      FIPS is a large group of standards - literally, the Federal Information Processing Standards. Any requirement is not "mandated by FIPS", it is mandated by one particular standard - which may or may not apply to any contract.

      FIPS 140-2 Annex C, for one, lists quite a few acceptable random number generators; for that standard, I see no requirement for Dual EC DRBG.

      There's still no requirement for Dual EC DRBG (so the summary is misleading) but Annex C is also somewhat misleading.

      FIPS 140-2 is modified by SP 800-131A which describes algorithm transitions (see FIPS 140-2 Implementation Guidance G.14) and therefore any new FIPS 140-2 module submitted after Dec 31, 2013 can only use an RNG from the SP 800-90A standard; not any of the other RNGs listed in Annex C.

      However SP 800-90A specifies four different DRBG algorithms, only one of them being the suspect Dual EC DRBG. So even today new modules aren't forced to use it. (And if fact I believe NIST posted a warning on their 140-2 website strongly recommending that people not use the Dual EC DRBG)

  9. How long until someone cracks the backdoor key? by gman003 · · Score: 4, Interesting

    Actually read TFA, enough flew over my head that I can't personally verify the math, but if true, well holy fucking shit. Once someone brute-forces the backdoor "key" used by the NSA, it looks like the entire system is cracked. Even if it takes a while to brute-force, once you have that you can open any encryption using that curve.

    Given that cracking this open would be so useful to both other monitoring agencies, and to criminal hackers, it's sure to happen eventually, if it hasn't already. I'm sure China could throw one of their supercomputers at it.

    I'd be curious to know just how hard it would be to brute-force the backdoor key itself. There didn't seem to be anything in TFA about that, and I can't figure out the math myself.

    1. Re:How long until someone cracks the backdoor key? by gnasher719 · · Score: 4, Informative

      Actually read TFA, enough flew over my head that I can't personally verify the math, but if true, well holy fucking shit. Once someone brute-forces the backdoor "key" used by the NSA, it looks like the entire system is cracked. Even if it takes a while to brute-force, once you have that you can open any encryption using that curve.

      It's quite possible that this cannot be brute forced. The only way is to create the back door at the time that the random number generator is created. In the end, that is the _first_ requirement: That an arbitrary attacker, given a complete description of the algorithm, cannot brute force it.

    2. Re:How long until someone cracks the backdoor key? by Anonymous Coward · · Score: 5, Informative

      (Hi. I'm the one Dan was replying to, from another thread. Proof on request, but /. mangles PGP signatures, amongst many other things.)

      No, it'd take a Rho attack of 2^127.8 complexity to break that key. Not happening. Way more likely is that someone simply steals the key from the NSA - a daunting prospect - but not particularly useful if all you wanted to know is that there is a backdoor, not to actually use it. There is, and people have been pointing that out since 2006.

      I was... surprised at Dan's response. I did not actually expect a response to noting that the backdoor in Dual_EC_DRBG was, and I'll quote myself here, "a backdoor that couldn't have been more obvious if you'd erected a flashing neon sign and driven a mounted parade with a marching band through it", because I didn't think anybody was in disagreement about that. Apparently I was wrong.

      My own reply to him, pointing out that even if you mind your Ps & Qs (in the way that he patented, mind you), Dual_EC_DRBG still sucks: http://www.ietf.org/mail-archive/web/cfrg/current/msg03689.html

      I don't have a reply to that yet. In all fairness, it has been the Christmas and New Year period, and it's been kind of a busy one this year, and there's some procedural things to sort out that are probably going to take some time (and input from the crowd here would probably only make things worse, right now). Meanwhile, we have recommendations to make about TLS - in short, use it, but for God's sake, turn off RC4 because it's shit and probably worse than the BEAST attack people tended to use it to avoid - and some new things to roll out with that before the big work on TLS 1.3; with encrypted ClientHellos and pinned certificates to stop random CAs impersonating sites high on the wishlist.

      An update, by the way: after re-opening the comments period, having been openly informed of the Snowden disclosures (albeit years after cryptographers warned them), NIST have agreed to remove Dual_EC_DRBG from SP 800-90A. So that's something, at least.

      /akr

    3. Re:How long until someone cracks the backdoor key? by jader3rd · · Score: 3, Informative

      It's quite possible that this cannot be brute forced. The only way is to create the back door at the time that the random number generator is created. In the end, that is the _first_ requirement: That an arbitrary attacker, given a complete description of the algorithm, cannot brute force it.

      From what I understand the whole point of algorithms like this is that brute force is the only option (without knowing the key). If there was some other mathematical way of determining the key the hackers would use that; so the goal is to create an algorithm where the secret key has to either be known, or brute forced. The only way to find the secret key is to literally try every possible number and hope that the computer stumbles across the right one eventually.

    4. Re:How long until someone cracks the backdoor key? by gman003 · · Score: 3, Informative

      From my understanding, the ability to have *a* backdoor is a quirk of the math, but the "key" depends on the parameters of the elliptic curve. Those parameters for this specific implementation were written by the NSA (under the guise of their mandate to secure American communications) and standardized by NIST. TFA had a full proof of concept using parameters he had generated, which worked.

    5. Re:How long until someone cracks the backdoor key? by thue · · Score: 2

      If you can choose P and e, then you can easily calculate Q=eP. It it only if you start with P and Q given that you can't find e.

    6. Re:How long until someone cracks the backdoor key? by Dr.+Blue · · Score: 3, Informative

      If its not doable how then did NSA supposed to have done it? Its not like they came up with the key at random then invented this algorithm to fit it, the fact that there is a backdoor key is a quirk of the mathematics.

      It's basically public-key crypto: you can create a keypair and publish the public key - that's essentially what this is, where the point Q in the Dual_CD_DRBG spec is really just a public key. There's a private key as well - it's far to expensive to compute it from the public key (basically 2^128 time), but they didn't have to do that since they generated the private key first.

      And it's really not a "quirk of the mathematics" - it's really pretty straightforward if you understand elliptic curves, and it has been well-known how to do this since 2007 or earlier. I think a lot of academic cryptographers didn't really worry about it when Shumow and Ferguson pointed out the potential backdoor, because it's really a pretty crappy technique anyway - academic cryptographers, who quite frankly often don't know what is used in practice, assumed no one would use this. Then it turns out that RSA used it as the default tehnique in BSAFE. Oops.

    7. Re:How long until someone cracks the backdoor key? by cold+fjord · · Score: 2

      I suggest anyone interested in this controversy read the following:

      How a Crypto ‘Backdoor’ Pitted the Tech World Against the NSA

      Although this is in regard to GCHQ, it probably applies to NSA as well: ‘We Can Trust GCHQ On Encryption’

      --
      much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
  10. This is pretty freaking huge, if true by Anonymous Coward · · Score: 2, Insightful

    Please, people who understand EC properly, verify & reproduce this ASAP. If so this is yet another thing (one the BIGGEST things) the NSA has denied about the content of the Snowden leaks.

    Plus RSA needs to really step up and be honest about just what occurred inside their walls wrt. FIPS and this algorithm.

    At this point, I think the longstanding rule that 'only a fool writes his own crypto' is getting weaker.. I would amend it to "only a fool writes his own crypto, or uses ones supplied by anyone without full, independent audit and full control over magic constants..."

    Captcha: bilked

  11. Re: OpenBSD by Richard_at_work · · Score: 4, Interesting

    No, because OpenBSD doesn't just use this PRNG as the source of randomness for its encryption implementations, it has used other sources mixed in for a long time. There was a recent story about FreeBSD switching to other sources and De Raadt being all cocky about other people finally doing what OpenBSD has done for years.

  12. Re: OpenBSD by iggymanz · · Score: 2

    that particular bug you link was fixed a week before it was found to be security vulnerability (at the time was known to cause crash)

    http://marc.info/?l=openbsd-misc&m=117404837006368&w=2

  13. Re:YES! by MobSwatter · · Score: 2

    Philip Zimmerman, PGP. Older versions 6.5.8 might be okay, something open source. However there is all this worthless security infrastructure in place already that has been rooted. There needs to be compensation for fraud.

  14. Re:YES! by Will.Woodhull · · Score: 4, Insightful

    For a start, we could at this point reasonably demand that everyone who has accepted a salary from NSA be branded on the forehead with a scarlet letter, so that anyone with any sense would know not to hire them for any position involving trust. Let them work as street sweepers. As persons who sort garbage into different recycling streams. We know these persons cannot be trusted. Identify them, remove them from their current jobs, and place their names on a very public list of persons who cannot be entrusted with anything, in any endeavor.

    There needs to be some amount of personal responsibility in the NSA, yet with the obvious exception of Snowden, there is no evidence of any such thing. One good place to start is to hold those who were involved in creating this monster accountable for ethical / moral turpitude.

    --
    Will
  15. More interesting facts by thue · · Score: 5, Informative

    I have been adding various facts to the Wikipedia article on Dual_EC_DRBG. A good deal of the most interesting points have not been reported in mainstream media.

    * The ANSI group which standardize Dual_EC_DRBG were aware of the potential for a backdoor.
    * Three RSA Security employees were listed as being in that ANSI group, making RSA Security's claim innocence claim shaky, since it is less likely that RSA Security didn't know about the back door when NSA paid them $10 million to use Dual_EC_DRBG as default.
    * Two Certicom members of the ANSI group wrote a patent which describes the backdoor in detail, and two ways to prevent it.
    * Somehow the ways to prevent the backdoor only make it into the standard as non-default options.
    * Somehow the people on the ANSI group forget to publicize the potential for a backdoor. Especially Daniel brown of Certicom (co-author of the patent), who also wrote an attempt at a mathematical security reduction for Dual_EC_DRBG, but somehow forgets to explicitly mention the backdoor. The conclusion in Brown's paper also seems very determined to hype Dual_EC_DRBG, whereas the other papers about Dual_EC_DRBG seem excited to hype the errors they find.
    * The potential backdoor only becomes public knowledge in 2007.
    * Daniel Brown writes in December 2013 that "I'm not sure if this was obvious." and "All considered, I don't see how the ANSI and NIST standards for Dual_EC_DRBG can be viewed as a subverted standard, per se.".

    Certicom is the main inventor and patent-holder for elliptic curve cryptography. The two Certicom employees failing to warn or prevent the backdoor they clearly know was possible doesn't reflect well on Certicom.

    1. Re:More interesting facts by thue · · Score: 4, Informative

      > In short, as is the case with many conspiracy theories all you have is a collection of things that are suggestive, not definitive.

      When you design a standard, one of the design criteria is that it does not allow for even a potential a backdoor. See fx https://en.wikipedia.org/wiki/Nothing_up_my_sleeve_number . It is most definitive that Dual_EC_DRBG should never have been approved given the knowledge available at the time of how to prevent any possible backdoor.

    2. Re:More interesting facts by cold+fjord · · Score: 2

      The DES case is well understood

      The DES case is well understood NOW. DES was at the subject of conspiracy theories, suspicion, and fear for nearly 20 years, just in the same way that this controversy is likely to go.

      The ironic thing about the DES controversy is that it was secretly stronger than many people knew, not weaker, and there are people that adopted other far weaker encryption schemes out of fear and suspicion rather than use DES. The secret techniques that DES was hardened against made cracking many of those other encryption much easier. I wonder how many secrets were lost because people went to those other encryption methods that were vulnerable to the secret cryptanalysis techniques that DES was immune to?

      Here is a though provoking piece for you: ‘We Can Trust GCHQ On Encryption’

      --
      much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
  16. Re:The maths is easy for a fifth grader by VortexCortex · · Score: 2

    You moron. My PGP encrypted email passes the Diehard tests for randomness -- Doesn't mean it's actually random bits.

  17. Re:is RSA soon an open vault? by sjames · · Score: 4, Insightful

    But looking at it from a motivation standpoint, only option 3 would be worth paying $10 million for.

  18. Re: Hmmm by MobSwatter · · Score: 5, Insightful

    Business Intelligence, for the purpose of corporate espionage. You also have to take into consideration that the NSA does answer to someone, and that someone was corporate sponsored before they were even put on a ballot to be voted on. They were put up to this, and continuance of the program likely has little to do with terrorism as the program has proven fruitless even after intelligence information was given about events prior to them being given/developing these tools but they in fact failed to respond accordingly to prevent them, this includes 9/11.

  19. Re: The maths is easy for a fifth grader by Anonymous Coward · · Score: 2, Informative

    Incorrect.

    Randomness will assume a gaussian curve distribution, given enought samples, over sufficient time.

    A generator algorithm that produces a uniform flat distribution would expose predictable patterns in output that could be exploited.

  20. Re:The maths is easy for a fifth grader by black3d · · Score: 2

    And when you're done in 50000 years with our current supercomputers, let us know the results. The number of possible combinations is a bit over 170141183460469231731687303715884105728. Good luck with your bubble-sort.

    --
    "The true measure of a person is how they act when they know they won't get caught." - DSRilk
  21. Re:YES! by Em+Adespoton · · Score: 5, Informative

    That's a fallacy. I choose what I share on social media.

    No you don't. Social media sites like Google+ and Facebook vacuum up information about you from everywhere, even things you never intended to be made public like links you've clicked on.

    Indeed -- you choose what you share on social media (to a degree), but most people aren't aware of the value of what they're sharing in the first place, and they have almost no control over what is shared about them. This is not the same as gossiping, as gossip involves the game of telephone -- there's no documented evidence that it's true. But when a date-stamped geolocated image of you in a nightclub shows up on your friend's blog with facial recognition indicating that it's you in the picture, and you called in sick that day, that's not gossip; that's evidence -- especially since that photo can then be flagged up for people who are following YOU (including co-workers and possibly your boss), even though you had nothing to do with the publication of the photo.

    And this is before we get into whether your privacy settings have been changed by the service host since the last time you reviewed them, and whether others who don't need to honor those settings have found anything interesting in "your" files hosted in an international cloud server system.

    If you choose to share nothing on social media, then at least none of the links can be verified, and it's closer to gossip. As soon as you start to share anything though, the metadata is enough of a net to snag all the bits of data about you that are published by others.

  22. The NSA is fucking stupid! by LazLong · · Score: 4, Insightful

    So, they introduced a backdoor into software that can be/is used to secure US nuclear secrets, in the hopes only they would be able to take advantage of it? This is just another variant of "security through obscurity." Really, really fucking stupid!

    1. Re:The NSA is fucking stupid! by ArsenneLupin · · Score: 2
      The backdoor is only useful if you have the "secret" key, i.e. the e such that Q^e=P . Working out e from P and Q is hard (discrete log problem). However, if you are in a position to pick the P and Q that will make it into the standard, you just pick up any Q and e of your liking, keep e secret to yourself, and hand out Q and the P derived from Q and e.

      So, only the NSA, and maybe people having managed to steal e from the NSA would be able to take advantage of this back door.

  23. Re:YES! by FishOuttaWater · · Score: 2

    How many people work at the NSA? How many of them are involved in eavesdropping programs aimed at US citizens? Why don't we just make it easier and brand all government employees? Or all Americans?

  24. Never trust an NSA douchebag by CuteSteveJobs · · Score: 2

    I trust Bruce Schneider. If he's a sleeper agent, they've put in so much effort it would seem churlish not to use him.

    And really, I'd use Blowfish ahead of any NSA encraption algorithm or LOL AES. If history has a sense of irony, China will pwn the entire US IT infrastructure using NSA backdoors.