Slashdot Mirror


NSA Turns To Commercial Software For Encryption

Roland Piquepaille writes "According to eWEEK, the National Security Agency (NSA) has picked a commercial solution for its encryption technology needs, instead on relying on its own proprietary code. "The National Security Agency has purchased a license for Certicom Corp.'s elliptic curve cryptography (ECC) system, and plans to make the technology a standard means of securing classified communications. In the case of the NSA deal, the agency wanted to use a 512-bit key for the ECC system. This is the equivalent of an RSA key of 15,360 bits." This summary includes the NIST guidelines for public key sizes and contains more details and links about the ECC technology. Since the announcement, Canadian Press reports that Certicom's shares more than doubled in Toronto."

51 of 264 comments (clear)

  1. FUD by ChozCunningham · · Score: 4, Funny

    Shouldn't we demand an open source solution? ;)

    1. Re:FUD by jdhutchins · · Score: 4, Insightful

      You can bet that NSA demanded the source code. I don't think they'd trust something they can't see the source to for their security. As for them buying a closed-source or open-source, to them it doesn't matter, they'll get the source anyways.

    2. Re:FUD by quadelirus · · Score: 5, Informative

      I stated this in another post, but I've got a link now:

      The NSA is not lisencing software, it is lisencing the right to use Certicom's ECC cryptosystem. Cryptosystems now are usually known even when proprietary to allow mathematicians and cryptographers the ability to test the security of it. (The RSA cryptosystem for instance is thoroughly explained on RSA's web-site, but you would still need a lisence to use the algorithm in a program)

      I found a tutorial by Certicom on their ECC cryptosystem here.

      PS. I could be wrong, but from the article it seems that "intellectual property" and "This is the first time that the NSA has endorsed any sort of public-key cryptography system." that they are not actually lisencing software but are in fact lisencing the cryptosystem. If I am wrong, I humbly apologize.

    3. Re:FUD by AKnightCowboy · · Score: 2, Interesting
      PS. I could be wrong, but from the article it seems that "intellectual property" and "This is the first time that the NSA has endorsed any sort of public-key cryptography system." that they are not actually lisencing software but are in fact lisencing the cryptosystem. If I am wrong, I humbly apologize.

      Well, before they just used it and didn't bother asking for permission. This isn't that big of a deal. The only thing out of the ordinary is they asked before using it. Nothing is stopping the NSA from ignoring a license for anything. Who are you going to call, the BSA to battle the NSA? Licensing applies to corporations and individuals.. governments can choose whether to obey them or not. We'd like for them to obey them, but who watches the watchers?

    4. Re:FUD by randyest · · Score: 4, Informative

      I'll take that bet aginst you. The NSA didn't demand the source code, they wrote the source code. Note that NSA is not buying some software tool, they are licensing a patented encryption concept. The NSA will implement this ECC encryption technology in many different ways, on their own:

      This agreement will give the NSA a nonexclusive, worldwide license with the right to grant sublicenses of MQV-based ECC covered by many of Certicom's US patents and applications and corresponding foreign rights in a limited field of use. The field of use is restricted to implementations of ECC that are over GF(p), where p is a prime greater than 2256.

      --
      everything in moderation
    5. Re:FUD by randyest · · Score: 4, Insightful

      Who the hell in their right mind is going to license this from the NSA?

      Uh, anyone who wants to do business with or exchange sensitive info (read: pretty much anything) with the NSA. If that's you, you'll most likely have to use this to talk to them about anything important. So, it seems logical that they've acquired the ability to grant sub-licenses -- that way you can be provided with tools to encrypt and decrypt communication that works with the NSA-specific implemntation of this patented ECC concept.

      Maybe you were thinking that the NSA is going to release commercial products based on ECC? I don't think so. They'll probably leave that to Certicom and just use the licensed technology for thier own use rather than resale.

      --
      everything in moderation
  2. What about license abuse? by MongooseCN · · Score: 2, Interesting

    What if a company is suspicious of the NSA not following the license it was given? It's not like the government is going to let a commercial company into the NSA to audit all its computer systems. I suppose it will all be done on the honor system.

    1. Re:What about license abuse? by randyest · · Score: 5, Informative

      The NSA practically can't not follow the license -- it's world-wide and allows granting sub-licenses, and is only restricted to use above a certain security level. The NSA would have to use relatively insecure implementations of the technology to violate the license, and I think that's unlikely:

      Certicom Corp. (TSX: CIC), a leading provider of wireless security solutions, today announced that the National Security Agency (NSA) in Maryland has purchased extensive licensing rights to Certicom's MQV-based Elliptic Curve Cryptography (ECC) intellectual property. ECC is becoming a crucial technology for protecting national security information.

      This agreement will give the NSA a nonexclusive, worldwide license with the right to grant sublicenses of MQV-based ECC covered by many of Certicom's US patents and applications and corresponding foreign rights in a limited field of use. The field of use is restricted to implementations of ECC that are over GF(p), where p is a prime greater than 2256. Outside the field of use, Certicom will retain all rights to the technology for other industries that require the same levels of security, including state and local government agencies. Certicom will continue its policy of making its intellectual property available to implementers of ECC under normal commercial terms on a non discriminatory basis.

      --
      everything in moderation
  3. Public key vs. symetric by autopr0n · · Score: 4, Informative

    You can't really compare symetric key systems like AES with public key systems like ECC or RSA. With a symetric system you need keey your key secret, with public key you have two keys (encryption and decryption), and you only need to keep one of them secret. The other you can distribute far and wide.

    A lot of times, people will create symetric keys and then use public key systems to distribute them.

    --
    autopr0n is like, down and stuff.
  4. Re:OSS ECC? ECC vs AES by espo812 · · Score: 3, Informative
    What makes ECC so much better vs AES with a key size of 256?
    I'm sure a small ammount of googling could tell you this, but comparing ECC to AES is like comparing apples to oranges. ECC is a public key algorithm, and AES is a symmetric key algorithm. Thus, you would have to look up the fundamental differences between public and private key algorithms to find the differences between ECC and AES.

    The difference between ECC and algorithms like RSA, for example, is that elliptic algorithms can work with smaller keysizes, and this should have been noticable from the slashdot post that points out the commercial product uses a smaller keysize than the equiviliant strength RSA key.
    --

    espo
  5. Re:FINALLY ... by Egonis · · Score: 2, Interesting

    I am from Mississauga, Ontario - where Certicom resides, and am feeling two emotions:

    - I am happy to see a local business score a large contract in my hometown
    - I am confused as to how the American Government ever approved a purchase of an external Intellectual Property

    I'm sure alot of Americans will have disagreements on this one!

  6. If true it sends a signal. No quantum computer now by j_dot_bomb · · Score: 2, Interesting

    If true it sends a signal. They currently dont have a quantum computer (and therefore expect no one else does or will in a reasonable amount of time). However I do remember seeing a standard created to do a form of digital signatures only with conventional encryption (which is not in general "breakable" by quantum computers like "hard problem" public key cryptography).

  7. Re:Canadian code? by Timesprout · · Score: 5, Funny

    Its pretty obvious. The strange pronunciation required for Canadian variables makes the code more difficult to comprehend and so creates an additional level of obfuscation and thus greater security.

    --
    Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
    What truth?
    There is no dupe
  8. Re:FINALLY ... by EvilSS · · Score: 3, Funny

    Yea, it's really bizarre. You would think there was some kind of draconian regulations on cryptography in the US that encourages companies that develop crypto to not reside here. hrm....

    --
    I browse on +1 so AC's need not respond, I won't see it.
  9. Size of key by ptaff · · Score: 3, Insightful
    ...the agency wanted to use a 512-bit key for the ECC system. This is the equivalent of an RSA key of 15,360 bits.


    Brute-force decoding of these schemes is not recommended for the faint of heart, but I wonder: how can they tell that a 2 ^ 512 possibility range is as secure as a 2 ^ 15360 probabilities scheme?

    If I can reduce a RSA 1024 bits to a new method using only 4 bits, how can my way be as secure?

    1. Re:Size of key by espo812 · · Score: 4, Informative
      I wonder: how can they tell that a 2 ^ 512 possibility range is as secure as a 2 ^ 15360 probabilities scheme?
      Because breaking RSA does not involve brute forcing the bits, it involves factoring huge ass numbers into primes. Look up the differences between symmetric and asymmetric (or private and public) key cryptosystems.
      --

      espo
    2. Re:Size of key by inburito · · Score: 2, Informative

      Maybe because discrete logarithm problems in ordinary number groups are much easier to solve than in elliptic number groups.

      As a matter of fact, discrete log problem for ordinary numbers has been improving steadily whereas Elliptic curve group discrete log techniques have not seen significant improvement in the past 20 years. This difference accounts for today's reduced key-size requirements for elliptic curves.

    3. Re:Size of key by LT+Grant · · Score: 2, Informative

      If you look back at Dr Chris Monico's work at cracking ECC-109 you can get some more background on the equivalences and how they match up and how the two are compared and how they are very different. 109 took a lot of computational time (biggest ever so far I believe), and this is vastly bigger, as if I remember correctly ECC encryption doesn't grow linearly, but exponentially. The code used to crack ECC-109 has been somewhat improved in ECC2-109 based mainly on things Dr Monico saw in 109 and based on some research he and I did regarding a paper by Teske of Waterloo.
      Hope that is informative.

      --
      ---
    4. Re:Size of key by Metex · · Score: 2, Informative

      Ugh this is actually pretty easy to calculate,
      for the rsa key in order to find the approximate number of keys possible you use the simple equation 2^k / (ln 2^k) this gives you an 'approximation' for all possible primes you can have in k-bits.

      As for the ECC system I cant remeber the exsact computation off the top of my head to calculate key space but it has a much higher key concentration per bit added to key. not as high as a symetric cryptographic system with a 2^k keyspace but pretty high up there.

      As for your reduction useing a ratio it wont work out since they both use diffrent keyspaces.

      --
      Never could figure out why my girl liked my bitch tits, then I found out she was a lesbian.
    5. Re:Size of key by bluGill · · Score: 2, Interesting

      You don't brute force either system. Useing the best known mythods to break encryption today (which in the case of both RSA and ECC is not brute force) breaking a 512 bit ECC key is about the same effort of breaking a 15360 bit RSA key. Note that breaking a 512 bit symetric key (something like AES, blowfish, modified to use a 512 bit key) is more effort than breaking either one.

      I'm not sure I belive the difference is that great. RSA type encryption has had a lot of effort put into breaking it, ECC gets less attention (though it is getting more). If ECC got as much attention as RSA did from the mathamatical world, the difference in efforts to break them would be a lot closer.

      Note that both ECC and RSA are NP-complete, meaning that if there is a generic way to break one, in essentially no time (no matter how big the key is), that algorythm can be easially modified to break the other. There is a lot fo debate in CS about such problems and if such an algorythm exists. Anyone using either must be aware that there is no proff that you can't break it trivially.

    6. Re:Size of key by jareds · · Score: 3, Informative

      Note that both ECC and RSA are NP-complete

      This has not been proven, nor is it even commonly believed to be true.

    7. Re:Size of key by joeblarnystone · · Score: 2, Informative

      The best known means for solving the Discrete Log Problem over an EC is much slower then the best known means for factoring integers. This is why they can claim that a 512 bit ECC key is equivilant to a 15630 bit RSA key. The time it would take to solve both problems is equivilant.

  10. Canada by nuggz · · Score: 3, Informative

    FWIW I'm Canadian.

    Canada has many exceptions to US restrictions. This makes sense. It is cheaper to work together, and we do in many military and space applications.
    Our interests are basically very similar, and both countries are generally trustworthy of each other.

    The only conflict are on specific policy issues.
    It also matters which government is in power in each country.

    There have been quite a few times where state and provincial officials have banded together to fight both federal governments.

    Plus if it works well, why shouldn't they use it?

  11. This isn't an issue of "open" vs "closed" by NotQuiteSonic · · Score: 3, Interesting

    The algorithm they used is patented and very much open for criticism. It would need to be fore NSA to choose it. Think of it like RSA where the algorithm was patented as well (many open source applications use RSA now, since the license has expired).

    Dr. Scott A. Vanstone is a professor at University of Waterloo, so it is kind of neat to see one of my profs in the news (I knew about the company, but they haven't had much going for them for a while). He teaches Coding Theory (CO 331) and is the Executive Director of Centre for Applied Cryptographic Research

  12. Damn! by MMC+Monster · · Score: 3, Funny

    I guess rot-13 just isn't good enough anymore. (Am I the only one to think "Wow, how the mighty have fallen!" when I read this?)

    --
    Help! I'm a slashdot refugee.
  13. Attention to the knee-jerkers! by Anonymous Coward · · Score: 3, Insightful

    In case you didn't catch the hint in the article, this is significant because NSA chose an EXTERNALLY developed encryption solution over an INTERNALLY developed solution. This has NOTHING TO DO WITH OPEN SOURCE SOFTWARE. Please save your comments like "what about SSH/GPG/SSL?" for some other discussion.

    Thanks.

  14. This isn't software, it's patents. by Garin · · Score: 4, Informative

    As far as I understand the deal, this has nothing to do with licensing software. They couldn't have gone with an OSS version (or "roll their own") as so many suggest because they're not licensing just software, they're licensing patents.

    You'll note that they've also got sublicensing rights on those patents. There could be a software component to this deal, but as far I can tell it appears that this is mainly about patents.

    --
    In any field, find the strangest thing and then explore it. -John Archibald Wheeler
  15. Re: Privatization by Black+Parrot · · Score: 5, Funny


    > The NSA's job is to make secure codes for government use, and break other people's codes. So they licensed someone else's code, but why are they announcing it for intra-government use? The obvious question is, Can't they roll their own?

    Probably just means that they've discovered how to crack it, so now they want everyone else to use it.

    --
    Sheesh, evil *and* a jerk. -- Jade
  16. Re:Privatization by paranoidsim · · Score: 3, Insightful

    I don't think this is about privatization. I think this is about the NSA being overloaded with more important things to worry about. Such as the "War on Inanimate Objects", namely, Terrorism. For instance, look at their new hires figures jump from roughly 100/yr, to over 1000. They are busy, they are upgrading, and they are worrying about processing the loads of new data from monitoring an exponentially higher amount of data then they were accustomed to only a few years ago.

  17. Re:Privatization by espo812 · · Score: 5, Informative
    Oh come on, I know Bush's administration is all for privatization and turning to the private sector and all, but this?
    I believe that the technological divide between the NSA and the private sector has been shrinking over the years. I also don't think they would have selected this product if they didn't have good reason to. I suspect that this product was probably developed with some degree of NSA involvement, either contract work there or by former contractors/employees. And, low and behold, as I RTFA it says:
    Certicom has worked with the NSA, based at Fort Meade, Md., on several classified projects in the past, and this agreement is essentially an outgrowth of that work, officials said.
    So, it appears to have a lot of NSA involvement in the development. Actually, RTFAing a bit more closely it appears NSA is licensing the algorithm from Certicom. So they may not even be using the code from Certicom, they could be developing all the systems in house. Clearly, they wouldn't make a move like this without thoroughly analyzing the algorithms involved.

    So what comes out is a solution that was produced much cheaper than a similar inhouse effort, and this will save the tax payers money (which sounds good to this poor college student.) I have to say I'm surprised at the Agency going after a commercial product for classified purposes, but I'm sure they have good reasons.
    --

    espo
  18. Re:Privatization by Anonymous Coward · · Score: 3, Interesting

    Hypothetical:

    You're the premiere intelligence agency in the world. When you need to secure data, you use algorithms that nobody else in the world knows about, designed in secret by some of the greatest mathematical geniuses there are.

    When you need to secure an email you're sending to someone not in the agency, you can't (not to mention don't) use your hidden good stuff, because the recipient doesn't have the algorithm. So, you use something publicly available.

  19. Re:If true it sends a signal. No quantum computer by dAzED1 · · Score: 3, Insightful
    How on EARTH did you come to that conclusion? Are you saying that if they had a quantum computer they should just throw their hands up in the air for anything else, and not get it as tight as possible? Or that if they have a single quantum computer, that they would necessarily have hundreds of thousands (if you can make one, then you can make millions?), and therefore would be able to distribute classified documents/transmitions with ease? It would be pointless if the same capability didn't exist on both ends, you know.

    No, all this means is that they want something with better encryption. Even if they had a dozen fully functional "quantum computers" that were able to do spectacular computations in an instant (ah, that lovely superposition...) that wouldn't mean that they should just suddenly give up and use weak encryption. Better that only a few people in the world could break it with ease, than that anyone with $100k could build a sufficient cluster to do it quickly...

  20. Re:OSS ECC? ECC vs AES by quadelirus · · Score: 2, Informative

    In cryptography it's usually not a program that gets lisenced, but an algorithm (or cryptosystem). My guess would be that ECC has the copyright or patent or whatever you get on their algorithm which would make it illegal to write a program using elliptic curve cryptography (or at least their algorithm) without permission from the company. I once wrote a project that used the RSA cryptosystem for education purposes and I had to obtain permission from RSA legal to use the cryptosystem. (However it might be public now...)

    Also between AES and ECC. My guess would be ECC is much more secure than AES. If a 512-bit key for ECC is the equiv of a 15360-bit key in RSA that sounds extremely secure. As far as the last time I checked a 4096-bit RSA key was virtually unbreakable in any normal time span by even the fastest supercomputers built.

    Finally what the other replies to your question have been, about comparing apples and oranges: AES is a symmetrical key, meaning, the key that encrypts also decrypts.

    Public/Private Key encryption deals with two keys, the public key is freely available to anyone becuase when a message is encrypted with the public key it can not be decrypted with the public key. It must be decrypted with the private, or secret key.

  21. Re:Huh? by randyest · · Score: 5, Insightful

    Being the NSA doesn't guarantee you can develop the best technology in every security-related area. If another company or research institute happens to come up with a technology that's remarkably better than anything else like it and patent it first (such as the ECC mentioned in the article), the NSA should and does license it. That is, they buy the the rights to use the technology that someone else spent a lot of time and effort to develop (maybe even more than the NSA put forth in this field) .

    It's not like the NSA is buying a binary encryption software package they can't decompile, or shipping the secrets up to Canada for encrypting. This isn't a security concern. The NSA bought the concept of ECC, and Certicom deserves to be paid fairly for it. The NSA can do anything they want with ECC now, including grant sub-licenses without approvasl from Certicom. The only restriction is to require a minimum level of ecryption field size (encryption strength), which isn't a problem for NSA:

    This agreement will give the NSA a nonexclusive, worldwide license with the right to grant sublicenses of MQV-based ECC covered by many of Certicom's US patents and applications and corresponding foreign rights in a limited field of use. The field of use is restricted to implementations of ECC that are over GF(p), where p is a prime greater than 2256.

    --
    everything in moderation
  22. This is for the more discerning crypto customer by vt0asta · · Score: 5, Insightful
    "If you want to build an NSA-approved product, they want this in there."
    All that means, is like DES back in the day, if you want to have something NSA approved you pick this. I can guarantee you that the government when it's working on it's black budget work in general and historically has no regard for paying licenses for patents, and routinely mines the patent office for anything they may need. NSA has government customers that want protection, and instead of giving them the super secret good stuff, they find something off the shelf and give them this. This Certicom Corp. ECC is the new algorithm to study, because if it's NSA endorsed it's "probably" years ahead of the public domain state of the art, and is "probably" resistant to some pretty sophisticated crypto analysis techniques.
    --
    No.
    1. Re:This is for the more discerning crypto customer by Threni · · Score: 2, Funny

      >ECC is the new algorithm to study, because if it's >NSA endorsed it's "probably" years ahead of the >public domain state of the art, and is "probably"
      >resistant to some pretty sophisticated crypto
      >analysis techniques.

      You FOOL! That's exactly what they WANT you to think!

  23. Re:OSS ECC? ECC vs AES by graf0z · · Score: 5, Informative
    GnuPG can use DSA which is ECC.

    No, DSA != ECC.

    DSA and ECC both do encryption by exponentation, relying on the assumtion that the reverse function - the logarithm - is infeasible with the used keylengths. They are both called "Discrete Logarithm Systems".

    But the multiplication is done in completly different mathematical contexts: DSA multiplies in the rings Z/p (that are the natural numbers modulo p, p being a prime) where ECC multiplies in suitable "elliptic curve groups over finite fields" . That are finite sets of "numbers" paired with an complicated operation called "multiplication". These "numbers" behave quiet odd.

    The main practical difference is the neccessary keylength. Depending on the chosen eliptic curve, ECC keys are 4-8 times smaller than DSA keys. They get much closer to the "no attack is faster than the brute force attack"-paradigm than other public key algorithms like DSA or RSA.

    Unfortunatly, huge classes of suitable elliptic curves got patented.

    Google for free ECC software. There are at least some libraries published by academic research groups.

    /graf0z.

  24. Re:Great by kfg · · Score: 2, Funny

    "I, for one, welcome our new elliptic overlords."

    Indeed, this will be a major improvement on the hyperbolic overlords we now have.

    KFG

  25. Re:Privatization by Anonymous Coward · · Score: 5, Insightful

    on one hand, you have a crackhead who could get all the drugs he wanted legally and privately, but for some unexplicable reason bought his dope illegaly on the street through someone who could (and did) dime him out.

    on the other hand, you have NSA could use whatever patented technique they wanted and no one would ever know, but they decide to go out and publicly annouce a license


    You're wondering why the NSA didn't just go ahead and use Certicom's patented ECC implementation and keep it a secret? Because they're a lot bigger than Rush freakin' Limbaugh, and it only takes one employee to speak up and say, "we knew someone else patented this but we used it anyway" before someone gets in a lot of trouble.

    No one wants that kind of a black eye. If that scandal broke, the manager who gave the go-ahead to implement the Certicom solution without licensing it would probably find himself reassigned to a communications post in Afghanistan.

    And one thing about the US government... no matter how hard they try to keep things under wraps, they're just not very good at it. There are just too many nosy journalists and authors poking around... everything comes out sooner or later :) (For examples, see the SR-71, spy satellite imagery, Predator UAVs, the TIA project, etc. and the number of times Tom Clancy has been accused of espionage for incorporating published projects into his work.)

  26. Buy Canadian by solprovider · · Score: 3, Insightful

    Did anybody notice that the United States National Security Agency is buying encryption software from a Canadian company? Is this the same United States that refused to allow products using good encryption to be exported because they were considered military weapons?

    I am not flaming Canada; I work with several Canadians and they are all nice and knowledgable people. I just noticed the inconsistencies in our policies.

    Disclaimer: I am a citizen of the USA, and I hope that this trend continues. I would really like all our government agencies to use the best global software, not just our homegrown insecure proprietary systems.

    --
    I spend my life entertaining my brain.
  27. let it be said by mcryptic · · Score: 3, Funny

    15,360 bits ought to be enough for everyone.

  28. Re:OSS ECC? ECC vs AES by pyrbe · · Score: 4, Informative

    Bouncycastle Crypto APIs support atleast Elliptic Curve DSA and Elliptic Curve basic Diffie-Hellman (according to release notes). Possible other ECC algorithms too.

  29. So this means there's no easy way to break ECC... by Urkki · · Score: 2, Interesting

    ...known to NSA I mean. Why would they license it if they knew of some weakness in it...

    Hmm...

    Or maybe there *is* a suble weakness, leading to an "easy" way to break ECC. And NSA is licensing this to give it undue creidibility, so more people start using it, while NSA can easily (compared to RSA or whatnot) read everything encrypted with it...

  30. Evidence for Quantum Computer by Markus+Registrada · · Score: 4, Informative
    This isn't proof that they don't have a quantum computer. It's evidence that they do have, or expect to, or expect others to have soon. A quantum computer isn't magic. The best guess about the power of quantum computers, as applied to decryption, is that they can crack a 2N-bit cipher about as fast as an ordinary computer cracks an N-bit cipher.

    So, when we see the NSA not just adding key bits, but adding bits and then doubling them, we see evidence of countermeasures against quantum computers. This doesn't mean they have quantum computers. Remember that they are not just guarding secrets they transmit today against attack now, but against attack ten years from now, when revelation might still be damaging.

    Once we all do have quantum computers, I wonder what amusing revelations will come from cracking old ciphertexts. You can bet the NSA will keep busy at it, and so will the Brits, and the French, and the Germans, and the Russians, and the Israelis. (No doubt a few of the biggest corporations go on that list too.)

  31. Re:512 bits? by damiam · · Score: 2, Informative
    If it's 15360, then you have to try 2^15360.

    No, you don't. You have to find the factors of a prime number of that length. That leaves significantly less than 2^15630 possibilities, especially if you're using a decent factoring algorithm.

    --
    It's hard to be religious when certain people are never incinerated by bolts of lightning.
  32. Restrictions on field of use, royalties, etc. by Adam+J.+Richter · · Score: 2, Insightful
    It appears that the NSA have licensed this math in such a manner that they are free to sublicense it however they see fit.

    This agreement will give the NSA a nonexclusive, worldwide license with the right to grant sublicenses of MQV-based ECC covered by many of Certicom's US patents and applications and corresponding foreign rights in a limited field of use.
    The "field of use" is not specified in any of the links provided by the slashdot article (and is probably confidential), nor are the parameters of the sublicensing, such as how much, if any, royalties NSA has to pass upstream. It is also worth noting that the users within "the limited field of use" are further slighty restricted, although I don't know enough math to understand how important the restriction is:
    The field of use is restricted to implementations of ECC that are over GF(p), where p is a prime greater than 2**256. [exponent notation changed to get through slashdot filters]
  33. Sun and ECC by pmsyyz · · Score: 2, Informative

    Sun likes Elliptic Curve Cryptography. They have helped add it to Mozilla's Network Security Services and to OpenSSL.

    --
    Phillip
  34. Just a Wild Guess, But... by Nom+du+Keyboard · · Score: 3, Informative

    Just a wild guess, but what are the chances that NSA developed this secretly years ago and either planned to, or already does, use it. When the civilian cryptography sector finally caught up with them and actually patented the algorithm, NSA had to license it or stop using it. It wouldn't be the first time NSA has been shown to be far ahead of publicly known cryptographic knowledge. Differential Cryptology comes to mind.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  35. Re:FUD, but whose? by tchdab1 · · Score: 3, Insightful

    Given the secretive nature of the organization, it's possible (I have no proof or even inuendo) that the NSA is licensing technology that they themselves developed independently, perhaps even prior art.
    They could have determined that this is the preferred technology to use publically at this time, and then require the license in order to operate with it in the public domain.
    James Bamford's more recent review of the NSA documented an employee's discovery of public-key cryptography prior to Diffie's. They can't patent an invention without public disclosure (I presume), and they can't avoid licensing patented technology without proving prior art, which they must be reluctant to do - they would need to disclose when they discovered it. So, if all this presumption is true, from now on they'll be forced to license technology they they themselves created in order to keep the lid on their capabilities.

  36. Re:OSS ECC? ECC vs AES by dasmegabyte · · Score: 2, Insightful

    Unfortunatly, huge classes of suitable elliptic curves got patented.

    Unfortunate? For whom? For the people who spent long hours doing the extensive research which led to the development of advanced encyption systems? Or for the people who read the papers and attended the conferences and say "Great idea...think I'll make the same thing for free in the name of Openness!"

    Encryption is not like a 1-click pattent or library compression. It's hard, expensive and risky to devote your time to coming up with the next great encryption algorithm. And I am glad that we have agencies like the NSA to help offset this cost. It means there might be jobs somewhere for some of us to sit around and think about stuff rather than have to sell our talents like consultant whores.

    Free Software is all well and good, but some things are worth paying for. Right?

    --
    Hey freaks: now you're ju
  37. Re:Huh? by Ogerman · · Score: 2, Interesting

    However, I'm not sure that I'd go so far as to say anything mathematical shouldn't be patentable. In particular, this is an application of mathematics, not just pure math. I don't think you can come up with a new way to solve a pure math problem, or a new way of expressing an equation, and get a patent on it. ... We could argue that ECC is a discovery rather than an invention just as easily as we can for any other technological advancement.

    The difference is that patents on mathematical techniques or software algorithms are a distinct limitation of free speech, whereas patents relating to physical inventions are only a limitation of manufacturing rights. Ultimately, it could be argued that all invention has a mathematical basis, but software patents are unique in that they are unembodied. Because anyone can create software, software patents directly infringe on personal freedoms, in the same way that patents on literary style would.