Slashdot Mirror


1024-bit RSA keys In Danger Of Compromise?

antiher0 writes "According to an email from Lucky Green that came across bugtraq yesterday, 1024-bit encryption should no longer be considered pristine. Bernstein released a proposal that outlines the creation of a machine capable of breaking 1024-bit crypto on the order of minutes or even seconds for the measly cost of ~$1B USD. For a more thorough discussion, check out the original email." Update: 03/26 03:16 GMT by T : And don't forget to revisit Bruce Schneier's analysis of Bernstein's claims, which cast doubt on the practicality of breaking such large keys anytime soon.

137 of 363 comments (clear)

  1. $1Billion by UnifiedTechs · · Score: 2, Funny

    for the measly cost of ~$1B USD.

    Is the company you work for hirring? God I wish I could call a billion dollars measly!!

    1. Re:$1Billion by Mittermeyer · · Score: 2, Insightful

      When carrier battle groups, air wings, army divisions and the fate of nations are on the line, $1 billion for total SIGINT access is cheap indeed.

      Break out those one-time key pads and pigeons, boys, the government will own your electronic crytposouls before you know it.

      --
      ________________________________________ History Must Not Fall Into The Wrong Hands ___________________________________
    2. Re:$1Billion by joe90 · · Score: 5, Informative

      It *is* a measly sum - as the email says - how many government agencies have this sort of funding? More than just a couple of US agencies that's for sure.

      Assuming the email is correct (and having read it, it does't seem to be that incredible) That $1B investment gets you the infrastructure, systems and processes to routinely break 1024 bit keys (and therefore the contents of the encrypted payload) in a fairly short order.

      Since many people believe that a 1024-bit key is essentially uncrackable today, tomorrow and next century, 1024-bit keys are still going to be popular.

      If an organisation can amortise the cost over 3-4 years (which is the likely life of short (1024 or smaller) keys). That gives you quite a return on investment.

      If that $1B allows you to break one key every 5 minutes, over a 4 year period, you can break ~420,000 keys - which works out to a cost of less than $2500 per key. If you can intelligently target who's keys you wish to compromise, the benefits could be significant.

      --

      Fast, cheap & reliable. Pick two.
    3. Re:$1Billion by Mr.+Flibble · · Score: 3, Interesting

      It *is* a measly sum - as the email says - how many government agencies have this sort of funding? More than just a couple of US agencies that's for sure.

      Exactly.

      For those of you who would like a breakdown of how a system like this would work, you may want to read Cracking DES by the Electronic Frontier Foundation. (Note, this book is out of print, but the EFF has made versions available online.)

      It discusses building a computer from scratch that can crack DES quite fast. This same principle can be applied to any brute-force technique. And if the cost is $1Billion now, it will be considerably less in a few years.

      --
      Try to hack my 31337 firewall!
    4. Re:$1Billion by Gerdts · · Score: 2, Funny

      Sounds like a business plan. Let's go find some VCs!

    5. Re:$1Billion by Shanep · · Score: 2

      Or move to 4096bit.

      Don't forget, every bit added, doubles the strength.

      4096 != 1024*4

      My HP 48GX says:
      2^1024=1.79769313486E308
      2^4096=9.99999999 999E499 (which it also says for 2^1661, which seems to be the overflow point).

      4096 is 2^3072 times stronger

      ; )

      --
      War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
    6. Re:$1Billion by ssimpson · · Score: 3, Informative

      The NFS factoring algorithm is subexponential - adding a bit doesn't even nearly double the strength.


      --
      "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
    7. Re:$1Billion by Shanep · · Score: 2

      Sorry, I was only speaking of bit depths in general for current variable or future algorithms that support those high bit depths.

      I was thinking of adding "this assumes the algorithm can realise the full...blah blah"

      --
      War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
    8. Re:$1Billion by ssimpson · · Score: 2

      We are discussing the NFS as used to solve the DLP/ IFP. NFS in this situation for any "bit depths" (key lengths?) is subexponential.

      --
      "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
  2. I'm sure I've heard this somewhere before... by darkwiz · · Score: 3, Informative
    1. Re:I'm sure I've heard this somewhere before... by RollingThunder · · Score: 3

      Not quite.

      This is about professionals (Banking security) getting together and talking about the ramifications of DJB's idea.

      It's not 100% new, but it's not 100% recycled either. Of note is the fact that $1B is not out of their league ($2B satellites are standard items), and that they would be irresponsible to NOT have done this already.

      It's more data, take it or leave it as you will.

    2. Re:I'm sure I've heard this somewhere before... by darkwiz · · Score: 2

      Well, I'll give you that, but that would make this a slashback, or something like that. The headline "1024-bit RSA keys In Danger Of Compromise?" is old news.

  3. previously reported by Roadmaster · · Score: 2, Informative

    The basis for this story was on slashdot almost a month ago. A repeat? something derived from the previous story's information? the key point here is Bernstein's paper on factoring huge numbers, about which some people have commented, and which appears to "work out" on a mathematical level.

    1. Re:previously reported by bourne · · Score: 3, Interesting

      It seems to me that this story is hitting slashdot because, well, it hit slashdot.

      The original was passed around a few small mailing lists, where it got some comment but nothing big. Then it hit slashdot a month ago, and the number of places I saw it popping up increased. I also saw a story about DJB cranking at some reporter for misunderstanding the exact nature of the information, which tells me that someone thought it was suddenly big enough to have a reporter look into.

      And now, perhaps based on all this "publicity," Lucky Green or whoever is setting up discussion of it at some conference and revoking his old key. Note that he didn't do it a month ago, when the story was on all the crypto lists - presumably the more attention it got, the more real it became.

      Maybe I'm off base here, but I think this is one of those examples of the media gestalt manipulating and being manipulated by the media consumers - the story had to get big before it could be taken seriously, and it had to be taken seriously before it could get big... and the slashdot story a month ago was probably one of the bigger steps along the way.

      The slashdot effect... It isn't just for websites anymore!

  4. It's funny, laugh. (IHNRTA) by Anonymous Coward · · Score: 3, Funny

    That's okay.

    I'm certain that qcrack will be poorly documented and require the addition of 5,000 users to whatever supercomputer it happens to operate properly on.

    Then DJB will speak incessantly about how it differs from other encryption cracking techniques with its "modular design" (which is actually the application of many patches in order to obtain features found in most SMTP daemons, err cracking programs). Yeah.

    (Disclaimer: I love qmail.)

    1. Re:It's funny, laugh. (IHNRTA) by suso · · Score: 2

      (Disclaimer: I love qmail.)

      That's probably because you haven't tried postfix yet. I thought qmail was the bomb too until I discovered postfix and realized how bad the logging is in qmail.

  5. Cheap. by perdida · · Score: 2

    You got a great machine to be built w/taxpayer dollars on the cheap and quick.

    It is way easier for you to move up a few orders of magnitude of encryption than for them to build a machine that can crack it.

    However, this will mean a bigger supercomputer for all kinds of numbering tasks - basic research and math, physics, and astronomy will eventually benefit.

  6. Re:a billion here, a billion there by nneul · · Score: 2

    Actually, I guess that's not entirely true... it's not really a brute force keyspace, so you'd get more than 1 bit for the doubling in cpu, but you wouldn't get double the bits.

  7. Break my crypto for $1B? by brer_rabbit · · Score: 5, Funny

    Don't waste your money. I'll sell my company's secrets for a fraction of that.

    1. Re:Break my crypto for $1B? by SuperCal · · Score: 2, Informative

      Actually that's a very good point. At some point it does become more economical to buy off a person on the 'inside' of what ever organization you want to get secrets from... Hell I'd sell my personal secrets for a $1.50. Of course I don't have anything worth mentioning except my infatuation with girls with southern accents... oops well there's a freebie.

      --
      Business News and Resources: www.usasource.net
    2. Re:Break my crypto for $1B? by suso · · Score: 3, Interesting

      This would be an interesting Slashdot poll. "How much do you consider your most sensitive data to be worth?"

      $1
      $100
      $1000
      $10000
      $100000
      $100000000
      Mo re than Cowboy Neil has.

  8. Been all over SecurityFocus Already. by vkg · · Score: 2, Informative

    Here's the link to their write up, commenting on Bruce Schneier's take No Big Deal .

    Anyway, we all know they've been reading our sekrit kees by telepathy for years now, right?

  9. Would this be a solution? by SClitheroe · · Score: 5, Insightful

    If you can come up with a brute force approach to common encryption schemes, could you not stay one step ahead of something like this by utilizing multiple layers of encryption, with differing methods of encryption at each level?

    Give that a brute force attack is orders of magnitude more computationally intensive than the original encryption, would this allow you to stay ahead of the curve?

    Also, although the papers seem to indicate that the proposed system could try multiple forms of attacks on the encrypted data, would modifying or customizing the encryption algorithm at each layer of encryption help? Computers are great at brute force attacks, but I highly doubt a system such as this proposed one can do much in the way of analysis or reverse engineering of the encryption algorithms used...at some point, you'd have to resort to good old (and slow) human deduction...

    1. Re:Would this be a solution? by wherley · · Score: 2, Informative

      That's kindof the idea behind Triple-DES. Description here. DES was deemed too easy to break, so Triple-DES was born and is still used in some applications today. Used properly, it turns the effective 56-bit key length of DES into 168 bits in Triple-DES.

    2. Re:Would this be a solution? by frinsore · · Score: 3, Insightful

      Using multiple encryption on one message may not increase the difficulty and may even lower it. Encryption algorithms are mathmatical formula so this example will suffice even though it may be simplistic. Say you have two encryption algorithms F(x)=8x and G(x)=x*x*x. You may think that by combining the two would make it more difficult to find x but F(G(x))=(2x)*(2x)*(2x) or 2x cubed which is as difficult as G(x) by itself. But say instead of G(x) you used H(x)=x/8 which would simply decrypt x to it's original value. In short to be able to combine encryption algorithms you have to know what they do and even then there is no garuntee that you're not introducing new holes.

      If you modify the encryption algorithm then you're probably introducing new holes into it or at the very least you have to distribure those modifications to whomever you want to decrypt it. In essance a type of one time pad. Either you have to create a new encryption algorithm for each message or group of messages that you send or choose one and stick with it. If you constantly change algorithms or modify you have to have some secure way of getting those modifications to whomever wants to decrypt it, which can be difficult. You could simply create or modify an algorithm and not tell anyone what it is except for the recipient but to do that you'd have to know alot about cryptography and hopefully know the benefits of peer review. The people that encrpt DVDs know the benefits of peer review, now, after they released DVDs using CSS. If your modified algorithm is broken you'd probably never know because who would tell you? The guys that are trying to read your encrypted data or the ones that don't want to read your email and don't have access to your modified algorithm?

      The safest thing to do is either use a very long key or learn cryptography develop your own algorithm, get it peer reveiwed and then most likely use a very long key.

    3. Re:Would this be a solution? by 0x0d0a · · Score: 2, Insightful

      I doubt that using multiple encryption on one message would lower the strength. I'm not a cryptographer, but if that were the case, the very first thing any attacker would do is encrypt the message again with the same encryption scheme and a random key, which is a relatively cheap operation.

    4. Re:Would this be a solution? by Rasta+Prefect · · Score: 2


      It is however interesting to note that due to the way such Fiestel ciphers work, a double DES is easier to break than a single. Why? I don't remember, I'm not a math major, and don't feel like getting out my Crypto notes from last semester. :)

      --
      Why?
    5. Re:Would this be a solution? by billstewart · · Score: 2

      Use a long key - yes. Develop your own algorithm - no. Even the GSM telephone people and DVD encryption, which were theoretically developed by trained professionals, were total crockery. GSM had no excuse - the DVD folks could at least argue that the problem they were trying to solve is inherently hard and they were using double protection - a cheapo algorithm and expensive lawyers to run the DVDCSS lawsuits. But the GSM folks were working in well-established territory for which there are straightforward commercial-quality solutions available.

      --

      Bill Stewart
      New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    6. Re:Would this be a solution? by AME · · Score: 2
      I doubt that using multiple encryption on one message would lower the strength. I'm not a cryptographer...

      I guess that just about sums it up.

      --
      "I have a good idea why it's hard to verify programs. They're usually wrong." --Manuel Blum, FOCS 94
    7. Re:Would this be a solution? by billstewart · · Score: 2
      Layering is fine, if you know what you're doing and implement it carefully enough to prevent some layers from giving away information about other layers. For instance, you could probably come up with a layering of elliptic-curve public-key encryption and RSA public-key encryption that doesn't violate any of the don't-reuse-stuff rules and is still relatively practical. The nice thing about elliptic curve is that the keys are short - the bad thing is that the math is hairy enough that nobody's quite sure that somebody won't find a way around the difficult part. By contrast, RSA uses simpler and better-explored math (and longer keys), and there's less chance of a major breakthrough making a radical change in the necessary keylength, though Bernstein's machine may turn out to be significant given further exploration.

      The basic question is whether it's worth doing a two-or-three-algorithm solution as opposed to just making your keys longer. Depends a lot on your threat scenarios. Are you worried about the NSA cracking a key during your lifetime? Or are you running a bank and worried about bank robbers forging withdrawals? Or are you worrying about somebody forging your signature on an article on Slashdot? :-)

      It turns out that it's easier to make signature systems use multiple algorithms than encryption systems - all you do is create a tuple of Sigalgo1(message,key1),Sigalgo2(message,key2)... as your signature (and use a representation that doesn't let the Bad Guy change how many bits of the signature string are interpreted as belonging to each algorithm) and there's none of this nesting business required that encryption systems use.

      Computers, as proposed here *are* being used in conjunction with deep analysis - that's why the amount of computation required may have just dropped significantly. Reverse engineering doesn't really apply in this world, unless you're reverse engineering God's excellent job of making factoring difficult large numbers and interesting. :-) If you're doing some obscurity-based approach that requires reverse engineering, you've blown your chance at modern crypto work... Most of the public-key systems work by applying known hard algorithms in ways that let the work required to crack them be computationally infeasible, and it's understood that that's a shifting boundary - usually the crackers blow a dozen or so bits off the strength limits per year (some with faster computers, some with mathematical analysis), but the encryptors can add several hundred bits per year to the practical strength - doubling the number of key bits roughly quadruples the computation required, but you could do 512 bits conveniently enough on an 8086, so 2048 is no problem today, unless you've got packet size limitations which make that annoying, or unless you've got antique code that nobody wants to update for longer keys (particularly if the code is a silicon implementation of a bignum mulitplier), or unless you're running a web site that has to process a large number of connections per second, in which case this costs you actual money.

      --

      Bill Stewart
      New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    8. Re:Would this be a solution? by ssimpson · · Score: 2

      Double DES isn't easier to break than DES. It's harder, in fact a lot harder, just not as strong as one would naively believe it would be.

      Do a search for "meet in the middle attack" to find out why 2DES isn't as strong as 3DES.

      --
      "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
    9. Re:Would this be a solution? by ssimpson · · Score: 2

      Only under the assumption that an adversary has (2^56)*8 bytes of storage available...

      524,288Tb of resilient storage is pretty infeasible...

      --
      "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
    10. Re:Would this be a solution? by mosch · · Score: 3, Interesting

      524,288Tb of resiliant storage is only $1b at current prices, and that's dropping rapidly. If historical trends continue, it'll be $1m in about a decade, and it will be included standard in the PlayStation 9.

    11. Re:Would this be a solution? by ssimpson · · Score: 2

      That's true. I would be the first to concede that 3des can be broken with 3 chosen plaintexts, 2^56 blocks of memory, 2^111 encryptions and 2^111 operations (e.g. table lookups).

      At the moment however, that attack is clearly infeasible, so I continue to recommend 3DES as "the best we've got" (at least until AES has gained further confidence in the crypto community).

      --
      "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
    12. Re:Would this be a solution? by PurpleBob · · Score: 2

      It would have been helpful if you had challenged his point, and not him. Then again, that would be quite a bit more difficult, because his reasoning is sound.

      --
      Win dain a lotica, en vai tu ri silota
    13. Re:Would this be a solution? by AME · · Score: 2
      ...because his reasoning is sound.

      I can see how his reasoning would appear sound to someone with little experience in cryptographic methods.

      In fact, cryptographic algorithms are designed to be strong by themselves. If re-cyphering with itself or another algorithm would likely make it stronger then the original algorithm would have included this already in order to maximize its effectiveness.

      Since I apparently must point out the obvious: The reason one wouldn't re-cypher before trying to crack the code is that this is not guaranteed to make the solution any easier to find and therefore might be a waste of time. This, by the way, is the same reason that one would not want to re-cypher their secret message -- because doing so might compromise the strength of the encoding.

      --
      "I have a good idea why it's hard to verify programs. They're usually wrong." --Manuel Blum, FOCS 94
  10. Re:But what's a measily $1B for a government agenc by Anonymous Coward · · Score: 2, Funny

    i think he's plural

  11. what would you do if you had a million dollars? by jrs+1 · · Score: 2, Interesting

    if you were a government agency with $1b to invest in some kind of anti-terrorist encryption breaking scheme, would you invest it in this or would you invest it in quantum computing research?

    would it be worth going for the brute force attack or would it be worth finding a different solution? not to mention how much money you could win and how much cancer you could cure with the idle time.

    1. Re:what would you do if you had a million dollars? by Stonehand · · Score: 2

      Neither. You'd want to put the billion into a combination of carrot and stick -- humanitarian aid, education, and investments into certain regions, tied to reforms and oversight where possible; plus substantial amounts into human intelligence and law enforcement, since some people aren't going to like you no matter how nice you play.

      When it comes to terrorism, encryption really isn't the main problem. Identifying, isolating and eliminating causes (be they philosophies -- such as a desire for complete theocratic control -- or individual people) is.

      --
      Only the dead have seen the end of war.
  12. Nope by Brigadoon · · Score: 2, Interesting

    1024 bit, of course, is 2^1024 (approx 1.797e308). If you add one more bit (2^1025), you double the possibility of the number of keys, which means you double the computation time... In theory. This assumes brute-forcing it, and that the time it takes equals the maximum theoretical time to break it.

    2^2048 is 2^1024 times more than 2^1024 (that is, it's 2^1024 squared). Meaning that to crack 2^2048 - in theory - it would take roughly 1.797e308 times as long to crack.

    More numbers: If this $1B computer could crack a 1024-bit key in one second (consistently), it would take 5.7e300 years to crack a 2048-bit. That's much longer than the life of the universe.

    All this stuff is theoretical, of course. That's why you don't try to break the encryption, but rather look for holes in the software, or post-it notes on the monitor :)

    -Xyphoid

    1. Re:Nope by nneul · · Score: 2

      Right, but it's factoring. It's not like symmetric keys where you have to check every key, so it is a doubling in total keys, but you don't have to check all of them.

    2. Re:Nope by Zeinfeld · · Score: 4, Insightful
      2^2048 is 2^1024 times more than 2^1024 (that is, it's 2^1024 squared). Meaning that to crack 2^2048 - in theory - it would take roughly 1.797e308 times as long to crack.

      Bzzt! Wrong

      That would be the case if the fastest attack was brute force, in fact there are much better attacks. 1024 bit RSA is generally considered to be equivalent in strength to an 80 bit symmetric cipher. 2048 bit RSA is only equivalent to about 132 bits.

      Even so, the issue has been known for some time and that is why the crypto world is in the middle of a transition to 2048 bit keys. Only it will take arround 5 years to complete the move. VeriSign has been distributing 2048 bit root keys for some time.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    3. Re:Nope by Zeinfeld · · Score: 2
      dammit! I hate you fucking assholes who use "Bzzt! Wrong" in reply to posts. It's so fucking pretentious. Who the fuck do you think you are??? I don't care if the previous poster was wrong, show some fucking respect!

      OK, I am sooooo sorry, in future I'll say:

      You are the weakest link goodbye...

      I kinda find folk pontificating incorrectly about the strengths of cipher algorithms somewhat pretentious. Since you ask, I am one of the people who Lucky discussed his paper with before publication.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    4. Re:Nope by CondeZer0 · · Score: 2

      Please, ignore him(them?)... somebody that writes like that don't
      deserve to even be answered to... and he talks about showing
      some respect... *sigh*

      Your posts have been the most interesting I have read in
      /. in a long time... it's nice to see that there are some
      people here that know what they are talking about... thanks.

      Best wishes

      \\Uriel

      --
      "When in doubt, use brute force." Ken Thompson
  13. Re:RC5-64 challenge by damiam · · Score: 2, Informative

    RC5 is not a public-key algorithm and has nothing to do with factoring, so this is irrelevent. Factoring is of importance only to RSA and similar algorithms.

    --
    It's hard to be religious when certain people are never incinerated by bolts of lightning.
  14. Pay attention. Security = risk management. by mib · · Score: 5, Insightful

    Don't any of you bozos pay attention to prior articles? Security is about risk management. If you have something to protect that is worth $1bn for someone to steal and the only protection you have on it is 1024-bit crypto, you deserve to have it stolen.

    Your homework for today is to (re)read Secrets and Lies. There will be a quiz.

  15. The US government has something like this by WolfWithoutAClause · · Score: 4, Informative

    The US government recently relaxed export regulation for public key cryptography to make it the same as the domestic restrictions. The reasonable implication that we can take from this is that they have a way to crack that length of key, or they know they can do it, if they really have to.

    Either that, or the American government suddenly have benevolent feelings to the rest of mankind and a minority of their software community. Yeah right.

    --

    -WolfWithoutAClause

    "Gravity is only a theory, not a fact!"
    1. Re:The US government has something like this by billstewart · · Score: 2
      It's been generally suspected that NSA has had the ability to break 512-bit RSA encryption for a while. Breaking 384-bit RSA is old hat, and breaking 512-bit has been doable even before Nicko's group made it easy on their machines, but this IS exponentially hard work - before Bernstein's hypothetical machine was hypothesized, the limit to current practice was believed to be in the low 600s. This suggests that 768-bit keys aren't trustable for more than casual work, but 1024-bit keys are still way fine.

      The NSA has the advantage of occasionally being able to spend a billion dollars on chips or machine design, which says that building something like the EFF's DES $250K cracker was done at NSA long before the public got there (though "long before" has Moore's Law implications...). They also have some good mathematicians focusing on problems like this, not only because they like to crack other governments' codes but also because they need serious estimates of the strengths of the codes they use, but the general opinion in the crypto community is that they're no longer particularly far ahead of the open academic world, and in some ways they're behind because it's hard to get good peer review on secret algorithms, and it's hard to get and keep good mathematicians if you don't let them publish and don't pay them much money either. I don't believe they had the ability to crack 1024-bit RSA or Diffie-Hellman keys before Bernstein's paper came out - but they *do* have Bernstein's paper now :-)

      --

      Bill Stewart
      New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    2. Re:The US government has something like this by Sircus · · Score: 2

      The NSA's the world's largest employer of mathematicians. Obviously, I've no clue what stage they're at, but I'd say it's not that improbable that they already knew about these optimisations and possibly even the next set of optimisations too.

      --
      PenguiNet: the (shareware) Windows SSH client
    3. Re:The US government has something like this by WolfWithoutAClause · · Score: 2

      >I feel it's more likely they have finally realized what people on Slashdot have said hundereds of times
      >in the past: Encryption above 128 bit is readily available to anyone who searches for it, export restrictions will not stop it.

      Ok, in that case, why are there still limits on key length? If it was just encryption being easily available they would have removed all restrictions because it would make no difference. The ONLY explanation that makes any sense is that they have the capability to crack the length they've allowed.

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
    4. Re:The US government has something like this by WolfWithoutAClause · · Score: 2

      The only question in my mind is whether RSA is still worth using at all. How big is safe? 8192 bits?

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
    5. Re:The US government has something like this by Sircus · · Score: 2

      If your enemy is a major government and you don't have a very large budget yourself, you might as well give up now, IMHO. Not because I think they could factor 4096-bit RSA, but because I think they probably can get into your house without you knowing about it and tap your keyboard. The only time an attack like this wouldn't be called for is if the danger (to life, to diplomatic relations, whatever) of their being discovered is worth the money they'd have to spend on a more sophisticated attack.

      Fortunately, most people's enemy (at least in the cryptographic sense we're on about here :-) isn't a major government. Unless you're planning on political overthrow of a G7 nation, the NSA doesn't really care what you write in your e-mails. Sure, there's the few Echelon stories about contracts won under dubious circumstances, but the important point is that this information was retrieved from unencrypted communications, via a near-zero-effort search.

      I'm personally more than happy that 1024-bit RSA and 128-bit Blowfish (or 168/112 bit TripleDES) in an appropriate combination is enough to protect anything I'm doing against any of the possible enemies my actions are likely to throw up. The day I start trying to forment political revolution in one country or another, I'll look again at my crypto needs :-)

      --
      PenguiNet: the (shareware) Windows SSH client
    6. Re:The US government has something like this by ssimpson · · Score: 2
      (Hi Bill),

      "but this IS exponentially hard work"

      NFS is sub-exponential...It's a "hard problem", but it's not exponential (erm, see e.g. here).

      --
      "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
    7. Re:The US government has something like this by aziraphale · · Score: 2, Insightful

      The non-conspiracy argument that I've heard makes a lot of sense to me, at least. US government believes that E-Commerce is going to be big. US Government notes that US retailers can export lots of goods to other countries if e-commerce is enabled. US Government notes, exports==good. US Government realises, people outside the US need to be able to communicate securely with companies inside the states in order to perform such transactions. US Government allows export of strong crypto, giving US a world lead in e-commerce market.

      Money is almost always a better explanation for the actions of Americans than malice.

    8. Re:The US government has something like this by WolfWithoutAClause · · Score: 2

      32 bits isn't centuries; its about 45 years if Moore's law keep up, but RSA is much weaker than that in fact, so an extra 32 bit might only be 5-10 years.

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
  16. Re:a billion here, a billion there by JesseL · · Score: 2

    Wow! So if I only need to crack 128-bit keys I only need to spend something like $1.93831e-258! I can't wait to get started.

    --
    "Prefiero morir de pie que vivir siempre arrodillado!"
  17. Clearing up the deceptive intro by Glorat · · Score: 5, Informative
    1024-bit encryption should no longer be considered pristine

    That intro is deceptive at best and is, well incorrect. Remember DES and other symmetric ciphers that currently use about 128-bit or so encryption are unaffected by this. Certainly, 1024-bit symmetric encryption (your typical secret password encryption) is going to be unbreakable for centuries based on current predictions. The intro should read asymmetric or public key encryption at 1024-bits

    Secondly, the advances being talked about are in factoring large numbers into their prime factors using the Number Field Sieve (NFS). This algorithm is the most advanced known factoring algorithm and if you believe the article improvements show that factoring 1024-bit length primes is doable for 1 billion dollars or so. (It was only a few years ago this kind of cost was attached to building a DES cracking machine... today I could probably crack DES on my uni computers given the software. 1024-bit factoring is only a matter of time before it is easy). However, not all public key schemes rely on the difficulty of prime factoring. Elliptic curves rely on a different hard problem

    Conclusion, the intro should read "1024-bit asymmetric encryption that relies on the difficulty of prime factoring (e.g RSA) should no longer be considered pristine"

    1. Re:Clearing up the deceptive intro by swordgeek · · Score: 2

      So forgive me for pointing this out, but what part of "1024-bit RSA keys In Danger Of Compromise?" didn't you understand???

      The title is part of the article, and makes the necessary limitations. If you are going to nitpick, then at least nitpick correctly.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    2. Re:Clearing up the deceptive intro by Glorat · · Score: 2

      Oh yeah... forgot about that one =P
      Each extra bit doubles the time for a brute force attack so going from current 56bit keys, that's a lot of time.

      The other useful analogy (cos noone really gets big numbers into their head) is that at 256 bits, there are more key possibilities than electrons in the universe!

      Safe

    3. Re:Clearing up the deceptive intro by Tom7 · · Score: 5, Funny

      ...show that factoring 1024-bit length primes is doable for 1 billion dollars or so.

      Oops, Mr. Smarty Pants! I can factor 1024-bit primes for $0!

    4. Re:Clearing up the deceptive intro by Glorat · · Score: 2

      I think you've got your logic backwards there. Ahh... memories of my first ever uni maths lesson explaining the differences between "if" and "only if". RSA does (trivially) rely on the difficulty of factoring. If factoring was easy then RSA is dead hence RSA relies on the difficulty of factoring

      What you are trying to say is that RSA does not *solely* rely on the difficulty of factoring which you would be correct in saying since currently it is surmised that factoring is the easiest break in point. And since factoring is NP-complete and I have a (groundless) belief that P!=NP, I feel RSA is safe from this point.

      But logically, my original statements stands

    5. Re:Clearing up the deceptive intro by ssimpson · · Score: 2

      "Conclusion, the intro should read "1024-bit asymmetric encryption that relies on the difficulty of prime factoring (e.g RSA) should no longer be considered pristine"

      This enhancement to the NFS can also be used against DLP based cryptosystems (e.g. Elgamal, DH, possibly DSS) - your intro is insufficient and vague.



      --
      "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
    6. Re:Clearing up the deceptive intro by Glorat · · Score: 2

      This isn't a question of maths or crypto but English. If you disagree with what I am about to say, I will leave it at that. The correct sentence should be The security of RSA has not been proved to rely solely on the difficulty of factoring. That would be correct.

      You have stated the converse statement in effect. I am sure you agree with "If factoring is broken then RSA is broken". Hence RSA relies on the difficulty of factoring. (But, again, not *solely* on the difficulty of factoring).

      Now, onto a different subject. How dare you say factoring is not NP?? That is ludicrous. Search for google for "NP complete factoring" and see what it comes up with. I am 100% sure it is NP and 95% sure it is NP-Complete (only 95% because I have no proof for it, only what I read and professors tell me). It is purely a matter of whether P=NP. I believe P!=NP (a groundless belief as I said) hence RSA is safe from brute force based factoring attacks in the long run

    7. Re:Clearing up the deceptive intro by Glorat · · Score: 2

      Ignoring the flamebait... thank you, I was not aware of these other uses of the NFS. Would you happen to have references? Do you know if it can be applied to elliptic curve crypto?

    8. Re:Clearing up the deceptive intro by ssimpson · · Score: 2

      Comment not meant as flamebait - just pointing out that your intro is as "insufficient and vague" as the previous posters was "deceptive and incorrect". Sorry for any offense.

      Anyway, details of NFS being applicable to DLP can be found in e.g. pg 262 Applied Crypto 2nd Ed by Schneier, or in the crypto bible Handbook of Applied Cryptography by Menezes et al. A complete copy of this definitive text is available online in PDF format here. See pg 128/129.

      NFS is not applicable to ECC at all....


      --
      "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
    9. Re:Clearing up the deceptive intro by ssimpson · · Score: 2

      "I am 100% sure it is NP and 95% sure it is NP-Complete"

      Factoring is known to be NP but there is no proof of NP-Complete - see e.g. Bob Silvermans post - he suggests that the conses is that factoring != NP-Complete.

      --
      "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
    10. Re:Clearing up the deceptive intro by Glorat · · Score: 2

      Ok, gotcha on the NP-Completeness part. My new more informed conclusion is the factoring is maybe/probably NP-complete. Many have claimed it (and my prof didn't debunk me when I claimed it in a NPness project) but indeed I have seen no proof.

      I still find the use of "relies" too weird for me.
      If Kevin Tam "relies" on his health it means if my health is broken, I die. (RSA relies on factoring, if factoring is broken, RSA dies). Sounds correct for both sentences.

      The converse (not so good analogy here, ignore this paragraph if it doesn't make sense): If Kevin Tam's understanding "relies" on google's truth then if my understanding is wrong, google is wrong too. That doesn't follow. (If RSA relies on factoring and RSA can be broken, then factoring can be broken easily)

      That's why I disagree with the use of English you gave. If cryptographical publications rely on this kind of use, I'll avoid reading them as I'll just get confused no end!

    11. Re:Clearing up the deceptive intro by Glorat · · Score: 2

      I stand corrected

    12. Re:Clearing up the deceptive intro by Our+Man+In+Redmond · · Score: 2

      Well, you should get in touch with Bill Gates, since he thinks this will be a big breakthrough.

      --
      Someone you trust is one of us.
  18. Re:so.... by Surt · · Score: 2

    The importance here is that if your company is guarding, say $10 billion worth of data using 1024 bit encryption, you should be worried whether there might be competitors capable of spending $1 billion to steal that $10 billion. There are drug companies, banks, and research organizations for whom this is not an imaginary threat.

    Also, I think that putting a price tag on breaking 1024 bit encryption definitely qualifies as news for nerds. Who else would want to know?

    --
    "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
  19. Re:Measly? by Stonehand · · Score: 2

    Think of it as an investment. It's not like the machine will explode after its first success, so you can recoup the cost over time.

    For instance, if a major government or other well-funded entity not averse to a little corporate espionage managed to intercept and decode information regarding, say, bids on major contracts, it could pay for itself very rapidly.

    --
    Only the dead have seen the end of war.
  20. Re:Would obscurity be a solution? by Glorat · · Score: 5, Informative
    Two issues going on here!

    Ah... the old security through obscurity notion. Someone else can carry the debate here but trying to get security by trying to hide what layers of algorithms you are using is defeating the point of security research. A "secure algorithm" is basically one such that it does not matter whether the hacker has access to the algorithm or not. Cracking a "secure algorithm" should be as hard as cracking by brute force. If your security relies on obscurity, then you are asking for trouble in general

    As for layering in general. Well it works for the most part (e.g 3DES) although there are caveats (2DES would not be safe). But the real point is that layering is slow. Doing 1024-bit RSA encryption is slow. And try generating a 2048-bit key instead of a 1024-bit key. It takes ages (possibly minutes on some computers). You may be increasing security but decreasing performance.

    Now going back to the first point about a "secure algorithm", you are better of say doubling your key size and exponentially increasing the keyspace on your existing algorithm then either inventing your own layering scheme that may or may not work AND will be slow nad memory wasteful by using many algorithms. The short answer is, you don't need layering, just make larger keys.

  21. Arbitrary costing = $1B by Nathdot · · Score: 5, Funny

    I can picture the scenario now:

    <TELEPHONE CORRESPONDANCE>
    SHADY GOVERNMENT OPERATIVE: So how much will this 1024 decryption system cost?
    PIMPLY TEEN HACKER: $1B US dollars to be deposited into my secure off-shore bank account and safe passage to the Maldives.
    SHADY GOVERNMENT OPERATIVE: Excellent. The money is being transferred as we speak. Begin work.
    </TELEPHONE CORRESPONDANCE>

    <PIMPLY TEEN HACKER INTERNAL MONOLOGUE>
    Sweet! I've just charged the US government 1 billion dollars for a beowulf cluster of dreamcasts running home-brew linux.
    </PIMPLY TEEN HACKER INTERNAL MONOLOGUE>

    <SHADY GOVERNMENT OPERATIVE INTERNAL MONOLOGUE>
    Sweet! We will retrieve the 1 billion dollars once we crack the secure off-shore bank account's 1024 bit encryption system
    </SHADY GOVERNMENT OPERATIVE INTERNAL MONOLOGUE>

    :)

  22. Laugh it's funny :-) by lw54 · · Score: 2
    Bernstein released a proposal that outlines the creation of a machine capable of breaking 1024-bit crypto on the order of minutes or even seconds for the measly cost of ~$1B USD.

    Okay, I've been hiding my idea, but who cares. I'm releasing it now and officialy proposing the creation of a machine capable of breaking 2048-bit crypto on the order of hours or even minutes for the measly cost of ~10B USD.

    I'm currently soliciting offers from several major tech companies to fund this joint venture to be used only in the private sector.

    Please call now.

    1. Re:Laugh it's funny :-) by TheLink · · Score: 2

      Factoring difficulty doesn't scale that way because brute force isn't the easiest method. One additional bit doesn't make it twice as hard.

      --
  23. Read the Paper! by gweihir · · Score: 5, Informative

    Actually Bernstein says that he does not expect his factoring device to have any significant speed advantage over other factoring techniques for "short" keys, "short" being significantly more than 1024 bits.

    The reason is that the speed up is asymptotic with a suspected slow convergence.

    But I agree that for security critical application 1024 bits is too short, even if only because there is not enough safety margin.

    Find the paper by D.J. Bernstein here.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted and ignored otherwise.
  24. Guess what else is in danger of compromise?? by Tom7 · · Score: 2


    Hey, I've got a much worse problem to report: Most people don't use encryption!!! Right now, we're all browsing slashdot, our credentials sent in plaintext, our sessions open for anybody to see! Almost everybody sends unencrypted e-mail!

    Rather than freak out about the NSA being able to crack 1024-bit keys, maybe we should be doing more to actually get encryption used by people?

  25. Only a billion dollars? by Futurepower(tm) · · Score: 2


    Only a billion dollars of the taxpayer's money to read other people's mail? The U.S. government will take 10.

    --
    Bush's education improvements were
  26. If you read the letter ..... by taniwha · · Score: 2, Informative

    he sais that the article referenced by slashdot has caused him to re-examine the CUMULATIVE effects of a number different recent development, not just the Bernstein paper

  27. Haha fools!!! by NoMoreNicksLeft · · Score: 4, Funny

    This is why I use 1025 bits. Suckers.

  28. OK... Could Somebody Clue Me In? by istartedi · · Score: 2

    According to an email from Lucky Green

    That key of his seems awfully long. Sure enough, when I pasted it into a text file it was 46 kilobytes!!!

    There must be something else in there besides the 2048-bit key, but what? Is the first part the public key, and the rest the encrypted message?

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  29. Re:But what's a measily $1B for a government agenc by compwizrd · · Score: 2

    Where's the one that tells you to flip the light switch off and on a few times?

  30. Re:But what's a measily $1B for a government agenc by mosch · · Score: 2
  31. Re:Maybe I'm missing something... by rcw-home · · Score: 2
    Exactly WHAT is an agency of the US Gov going to crack that will allow it to gain exactly WHAT money to amortize it's $1B that won't be missed?

    If you've been properly trained in US politics, the phrases "Won't someone please think of the children" and "National Security" should pop into your head immediately.

    Why are we worrying about one billion dollars when having the capability to factor 1024-bit RSA keys could save children's lives?!

  32. Re:But can you prove that they are prime? by ajna · · Score: 3, Funny

    Yes. Use Euler's Theorem, with the extensions by Miller and Rabin. Sorry for being so humorless today.

  33. So, Just try and get people to use Encryption. by Zapdos · · Score: 2

    Everyone here uses gpg or equiv for your email right?
    As a member of several mailing list most people do not even have gpg signatures, those that do never upload their public keys.
    Breaking 1024 bit encrytpion isnt that big of a deal for most people.

    I guess they like running naked through public parks.

  34. Not so fast.. by Sloppy · · Score: 5, Insightful

    The person who builds this machine may still underbid you. The machine doesn't just crack your secrets -- it's reusable. When you amortize the gigabuck over all the different people who need to be spied on, it may yet work out to be less than your minimum bribe.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  35. Threat Assesment by the+eric+conspiracy · · Score: 2

    One thing to consider is that rigorous threat assesment is based on CAPABILITY, not INTENT. Clearly it seems that there now many organizations that may have the capability seriously compromise a significant and growing part of the world economy.

  36. Re:Maybe I'm missing something... by nathanm · · Score: 5, Insightful

    First, it's not that the gov't is cracking encryption of bank systems so they can steal money. The cost of cracking encrypted messages from terrorists, countries they don't like, etc. using this technology would be less than the cost of other intel methods, i.e. getting someone on the inside, not to mention the intangible cost of a human life if an agent were compromised.

    Second, if you'd read the e-mail on Security Focus, the estimated price range is several hundred million dollars to about 1 billion dollars, lower if they have access to a chip fab. It also mentions that the NSA and several other countries' intelligence agencies have their own fabs. So it's not as prohibitively expensive as it sounds. The e-mail's author goes as far as saying The NSA would have to be derelict of duty to not already have built such a decryption device.

  37. Re:Pay attention. Security = risk management. by Sloppy · · Score: 2

    It doesn't cost the bad guys a billion dollars to steal your secret. It costs them a billion dollars to steal the secrets of everyone who uses the type of key the machine can crack. Your share might only be worth $10000 and it could conceivably still be worth their effort to buy/build the machine. Then you lose.

    Your argument only makes sense if they have to dedicate their billion dollars to just cracking one key.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  38. Re:Pay attention. Security = risk management. by Emugamer · · Score: 2

    but if 1024 bit crypto only takes a minute to crack then theoretically during the 3 year life of this 200million to billion dollar machine.
    $2e11 to 1e12 / 3 years / 365 days / 24 hrs /60 minutes

    This means that all of your assets between 124,000 (if machine costs 200 million) and 634,000(for 1 billion) and above are all worthwhile "investments" of this machine's time.

    Thank god I'm poor

  39. Real Issue with encryption by lamj · · Score: 2, Interesting

    We are facing some big challenges right now. Due to the crazy growth of computing power (despite the fact that new methods of calculation - factoring large number and stuff are constant being developed) Encryption standard are being obsolete faster than we can adapt to it.

    Think about how long the US government will take to adopt AES.... Same encryption are going to get weaker and weaker as times goes by, we have to adapt to the rate it fades out. But apparently, encryption standards takes time to develop and get accepted. We are very likely going to change standards every 5-10 years. Government agencies, are you coming along?

  40. Re:Pay attention. Security = risk management. by The+Pim · · Score: 2
    Don't any of you bozos pay attention to prior articles? Security is about risk management.

    What do you see in the post that is inconsistent with this view? It claims that the cost of breaking 1024 bit keys is lower than previously believed. This means that risks must be reassessed.

    If you have something to protect that is worth $1bn for someone to steal and the only protection you have on it is 1024-bit crypto, you deserve to have it stolen.

    Guarding a $1B asset with a 1024 bit key would be foolish, with or without this finding. (For starters, the enemy doesn't necessarily have to build a cracker, they just have to rent time on one.) But who says we were talking about a $1B asset? Trivially, there exists some scenario in which 1024 bits was a good risk prior to this finding, but is no longer. So this finding is entirely relevant to a risk management approach.

    --

    The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.
  41. 2048 bit by MWright · · Score: 3, Informative
    Correct me if I'm wrong, but:


    Each bit that you add roughly doubles the amount of time it takes to crack. 2048-bit encryption, although slow, is possible.


    What this means is that, assuming that a 1024-bit key can be factored in 1 second, it would take roughly
    570044753571256946895391042233962688235025678254 15 606695024759372695\
    54661513856010042759935388366 819543382606540822975 572640467047641318\
    57219835840434659197037569423 594829671728507799344 387665269701556798\
    84895284385512012411993557037 643680409952827613949 299430678049923879\
    77103579392323212688873973370
    years to crack 2048 bit encryption. I'm not all that worried.

    --
    "But really, I think life is just a game of Mao Nomic." -Purplebob
    1. Re:2048 bit by prakashj79 · · Score: 3, Insightful
      A brute force decryption attempt would take roughly twice as much time for every extra bit in the key. No naive decryption scheme will work even if the key size is as low as 128 bits.

      The problem has to be tackled at a more fundamental level - maybe by finding an inherent weakness in the algorithm, which can be used to decrypt the message without having to go through all possible key values.
      For example, if a few (plain text, encrypted text) pairs are known, we can search for a pattern, apply the pattern in reverse to an encrypted message, and get back the original plain text message.

      --
      With profound apologies to whomsoever this sig originally belonged.
    2. Re:2048 bit by jessohyes · · Score: 2, Informative

      IIRC every 10 bits doubles the amount of work requred to break RSA. The reason for this is there are factoring algorithms which can do better than straight brute force.

      The best general-purpose factoring algorithm today is the Number Field Sieve (NFS) [BLP94] [BLZ94], which runs in time approximately O(e1.9(lnn)1/3(lnlnn)2/3). Previously, the most widely used general-purpose algorithm was the Multiple Polynomial Quadratic Sieve (MPQS) [Sil87], which has running time O(e(lnn)1/2(lnlnn)1/2).

  42. Re:Would obscurity be a solution? by sigwinch · · Score: 2
    A "secure algorithm" is basically one such that it does not matter whether the hacker has access to the algorithm or not.
    The point of layering is not to keep the algorithm secret, it's to protect against cryptanalytical breakthroughs. Even if the cryptanalyst gets very lucky (or is very smart) and completely breaks one of the subciphers, the other subciphers still protect your data.
    --

    --
    Kuro5hin.org: where the good times never end. ;-)

  43. Huh??? by TheLink · · Score: 2

    And how do you propose the recipient reads it from the sender's machine?

    Send the message to the recipient in plain HTTP?

    Get the recipient to walk all the way to your hosting site?

    Your self host solution doesn't solve that problem. Or is incomplete at best.

    --
  44. Most of us are safe by mikec · · Score: 2

    Suppose some agency actually did build a machine that could crack 1024-bit RSA. How would they use it? The answer is, they would keep it very secret and use it only on very important stuff---nuclear threats, etc. They would certainly not risk revealing it's existence to crack small cases.

    1. Re:Most of us are safe by perlyking · · Score: 2

      You havent thought this through have you. How will they know whether to decrypt a message or not. How would they know to check terrorist (or communist - choose your fake enemy) cells talking about plans?
      Nah they cant risk that, for the children and for national security they will read everyones, they probably allready are.

      --
      no sig.
  45. a slightly-less-Amerocentric thought... by Simon+Garlick · · Score: 3, Insightful

    How many tyrants and dictators around the world would think NOTHING of squeezing their own countries $1B harder in order to crack the communications of dissidents, opposing political parties, and oppressed ethnic minorities?

    ObDisclaimer: this isn't some pinko commie "FUCK YOU AMERIKKKA!" post... it's just an observation that I haven't yet seen made by another poster in the thread. I see a lot of people talking about the NSA, and breaking into banks, etc etc... but middle-class white male citizens of post-industrial western economies aren't the only people who have good reasons to use crypto, you know?

  46. Shit by loraksus · · Score: 2

    I'll just pay Guido to torture your ass for $10,000. There are other ways of extracting information . . . ironically brute force is an option in both umm professions. . .
    Sort of off topic, but honestly, the investment (for the machine) isn't worth it unless you plan on doing this a lot of times, and if somebody was going to do this on a case by case basis, it would be cheaper to hire one of Pol-pot's henchmen to do the job.

    --
    1q2w3e4r5t6y7u8i9o0pqawsedrftgthyjukilo;p'azsxdcfv gbhnjmk,l.;/
  47. Ian Goldberg isn't worried by SiliconEntity · · Score: 4, Informative
    One of the people to whom Lucky Green attributes the calculation that Bernstein's machine is practical is cryptographer Ian Goldberg. Ian is well known in the crypto community and has broken a number of publicly fielded cryptosystems.

    However, in a follow-up post to the cypherpunks mailing list, Ian said that he did not agree with the calculations.

    In fact he says that the physical properties of the factoring machine seem "implausible", and that there is no reason to believe that the result applies to "real" key lengths like 1024 bit keys.

  48. $1Billion wasted by 0x0d0a · · Score: 2, Funny

    The depressing thing is that probably a few goverments seriously would like to spend $1 billion to try to read something in an RSA encrypted format.

    Yet despite all that money and zillions of man-years being blown on reading stuff in such a format, no one has managed to go out, and no one is willing to spend the money to try to crack .DOC and produce software capable of reading it. A much, much easier problem but one that hasn't been done completely.

    There are so many *smarter* things to blow money on than cryptography that it blows the mind. Cryptography is a fun mind game, but frankly when this much money is being spent on it it's just ridiculous.

    You can bribe the people involved for less than $1 billion. Heck, buy up a private army and take over the building that has the information that you want.

  49. Just think about what they've been doing for years by Ececheira · · Score: 2, Informative

    It is generally regarded that the NSA and the military have technology that is about 20 years, yes 20, ahead of what is publicly known.

    The NSA has the budget to hire the best and brightest mathematicians money can buy. Whose to say that the NSA hasn't know about this for years? Sure, Bernstein could have simply "rediscovered" what the NSA has known for years.

    There have long been rumrors of a $2-3B machine that the NSA has for breaking encryption. Taking time into account, that translates to that $1B machine now.

    The NSA has likely been able to break these keys for years.

  50. 1024-bit RSA is in no danger. Not yet, anyway. by swillden · · Score: 5, Insightful

    Even Bernstein's original paper is clear to point out that while his mathematical results are correct, and that his proposal does allow RSA keys of size n bits to be factored in the time we currently think it takes to crack keys of size n/~3.009, he proved this to be true *only in the asymptotic case*!!

    This means that for very, very large n Bernstein's results are known to hold. His paper is actually a grant proposal requesting funding so that he can spend the next few years finding out if it's possible to apply the same techniques to practical-sized keys. As I understand it, what Bernstein wants to study will still be purely theoretical. He wants to calculate what the savings factor is for smaller keys. The reduction factor for smaller keys may be as large as 3, or it may be smaller but still worthwhile, or it may be negligible.

    Even after Bernstein has done his calculations for smaller keys (which will take years) the results will still be purely theoretical, and there will likely remain a great number of practical challenges in building the rather unique kind of hardware Bernstein is proposing. It's possible that even if the theory holds for smaller keys, building a real machine may still be impractical.

    For more detailed discussion than you're likely to be able to digest, go read sci.crypt.

    From what I've read, I would say that if you have secrets you need to keep for more than 5 years, you might consider using a 2048-bit RSA key, or switching from RSA to ECC.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  51. Re:Pay attention. Security = risk management. by quintessent · · Score: 2

    Heh. You thought I was buying this to get your secrets. No, that's just the icing on the cake. This baby's for LAN parties. Nothing plays Quake quite like it.

    And there's the occasional corporate secrets to bust into once in a while. Ahhh.

    Did I mention Pac Man?

  52. Re:Maybe I'm missing something... by dvdeug · · Score: 2

    SUPPOSE there's a US Govt agency with $1B

    The Department of Defense gets $303B a year.
    See the official budget of the United States Government for 2003.

    Exactly WHAT is an agency of the US Gov going to crack
    that will allow it to gain exactly WHAT money
    to amortize it's $1B
    that won't be missed?


    IIRC, each Stealth bomber costs about a billion dollars. Given the tradeoff between buying a new Stealth fighter, and knowing where to put my current Stealth fighters before my opponent has got a chance to move his armies, I'd pick the latter.

  53. Goof off by kindbud · · Score: 2

    I wish that bum would get back to work and finish Qmail 2.0!!

    --
    Edith Keeler Must Die
  54. Re:But can you prove that they are prime? by cperciva · · Score: 2

    MR does not prove primality. If you assume GRH, then by running MR O((log n)^2) times you can prove primality, but that is impractically slow even for 1024-bit primes.

    All large provable primes are constructed in special forms in order to allow use of one of several fast proving algorithms.

  55. Misleading article by Llanfairpwllgwyngyll · · Score: 4, Informative

    I'm afraid that this story is altogether misleading.

    When the paper first came to prominence, yes, it looked worrying.

    However... the speedup factor appears only to apply to LARGE numbers, not necessarily to smaller ones. Exactly how much advantage one gets for smaller ones is unclear.

    Note that this paper is a "research proposal", not a finished item of research. It's a very interesting read, nevertheless :-)

    However, if you're worried then you should be using 2048-bit original-style RSA PGP keys anyway (or 3072 or even 4096 bit new-style RSA keys). You might want to avoid the DH/DSS keys since the signature part cannot exceed 1024 bit....

    1. Re:Misleading article by pclminion · · Score: 2
      However, if you're worried then you should be using 2048-bit original-style RSA PGP keys anyway (or 3072 or even 4096 bit new-style RSA keys). You might want to avoid the DH/DSS keys since the signature part cannot exceed 1024 bit....

      DSS uses a method similar to ElGamal, which is NOT based on the difficulty of factorization. ElGamal (and DSS) are based on the difficulty of the discrete logarithm problem. Discrete logarithm systems are not affected by this "breakthrough," even if it is one.

    2. Re:Misleading article by Llanfairpwllgwyngyll · · Score: 2

      Sure, that's true. However, my dislike of DSS is not related to the factoring - it's because the size is limited by the standard, and because the covert channel is "unusually large" in DSS (see Schneier's Applied Cryptography).

      The covert channel is in fact big enough to leak up to 10% of the private key per signature if the software is suitably written. Unlike other ways of leaking keys (trojans etc) this leakage is impossible to detect without the numbers chosen to fit the algorithm (ok, yes, you could reverse engineer the code...). Unlike many other ways of leaking information, this one *doesn't* break the interoperability. Sneaky eh?

      Thus, if you are using, say GnuPG, fine - use the published code and it's likely that any such devious mechansim would be noticed. However, if you are using, say PGP "wot no source code available now?" then you cannot be sure.

      As ever, it's all a balancing act - working out which is the greatest risk and dealing with it on a case by case basis....

  56. Re:Price depreciation by arivanov · · Score: 2

    In this case you would not.

    What Schneider has overlooked that the machine in question is not a general purpose parallel machine. It is a specialised simple numerical unit matrix with flat memory architecture. Such beasts with up to 2^16 CPUs have already been designed and have been used for more then 10 years in processing of satellite data. All that is needed here is to up the numerical capabilities of the singele unit, up the number and up the memory interface bandwidth. It is something that can realistically be done in 3-5 years.

    Still, it will remain a relatively specialised beast. The specialised 2^16 parallel hardware used for sat image processing has not depreciated over the last 10 years. Neither will this hardware because it will not become a commodity.

    What is more worrying is that bernstein's model is close to the hardware model of the latest cray proposal (large number of CPUs on flat memory). And this is a commodity machine that money can buy now to be delivered tomorrow. It will not give you as much as the 1B price tag specialised hardware but it is sure worth a try.

    --
    Baker's Law: Misery no longer loves company. Nowadays it insists on it
    http://www.sigsegv.cx/
  57. Quantum Computers aren't real yet by billstewart · · Score: 3, Informative
    There have been a few quantum computers developed, able to get a few bits of resolution (They've done 3 bits, and maybe they're close to 7.) This stuff is still undeveloped rocket-science. It's possible that the Feds have put billions of black-budget dollars into it, but I'd be surprised - it's probably more like small millions of dollars on open research in universities. As with computers, there are some things you can do better in secret, but usually the scale of the open market's research outruns it.

    It'll really be interesting when they start to get to ~64-bits of resolution (at least if they don't run into Heisenberg uncertainty problems when the resolution approaches Planck's constant.) Will the resolution of this technology scale that far? But things don't get interesting for public-key crypto until you're at ~512 bits.

    Also, there are some problems that quantum computers can accelerate and some that it can't. For instance, factoring is tractable, if you've got enough resolution, and there's a quantum computer that was able to factor the number 15 into 5 and 3. So RSA and Diffie-Hellman are toast, at least for 4-bit keys :-) Perhaps for much longer keys, if QC can be developed, but perhaps not. It's not clear whether elliptic curves can be cracked by quantum computers, but then, it's not clear that they can't be cracked by better mathematics.

    Basically, if They can crack everything using public-key technology, you're back to private-key methodology like Kerberos, or traditional methods like one-time pads and guys with Kevlar briefcases handcuffed to their wrists.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  58. Re:Price depreciation by billstewart · · Score: 2

    While it's not going to be on the same price curve as high-volume PC production, there are still Moore's Law effects here - the price/performance of FPGAs and ASICs keeps decreasing as technology improves, and the price of smaller-width chip design keeps improving. The real question is whether the development of this sort of machine can piggyback on other hardware development, plus how motivated is the NSA to build it as further research indicates whether or not it will be really useful...

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  59. Re:so.... by billstewart · · Score: 2

    Your Visa number probably isn't worth spending a $1B to crack, so you don't need to worry. Visa, on the other hand, has to worry about millions of credit card numbers getting stolen, though it's still much easier to crack into most of the machines on the web that absorb credit card numbers, and if there's one master key that lets you steal all of Visa (I doubt there is), it's probably easier to find the people who have parts of that key and bribe them (if you're the Mafia), or subpoena them, if you're the sleazy bunch of thugs at the DoJ who just filed a "Go Fish" subpoena on Visa and American Express.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  60. Re:Then use another Public-Key Algo! by billstewart · · Score: 3, Informative

    Diffie-Hellman and El-Gamal are closely enough related to RSA that you don't get much diversity by picking them. Elliptic Curve is a nice possibility, though it's possible somebody will find the math to crack that. NTRU is a lot different - I don't know that any of the academic cryptographers are calling it really secure yet, but the people who've looked at it don't seem to be calling it "snake oil" either.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  61. Re:Just think about what they've been doing for ye by nagora · · Score: 2
    An interesting point about these theories is that they all assume that the NSA is a competent organisation. There seems to me to be a fair bit of evidence that they are in fact a bunch of self-politicised, bureaucratic, clueless idiots who spend their time and money talking to contractors whose only interest in life is to divest the government of as much money for as little work as possible, usually to a high level of success. 20 years behind sounds more realistic.

    Just a thought.

    TWW

    --
    "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  62. This is a DoS attack by Florian+Weimer · · Score: 2

    This is an attack on the web of trust. The author is spreading FUD to fool people into revoking their keys. If everybody follows his advice, the web of trust is gone, and it will take quite some time to reconstruct it. In the end, revoking keys based on such unsubstantiated threats will water the meaning of key revocation as a whole.

  63. Re:so.... by actiondan · · Score: 2

    Until they actually do it I dont think anyone shoud even care

    How will you know when someone builds this machine and starts actually cracking the encryption? Do you really think 'they' will advertise the fact that they can factor keys in minutes? I find it more likely that 'they' will just quietly read the encrypted messages they want to read - from their point of view the longer people stick with key lengths they can crack, the better.

    The general point is - the safest thing to assume is that once something is theoretically breakable in a practical timeframe, it is broken. Assuming that we will find out when a practical implementation is available seems a little naive.

    Dan.

  64. Re:Would obscurity be a solution? by Sircus · · Score: 2

    Another handy side-effect is that it may make the cracks themselves more difficult. It doesn't apply to breaking RSA (which is just factoring), but many of the best attacks for symmetric ciphers rely on having known plaintext - a file header, or whatever. Since the plaintext in this case would in fact be (hopefully) random ciphertext, the attacker's got a lot less to work with.

    There are disadvantages, of course - you don't know that the two algorithms together are secure, and when considered as a whole, the chances are that they're not more secure. You're relying to a certain extent on the attacker sticking to the rules and considering the supciphers as subciphers, instead of just trying to cryptanalyse the whole mess. The other difficulty is that the more layers you add, the more key material you need - at a certain point, you begin to have trouble getting enough truly random data.

    --
    PenguiNet: the (shareware) Windows SSH client
  65. Re:Would obscurity be a solution? by Shiny+Metal+S. · · Score: 5, Funny
    As for layering in general. Well it works for the most part (e.g 3DES) although there are caveats (2DES would not be safe).
    That's correct. Once I wanted to make ROT13 stronger, so I decided to encrypt the message twice, but I discovered that 2ROT13 was actually less safe than ROT13. I finally used 3ROT13 and even 5ROT13 for the most sensitive data, however I'm not sure how much more secure is 5ROT13 than 3ROT13, but what the hell, the overhead is not very high.
    --

    ~shiny
    WILL HACK FOR $$$

  66. Slashdot already ran this story! by phr2 · · Score: 2
  67. Re:Would obscurity be a solution? by Glorat · · Score: 2

    I'll follow on although you sound like you know about the subject already. Firstly the cryptanalyst may well have more luck breaking the combined layered cipher than trying to break both individually The layered cipher may well be weaker! There is no law that says that if you perform two strong encryptions over a plaintext it is at least as hard as each encryption. This unknown is one reason against. (In practice, layering is "probably safe")

    The next thing is that I strongly doubt that even DES will be "broken" ever. It has been under scrutiny for too long and the only successful attacks are based on brute force and require vast amounts of data for a known-plaintext attack. Brute force... what does that mean? 56-bit breakable today. 128-bit breakable tomorrow. 256-bit breakable... when there are more than 2^256 electrons in the universe! Which there aren't

  68. No need for analysis at all by armb · · Score: 2
    can do much in the way of analysis or reverse engineering of the encryption algorithms used.

    We're talking about RSA here. RSA is a public key algorithm. One where you can give out your public key, keep your private key secret, and anybody can send encrypted messages to you, but only you can decrypt. If you keep your algorithm secret, it becomes totally pointless.

    In general, layering can help, but doesn't always, and can make things worse if you are careless about it. But keeping the layering scheme secret doesn't help much - it's probably equivalent to only a few bits of key, and if it is cracked changing schemes is much tedious than changing keys (and that assumes you _know_ it has been cracked). Making up your own crypto is almost always a really bad idea.

    --
    rant
  69. Re:Then use another Public-Key Algo! by ssimpson · · Score: 2

    Yes! The machine doesn't attack RSA per-se but is a speed up related to the more generic NFS algorithm. NFS similarly works against DLP based problems (e.g. Diffie-Hellman, Elgamal etc).

    --
    "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
  70. Re:Then use another Public-Key Algo! by ssimpson · · Score: 2

    Diffie-Hellman, El Gamal and other similar DLP based algorithms will also be affected by this NFS improvement.


    --
    "Mary had a crypto key, she kept it in escrow, and everything that Mary said, the Feds were sure to know."
  71. better then encryption: invent a language by nalfeshnee · · Score: 2, Interesting

    i thought of putting this in 'ask slashdot' to be honest, but here goes ... what kind of effort is required to invent a reasonably efficient language which of course only you and your confederates would be able to use. esperanto, es an example, required a mere *eight* years.

    the advantage with this is that it requires practically no encryption, if any.

    "jan? khlaz tuirt'kah dar gangan Mbou!"

    any idea what it means? nope, me either. and if you want an example of how strong this kind of 'encryption' is, simply take a look at the puzzles linguistics has tried to crack over the years: Linear B, (Linear A is still a mystery), hieroglyphics, etc., etc. For an example of something which is *still in plaintext and not deciphered*, check out the Voynich Manuscript.

    OK, I'm not saying that one can simply go off and invent a perfect language in a coupla weeks, but look at the pseudo-languages like Elvish, Klingon and whatnot. Ideas, criticisms, reactions??

    Plus of course, if someone is holding a cattleprod to your crown jewels and you're standing in a bucket of water, it doesn't *really* matter whether u used gazillion-bit keys anyway...

    nalfy

    --

    -- Despair is an operating system that ANY human being can run, sort of a psychological JAVA --

  72. Re:But can you prove that they are prime? by bluGill · · Score: 2

    Yes I can prove they are prime. Well, I can prove they are Newton primes anyway. Meaning if I say it is prime, I'm right most of the time. When I wrong, it won't affect the quality of my encryption (that we know of, though someone that is newton prime, but not prime is belived the reduce security, nobody has proved that to my knowledge)

  73. Re:Huh? Very Dead? by Pii · · Score: 2
    Obligatory Princess Bride Dialog:
    MIRACLE MAX - Look who knows so much. Well, it just so happens that your friend here is only mostly dead. There's a big difference between mostly dead and all dead. Please open his mouth.

    [Inigo does. Max inserts the bellows in Westley's mouth and starts to pump.]

    MIRACLE MAX - Now, mostly dead is slightly alive. Now, all dead...well, with all dead, there's usually only one thing that you can do.

    INIGO - What's that?

    [He stops pumping.] MIRACLE MAX - Go through his clothes and look for loose change.

    --
    For those that would die defending it, Freedom
    has a sweet taste that the protected will never know.
  74. Re:Layering by Glorat · · Score: 2

    I don't quite understand your question there (running through DES with unknown key... extra encryption reducing security) but I'll try to say something helpful

    Ok, I'd better disclaim IANACE (crytography expert). I've studied the subject at university level so I know the defintions and have read the facts but have done no analysis myself.

    Cracking DES-64 is "easy". Now which is harder to break of these two? DES-64 performed twice with two different keys or DES-128? As it turns out, both are using 128bits worth of key. I would rather use DES-128 on principle since 2^128 is a big key space and current DES breaking difficulty is in the order of brute force as far as I know.

    Now what about DES-64 twice? Well, as it turns you might be safe with DES (because I think some people have found it is not a group) BUT suppose we weren't using DES but a symmetric algorithm that *is* a group. Then the hacker could just do a brute force attack on your code with a *64* bit key.

    The thing is, I am just touching the surface here. In this case, I have showed that layering using the same cipher that is a group is BAD. Now you could argue, different ciphers etc. etc. but that *may* introduce weaknesses. To know, you would need to analyse it! But why bother when DES and the like have already been analysed to death so you can be fairly sure you are safe at larger key lengths

  75. You *assholes* by tqbf · · Score: 2
    Don't any of you read sci.crypt?

    Dan Bernstein has been yelling for the past few weeks since he published nfscircuit that his work does not yet apply to 1024 bit keys (or other "realistically" small key sizes).

    In spite of that, stories like this one keep popping up, forcing him to defend himself from idiots who construct bogus straw-man analyses against points that he hasn't even made.

    I would rather see Bernstein continue this work, and have knowledgeable people peer-review it, rather than see people waste their time discussing whether solar cells cost more money than AC power (an argument DJB had to get involved in on sci.crypt) and other such lunacy.

  76. Re:Would obscurity be a solution? by hymie3 · · Score: 2

    If you wanted to mask the fact that you were using 5ROT13 instead of 3ROT13, you could XOR the message after each application of ROT13. How would you write that?
    5XORROT13?
    Looks like something my old admin would have thought was a swell password....

  77. Re:Would obscurity be a solution? by sigwinch · · Score: 2
    Firstly the cryptanalyst may well have more luck breaking the combined layered cipher than trying to break both individually The layered cipher may well be weaker!
    If the subciphers are independently keyed, the overall cipher is at least as strong as the weakest subcipher.
    Brute force... what does that mean? 56-bit breakable today. 128-bit breakable tomorrow. 256-bit breakable... when there are more than 2^256 electrons in the universe!
    Key length means nothing if you can find analytical attacks. A primary worry is automated theorem provers, which can pull structure out of provably chaotic systems--witness the equation that calculates an arbitrary binary digit of pi without calculating any other digits. If strong AIs are developed, who knows what could be analyzed...

    I think it's likely that vulnerabilities will be discovered in some ciphers as better analytical tools become available. Layering ciphers can mitigate this problem, and it doesn't cost much.

    --

    --
    Kuro5hin.org: where the good times never end. ;-)

  78. Re:Would obscurity be a solution? by Glorat · · Score: 2

    If the subciphers are independently keyed, the overall cipher is at least as strong as the weakest subcipher
    In almost all cases, yes. But not if the two ciphers are a group, for example.

    Key length means nothing if you can find analytical attacks.
    True also but one could just as well find an analytical attack in the combined layered cipher if a "poor" choice in ciphers is chosen

    Basically, if I had to choose what cipher to use, I think it is more likely that I would make a mistake in choosing a poor combination of ciphers to layer than I would someone finding an analytical attack in a cipher that has been analysed for decades.

    The fact is, both layering and key-growing are both valid and are both used. I just happen to prefer one over the other ;)

  79. Re:Would obscurity be a solution? by ipfwadm · · Score: 2, Funny

    5XORROT13

    Damn... that's the combination on my luggage!