1. 25 5月, 2015 1 次提交
  2. 22 5月, 2015 3 次提交
    • H
      crypto: aead - Add support for new AEAD implementations · 63293c61
      Herbert Xu 提交于
      This patch adds the basic structure of the new AEAD type.  Unlike
      the current version, there is no longer any concept of geniv.  IV
      generation will still be carried out by wrappers but they will be
      normal AEAD algorithms that simply take the IPsec sequence number
      as the IV.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      63293c61
    • H
      crypto: aead - Rename aead_alg to old_aead_alg · 2d0f230f
      Herbert Xu 提交于
      This patch is the first step in the introduction of a new AEAD
      alg type.  Unlike normal conversions this patch only renames the
      existing aead_alg structure because there are external references
      to it.
      
      Those references will be removed after this patch.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      2d0f230f
    • H
      crypto: aead - Add new interface with single SG list · 996d98d8
      Herbert Xu 提交于
      The primary user of AEAD, IPsec includes the IV in the AD in
      most cases, except where it is implicitly authenticated by the
      underlying algorithm.
      
      The way it is currently implemented is a hack because we pass
      the data in piecemeal and the underlying algorithms try to stitch
      them back up into one piece.
      
      This is why this patch is adding a new interface that allows a
      single SG list to be passed in that contains everything so the
      algorithm implementors do not have to stitch.
      
      The new interface accepts a single source SG list and a single
      destination SG list.  Both must be laid out as follows:
      
      	AD, skipped data, plain/cipher text, ICV
      
      The ICV is not present from the source during encryption and from
      the destination during decryption.
      
      For the top-level IPsec AEAD algorithm the plain/cipher text will
      contain the generated (or received) IV.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      996d98d8
  3. 13 5月, 2015 1 次提交
    • H
      crypto: aead - Convert top level interface to new style · 5d1d65f8
      Herbert Xu 提交于
      This patch converts the top-level aead interface to the new style.
      All user-level AEAD interface code have been moved into crypto/aead.h.
      
      The allocation/free functions have switched over to the new way of
      allocating tfms.
      
      This patch also removes the double indrection on setkey so the
      indirection now exists only at the alg level.
      
      Apart from these there are no user-visible changes.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      5d1d65f8
  4. 01 8月, 2014 1 次提交
  5. 11 1月, 2008 2 次提交
    • H
      [CRYPTO] aead: Add top-level givencrypt/givdecrypt calls · 3a282bd2
      Herbert Xu 提交于
      This patch finally makes the givencrypt/givdecrypt operations available
      to users by adding crypto_aead_givencrypt and crypto_aead_givdecrypt.
      A suite of helpers to allocate and fill in the request is also available.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      3a282bd2
    • H
      [CRYPTO] aead: Add givcrypt operations · 743edf57
      Herbert Xu 提交于
      This patch adds the underlying givcrypt operations for aead and associated
      support elements.  The rationale is identical to that of the skcipher
      givcrypt operations, i.e., sometimes only the algorithm knows how the
      IV should be generated.
      
      A new request type aead_givcrypt_request is added which contains an
      embedded aead_request structure with two new elements to support this
      operation.  The new elements are seq and giv.  The seq field should
      contain a strictly increasing 64-bit integer which may be used by
      certain IV generators as an input value.  The giv field will be used
      to store the generated IV.  It does not need to obey the alignment
      requirements of the algorithm because it's not used during the operation.
      
      The existing iv field must still be available as it will be used to store
      intermediate IVs and the output IV if chaining is desired.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      743edf57