Slashdot Mirror


New Attack Against Multiple Encryption Functions

An anonymous reader sends word of a paper presented a few days back by Adi Shamir, the S in RSA, that promises a new form of mathematical attack against a broad range of cryptographic ciphers. The computerworld.com.au report leans heavily on Schneier's blog entry from the Crypto 2008 conference and the attached comments. Shamir's paper has not been published yet. "[The new attack could affect] hash functions (such as MD5, SHA-256), stream ciphers (such as RC4), and block ciphers (such as DES, Triple-DES, AES) at the Crypto 2008 conference. The new method of cryptanalysis has been called a 'cube attack' and formed part of Shamir's invited presentation at Crypto 2008 — 'How to solve it: New Techniques in Algebraic Cryptanalysis.' The new attack method isn't necessarily going to work against the exact ciphers listed above, but it offers a new generic attack method that can target basically formed ciphers irrespective of the basic cipher method in use, provided that it can be described in a 'low-degree polynomial equation'... What may be the biggest outcome from this research is the range of devices in widespread use that use weaker cryptographic protection, due to power or size limitations, that are now vulnerable to a straightforward mathematical attack."

11 of 130 comments (clear)

  1. Ha! I'm immune! by DikSeaCup · · Score: 5, Funny

    I store all of my passwords in plain text!

  2. Re:ehm by moderatorrater · · Score: 5, Informative

    The summary is blatantly wrong. Take a look at the schneier blog post (from 3 days ago) and the second update: this attack only works against LSFR encryption of a low order, which means that none of the schemes mentioned in the summary are actually affected.

    Now, if I were to actually RTFA, I would know whether the article was slow on the uptake or slashdot, and whether or not they should have known that the attack wouldn't affect the major algorithms, just smaller ones. Either Slashdot's dead wrong on this or computerworld is, and I'm not sure which one's more likely.

  3. Correct the summary/FUD by trifish · · Score: 5, Informative

    As Schneier wrote (emphasis mine): "this attack doesn't apply to any block cipher -- DES, AES, Blowfish, Twofish, anything else -- in common use; their degree is much too high." Now, correct the misleading summary (or be uninformed FUD spreader like Computerworld).

    1. Re:Correct the summary/FUD by secPM_MS · · Score: 5, Informative
      The "low degree" here may be a bit higher than most readers suspect. The abstract I have for the talk is:

      ABSTRACT: In this talk I will describe a new algebraic attack which is very powerful and very general. It can solve large systems of low degree polynomial equations with surprisingly low complexity. For example, solving dense random-looking equations of degree 16 in several thousand variables over GF(2) (which correspond to many types of LFSR-based stream ciphers) can now be practically done in less than 2^{32} complexity by the new technique.

      That said, the algebraic degree associated with modern block codes is far beyond this. The possible uility of such approaches in reducing the complexity of collision generation in hashes is yet undetermined.

  4. Re:The synopsis stated "low grade" crypto by eudaemon · · Score: 5, Insightful

    The reason to casually encrypt phone calls or any other data is to prevent the casual snooping of same.

    Look at this way -- the barrier to entry for snooping your data is very low, and getting lower with each
    new executive order. On the other hand the barrier to entry on snooping your data can be set arbitrarily high;
    you can choose anything from 56 bit single-DES to 2048 bit RC4. The effort required to casually snoop you for
    no other reason has now exploded. It was fear of people adopting this strategy and blocking the casual snooping
    that inspired the clipper chip. It was the people's laziness, ignorance or both towards protecting their privacy
    and their fear of terror that has eroded any expectation of privacy now, which is truly unfortunate.

    If we had an expectation of privacy in this country, I think things would be very different now with regards to
    all the second order effects such as identity theft.

  5. Re:Ha! I'm immune! by oahazmatt · · Score: 5, Funny

    I do one better. I use inkblot tests. I can leave them in plain sight and their totally secure.

    Co-worker: Your password is "flower"?
    Me: What? No. It's "zombie clown hitting fish with hammer". What's wrong with you?

    --
    Those who believe the Internet is private,
    find their privates are on the Internet.
  6. Re:disgusting fatbodies by thedonger · · Score: 5, Funny

    I'm sure this post is encrypted...If only there were a way to use Schneier's algorithm...Wait...Got it! Here is the decrypted text:

    Yes, I agree with moderatorrater. It appears Slashdot was jumping the gun. I like to ride mopeds.

    --
    Help fight poverty: Punch a poor person.
  7. Re:Ha! I'm immune! by iminplaya · · Score: 5, Funny

    Me too. It's ******

    --
    What?
  8. Re:Ha! I'm immune! by jam244 · · Score: 5, Funny

    Your password is hunter2?

  9. Re:ehm by MightyMartian · · Score: 5, Funny

    Nonsense. The real solution is to get a court order banning the guy from giving his presentation. After all, as has been demonstrated just recently, court orders are the preferred means of securing anything.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  10. Re:DES, AES, Blowshifh, twofish likely immune by Anonymous Coward · · Score: 5, Informative

    While finding collisions quickly does indeed show MD5 has weaknesses, no one has found a efficient way to match an existing checksum. For most that's the definition of completely broken.