1. 11 1月, 2008 1 次提交
    • J
      [CRYPTO] ctr: Add CTR (Counter) block cipher mode · 23e353c8
      Joy Latten 提交于
      This patch implements CTR mode for IPsec.
      It is based off of RFC 3686.
      
      Please note:
      1. CTR turns a block cipher into a stream cipher.
      Encryption is done in blocks, however the last block
      may be a partial block.
      
      A "counter block" is encrypted, creating a keystream
      that is xor'ed with the plaintext. The counter portion
      of the counter block is incremented after each block
      of plaintext is encrypted.
      Decryption is performed in same manner.
      
      2. The CTR counterblock is composed of,
              nonce + IV + counter
      
      The size of the counterblock is equivalent to the
      blocksize of the cipher.
              sizeof(nonce) + sizeof(IV) + sizeof(counter) = blocksize
      
      The CTR template requires the name of the cipher
      algorithm, the sizeof the nonce, and the sizeof the iv.
              ctr(cipher,sizeof_nonce,sizeof_iv)
      
      So for example,
              ctr(aes,4,8)
      specifies the counterblock will be composed of 4 bytes
      from a nonce, 8 bytes from the iv, and 4 bytes for counter
      since aes has a blocksize of 16 bytes.
      
      3. The counter portion of the counter block is stored
      in big endian for conformance to rfc 3686.
      Signed-off-by: NJoy Latten <latten@austin.ibm.com>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      23e353c8
  2. 27 10月, 2007 1 次提交
  3. 26 10月, 2007 1 次提交
  4. 23 10月, 2007 1 次提交
  5. 11 10月, 2007 2 次提交
  6. 18 5月, 2007 1 次提交
  7. 02 5月, 2007 1 次提交
  8. 21 3月, 2007 1 次提交
  9. 07 2月, 2007 4 次提交
  10. 07 12月, 2006 2 次提交
  11. 21 9月, 2006 6 次提交
  12. 26 6月, 2006 2 次提交
  13. 07 1月, 2006 1 次提交
  14. 30 10月, 2005 2 次提交
  15. 02 9月, 2005 1 次提交
  16. 23 6月, 2005 5 次提交
  17. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4