1. 26 10月, 2013 1 次提交
  2. 26 9月, 2013 2 次提交
  3. 25 9月, 2013 2 次提交
  4. 21 8月, 2013 1 次提交
  5. 25 4月, 2013 1 次提交
  6. 03 4月, 2013 1 次提交
  7. 06 12月, 2012 1 次提交
  8. 15 10月, 2012 1 次提交
  9. 08 10月, 2012 2 次提交
    • D
      KEYS: Provide signature verification with an asymmetric key · 4ae71c1d
      David Howells 提交于
      Provide signature verification using an asymmetric-type key to indicate the
      public key to be used.
      
      The API is a single function that can be found in crypto/public_key.h:
      
      	int verify_signature(const struct key *key,
      			     const struct public_key_signature *sig)
      
      The first argument is the appropriate key to be used and the second argument
      is the parsed signature data:
      
      	struct public_key_signature {
      		u8 *digest;
      		u16 digest_size;
      		enum pkey_hash_algo pkey_hash_algo : 8;
      		union {
      			MPI mpi[2];
      			struct {
      				MPI s;		/* m^d mod n */
      			} rsa;
      			struct {
      				MPI r;
      				MPI s;
      			} dsa;
      		};
      	};
      
      This should be filled in prior to calling the function.  The hash algorithm
      should already have been called and the hash finalised and the output should
      be in a buffer pointed to by the 'digest' member.
      
      Any extra data to be added to the hash by the hash format (eg. PGP) should
      have been added by the caller prior to finalising the hash.
      
      It is assumed that the signature is made up of a number of MPI values.  If an
      algorithm becomes available for which this is not the case, the above structure
      will have to change.
      
      It is also assumed that it will have been checked that the signature algorithm
      matches the key algorithm.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      4ae71c1d
    • D
      KEYS: Asymmetric public-key algorithm crypto key subtype · a9681bf3
      David Howells 提交于
      Add a subtype for supporting asymmetric public-key encryption algorithms such
      as DSA (FIPS-186) and RSA (PKCS#1 / RFC1337).
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      a9681bf3
  10. 07 9月, 2012 2 次提交
  11. 01 8月, 2012 3 次提交
  12. 29 3月, 2012 1 次提交
  13. 20 3月, 2012 1 次提交
  14. 21 11月, 2011 1 次提交
    • J
      crypto: serpent-sse2 - add lrw support · 18482053
      Jussi Kivilinna 提交于
      Patch adds LRW support for serpent-sse2 by using lrw_crypt(). Patch has been
      tested with tcrypt and automated filesystem tests.
      
      Tcrypt benchmarks results (serpent-sse2/serpent_generic speed ratios):
      
      Benchmark results with tcrypt:
      
      Intel Celeron T1600 (x86_64) (fam:6, model:15, step:13):
      size    lrw-enc lrw-dec
      16B     1.00x   0.96x
      64B     1.01x   1.01x
      256B    3.01x   2.97x
      1024B   3.39x   3.33x
      8192B   3.35x   3.33x
      
      AMD Phenom II 1055T (x86_64) (fam:16, model:10):
      size    lrw-enc lrw-dec
      16B     0.98x   1.03x
      64B     1.01x   1.04x
      256B    2.10x   2.14x
      1024B   2.28x   2.33x
      8192B   2.30x   2.33x
      
      Intel Atom N270 (i586):
      size    lrw-enc lrw-dec
      16B     0.97x   0.97x
      64B     1.47x   1.50x
      256B    1.72x   1.69x
      1024B   1.88x   1.81x
      8192B   1.84x   1.79x
      Signed-off-by: NJussi Kivilinna <jussi.kivilinna@mbnet.fi>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      18482053
  15. 09 11月, 2011 5 次提交
  16. 21 10月, 2011 1 次提交
  17. 22 9月, 2011 1 次提交
  18. 16 8月, 2011 1 次提交
    • H
      crypto: sha - Fix build error due to crypto_sha1_update · 4619b6bd
      Herbert Xu 提交于
      On Tue, Aug 16, 2011 at 03:22:34PM +1000, Stephen Rothwell wrote:
      >
      > After merging the final tree, today's linux-next build (powerpc
      > allyesconfig) produced this warning:
      >
      > In file included from security/integrity/ima/../integrity.h:16:0,
      >                  from security/integrity/ima/ima.h:27,
      >                  from security/integrity/ima/ima_policy.c:20:
      > include/crypto/sha.h:86:10: warning: 'struct shash_desc' declared inside parameter list
      > include/crypto/sha.h:86:10: warning: its scope is only this definition or declaration, which is probably not what you want
      >
      > Introduced by commit 7c390170 ("crypto: sha1 - export sha1_update for
      > reuse").  I guess you need to include crypto/hash.h in crypto/sha.h.
      
      This patch fixes this by providing a declaration for struct shash_desc.
      Reported-by: NStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      4619b6bd
  19. 10 8月, 2011 1 次提交
  20. 22 6月, 2011 1 次提交
    • A
      net: remove mm.h inclusion from netdevice.h · b7f080cf
      Alexey Dobriyan 提交于
      Remove linux/mm.h inclusion from netdevice.h -- it's unused (I've checked manually).
      
      To prevent mm.h inclusion via other channels also extract "enum dma_data_direction"
      definition into separate header. This tiny piece is what gluing netdevice.h with mm.h
      via "netdevice.h => dmaengine.h => dma-mapping.h => scatterlist.h => mm.h".
      Removal of mm.h from scatterlist.h was tried and was found not feasible
      on most archs, so the link was cutoff earlier.
      
      Hope people are OK with tiny include file.
      
      Note, that mm_types.h is still dragged in, but it is a separate story.
      Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b7f080cf
  21. 07 1月, 2011 1 次提交
  22. 02 12月, 2010 1 次提交
  23. 19 11月, 2010 1 次提交
    • H
      crypto: af_alg - User-space interface for Crypto API · 03c8efc1
      Herbert Xu 提交于
      This patch creates the backbone of the user-space interface for
      the Crypto API, through a new socket family AF_ALG.
      
      Each session corresponds to one or more connections obtained from
      that socket.  The number depends on the number of inputs/outputs
      of that particular type of operation.  For most types there will
      be a s ingle connection/file descriptor that is used for both input
      and output.  AEAD is one of the few that require two inputs.
      
      Each algorithm type will provide its own implementation that plugs
      into af_alg.  They're keyed using a string such as "skcipher" or
      "hash".
      
      IOW this patch only contains the boring bits that is required
      to hold everything together.
      
      Thakns to Miloslav Trmac for reviewing this and contributing
      fixes and improvements.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Acked-by: NDavid S. Miller <davem@davemloft.net>
      Tested-by: NMartin Willi <martin@strongswan.org>
      03c8efc1
  24. 18 10月, 2010 1 次提交
  25. 20 9月, 2010 1 次提交
  26. 19 5月, 2010 1 次提交
    • D
      crypto: skcipher - Add ablkcipher_walk interfaces · bf06099d
      David S. Miller 提交于
      These are akin to the blkcipher_walk helpers.
      
      The main differences in the async variant are:
      
      1) Only physical walking is supported.  We can't hold on to
         kmap mappings across the async operation to support virtual
         ablkcipher_walk operations anyways.
      
      2) Bounce buffers used for async more need to be persistent and
         freed at a later point in time when the async op completes.
         Therefore we maintain a list of writeback buffers and require
         that the ablkcipher_walk user call the 'complete' operation
         so we can copy the bounce buffers out to the real buffers and
         free up the bounce buffer chunks.
      
      These interfaces will be used by the new Niagara2 crypto driver.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      bf06099d
  27. 17 1月, 2010 1 次提交
  28. 07 1月, 2010 1 次提交
  29. 19 10月, 2009 2 次提交