Slashdot Mirror


Parallel Algorithm Leads To Crypto Breakthrough

Hugh Pickens writes "Dr. Dobbs reports that a cracking algorithm using brute force methods can analyze the entire DES 56-bit keyspace with a throughput of over 280 billion keys per second, the highest-known benchmark speeds for 56-bit DES decryption and can accomplish a key recovery that would take years to perform on a PC, even with GPU acceleration, in less than three days using a single, hardware-accelerated server with a cluster of 176 FPGAs. The massively parallel algorithm iteratively decrypts fixed-size blocks of data to find keys that decrypt into ASCII numbers. Candidate keys that are found in this way can then be more thoroughly tested to determine which candidate key is correct." Update by timothy, 2010-01-29 19:05 GMT: Reader Stefan Baumgart writes to point out prior brute-force methods using reprogrammable chips, including Copacobana (PDF), have achieved even shorter cracking times for DES-56. See also this 2005 book review of Brute Force, about the EFF's distributed DES-breaking effort that succeeded in 1997 in cracking a DES-encrypted message. "'This DES cracking algorithm demonstrates a practical, scalable approach to accelerated cryptography,' says David Hulton, an expert in code cracking and cryptography. 'Previous methods of acceleration using clustered CPUs show increasingly poor results due to non-linear power consumption and escalating system costs as more CPUs are added. Using FPGAs allows us to devote exactly the amount of silicon resources needed to meet performance and cost goals, without incurring significant parallel processing overhead.' Although 56-bit DES is now considered obsolete, having been replaced by newer and more secure Advanced Encryption Standard (AES) encryption methods, DES continues to serve an important role in cryptographic research, and in the development and auditing of current and future block-based encryption algorithms."

7 of 186 comments (clear)

  1. Re:searching for ASCII by 2.7182 · · Score: 3, Funny

    Agreed! Also what I do, is before I encode is to switch 1 to 0 and 0 to 1. That'll really confuse'em!

  2. Re:searching for ASCII by Arancaytar · · Score: 4, Funny

    Me, I let a Navaho code talker read out the bit stream before transmission.

  3. Re:searching for ASCII by rubycodez · · Score: 3, Funny

    I rot-13 everything first, and then I go the extra mile and do it again, cause you can't be too sure

  4. Re:What? by Colin+Smith · · Score: 3, Funny

    I mean, yes, his DES-cracking hardware is about 800x faster than a PC. Where's the "Crypto Breakthrough"?

    He noticed the previous researcher's "sleep" statements.

     

    --
    Deleted
  5. Re:What? by QuoteMstr · · Score: 4, Funny

    I guess "Interesting Thing This Guy Did with Numbers n' Shit" just doesn't have quite the newsworthy ring to it.

    Nah, if we adhered to normal journalistic conventions, the headline would read something like "Man Causes Pig to Fly using Homemade Rocket".

    Or if this were the New York Times, "In New Development, Swine's Aerial an Inspiration to All" and an editorial the next day, an editorial "Pigs Must Fly Farther, Higher", paired with "Opinionator: Will the Pig Land? Experts Divided. Join the Discussion."

    (Then, on Monday, Krugman's "Why we Need Swine Flight Credits" and Ross Douthat's "When will This Liberal Pig Eat Your Children?")

  6. Re:searching for ASCII by JustOK · · Score: 3, Funny

    I do rot-6.5, but I do it four times.

    --
    rewriting history since 2109
  7. Re:searching for ASCII by Arthur+Grumbine · · Score: 3, Funny

    I rot-13 everything first, and then I go the extra mile and do it again, cause you can't be too sure

    I do rot-6.5, but I do it four times.

    You guys are both doing it wrong - wasting CPU cycles to get that additional security. I just do one pass with ROT-26.

    --
    Now that I think about it, I'm pretty sure everything I just said is completely wrong.