Ok, let's see this graph again. Fig 13 shows that throughoutput of SHA512 was 616Mbit/s comparing to 91Mbit/s for 3DES. As we talking about breaking password, we interested in number of encryptions per second, not in throughoutput. SHA512 block size 512 bit which gives us 1203125 encryptions/s. 3DES block size 64 bit, that's 1421875 3DES encryptions/s or 4265625 DES encryptions/s. And this turns your 6 coefficient into 0.28. Now, reading description of tests in you can see that they were hashing 3MB of data, which means that they probably used 3DES in CBC mode, so couldn't use many optimisations, like e.g. parallel encryption of several blocks. Note also that Fig 12 shows that SHA512 implementation used 23% of FPGA slices, twice as much as SHA1 implementation (not counting IO slices), and document says nothing about 3DES.

Summarising:

  1. SHA512 in [1] was 3.5 times slower than DES
  2. you're not taking into account number of slices required to implement SHA512 and DES
  3. [1] is about hashing data stream, copacobana is about key search. [1] doesn't allow parallel operations, copacobana does.

And based on that I think your estimation sucks

[1] http://www.east.isi.edu/~bschott/pubs/grembowski02comparative.pdf

In reply to Re^14: SaltedDigest Salt? by zwon
in thread SaltedDigest Salt? by packetstormer

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.