1. 23 6月, 2012 4 次提交
  2. 22 6月, 2012 4 次提交
  3. 21 6月, 2012 5 次提交
  4. 20 6月, 2012 3 次提交
  5. 19 6月, 2012 9 次提交
  6. 18 6月, 2012 3 次提交
  7. 17 6月, 2012 2 次提交
  8. 16 6月, 2012 1 次提交
    • G
      md5: consistently use uint32_t instead of unsigned int · c78cf00b
      Giorgio Vazzana 提交于
      Basically to make code clearer and adherent to the
      standard. RFC 1321, on page 2 states
      
      Let the symbol "+" denote addition of words (i.e., modulo-2^32
      addition). Let X <<< s denote the 32-bit value obtained by circularly
      shifting (rotating) X left by s bit positions.
      
      on page 3, section 3.3 states:
      
      A four-word buffer (A,B,C,D) is used to compute the message digest.
      Here each of A, B, C, D is a 32-bit register.
      
      so the algorithm needs to work with integers that are exactly 32bits
      in length. And indeed in struct AVMD5 the MD buffer is declared as
      "uint32_t ABCD[4];", while in the function that performs the block
      transformation the state variables were "unsigned int"s. On
      architectures where sizeof(unsigned int) != sizeof(uint32_t) this
      could be a problem, although I can't name such an architecture from
      the top of my head.
      On a side note, both the reference implementation in RFC 1321 and the
      gnulib implementation (used by md5sum program on GNU systems) use
      uint32_t in the transform function.
      Signed-off-by: NMichael Niedermayer <michaelni@gmx.at>
      c78cf00b
  9. 15 6月, 2012 2 次提交
  10. 14 6月, 2012 1 次提交
  11. 13 6月, 2012 1 次提交
  12. 12 6月, 2012 5 次提交