3 ms·

Quoth the parent: "It does not apply here"

• tptacek 14y ago
  Sure. The flaw here isn't strcmp. In fact, most crypto compares don't use strcmp, even in naive code; an HMAC-SHA1 MAC, for instance, is an array of 8-bit bytes, not the hex string that programs encode them into for human consumption. "memcmp" is the normal culprit. Timing attacks aren't a flaw in memcmp or strcmp. Touching every byte of a string is stupid behavior in the overwhelming majority of cases.
  • Xuzz 14y ago
    Unless, of course, you're Nintendo: http://wiibrew.org/wiki/Signing_bug http://wiibrew.org/wiki/Signing_bug
    • tptacek 14y ago
      Good find. Again, notice how the problem here isn't strcmp or it's timing behavior; it's mistakenly using ASCIIZ strings to hold ciphertext.