1. 08 Jul, 2018 1 commit
    • Eric Biggers's avatar
      crypto: shash - remove useless setting of type flags · e50944e2
      Eric Biggers authored
      Many shash algorithms set .cra_flags = CRYPTO_ALG_TYPE_SHASH.  But this
      is redundant with the C structure type ('struct shash_alg'), and
      crypto_register_shash() already sets the type flag automatically,
      clearing any type flag that was already there.  Apparently the useless
      assignment has just been copy+pasted around.
      So, remove the useless assignment from all the shash algorithms.
      This patch shouldn't change any actual behavior.
      Signed-off-by: default avatarEric Biggers <[email protected]>
      Signed-off-by: default avatarHerbert Xu <[email protected]>
  2. 13 Jan, 2015 1 commit
    • Mathias Krause's avatar
      crypto: add missing crypto module aliases · 3e14dcf7
      Mathias Krause authored
      Commit 5d26a105 ("crypto: prefix module autoloading with "crypto-"")
      changed the automatic module loading when requesting crypto algorithms
      to prefix all module requests with "crypto-". This requires all crypto
      modules to have a crypto specific module alias even if their file name
      would otherwise match the requested crypto algorithm.
      Even though commit 5d26a105 added those aliases for a vast amount of
      modules, it was missing a few. Add the required MODULE_ALIAS_CRYPTO
      annotations to those files to make them get loaded automatically, again.
      This fixes, e.g., requesting 'ecb(blowfish-generic)', which used to work
      with kernels v3.18 and below.
      Also change MODULE_ALIAS() lines to MODULE_ALIAS_CRYPTO(). The former
      won't work for crypto modules any more.
      Fixes: 5d26a105 ("crypto: prefix module autoloading with "crypto-"")
      Cc: Kees Cook <[email protected]>
      Signed-off-by: default avatarMathias Krause <[email protected]>
      Signed-off-by: default avatarHerbert Xu <[email protected]>
  3. 24 Nov, 2014 1 commit
  4. 17 Oct, 2014 1 commit
    • Daniel Borkmann's avatar
      crypto: memzero_explicit - make sure to clear out sensitive data · 7185ad26
      Daniel Borkmann authored
      Recently, in commit 13aa93c70e71 ("random: add and use memzero_explicit()
      for clearing data"), we have found that GCC may optimize some memset()
      cases away when it detects a stack variable is not being used anymore
      and going out of scope. This can happen, for example, in cases when we
      are clearing out sensitive information such as keying material or any
      e.g. intermediate results from crypto computations, etc.
      With the help of Coccinelle, we can figure out and fix such occurences
      in the crypto subsytem as well. Julia Lawall provided the following
      Coccinelle program:
        type T;
        identifier x;
        T x;
        ... when exists
            when any
        ... when != x
            when strict
        type T;
        identifier x;
        T x[...];
        ... when exists
            when any
        ... when != x
            when strict
      Therefore, make use of the drop-in replacement memzero_explicit() for
      exactly such cases instead of using memset().
      Signed-off-by: default avatarDaniel Borkmann <[email protected]>
      Cc: Julia Lawall <[email protected]>
      Cc: Herbert Xu <[email protected]>
      Cc: Theodore Ts'o <[email protected]>
      Cc: Hannes Frederic Sowa <[email protected]>
      Acked-by: default avatarHannes Frederic Sowa <[email protected]>
      Acked-by: default avatarHerbert Xu <[email protected]>
      Signed-off-by: Theodore Ts'o's avatarTheodore Ts'o <[email protected]>
  5. 01 Aug, 2012 1 commit
  6. 25 Dec, 2008 1 commit
  7. 21 Apr, 2008 1 commit
    • Kamalesh Babulal's avatar
      [CRYPTO] all: Clean up init()/fini() · 3af5b90b
      Kamalesh Babulal authored
      On Thu, Mar 27, 2008 at 03:40:36PM +0100, Bodo Eggert wrote:
      > Kamalesh Babulal <[email protected]> wrote:
      > > This patch cleanups the crypto code, replaces the init() and fini()
      > > with the <algorithm name>_init/_fini
      > This part ist OK.
      > > or init/fini_<algorithm name> (if the 
      > > <algorithm name>_init/_fini exist)
      > Having init_foo and foo_init won't be a good thing, will it? I'd start
      > confusing them.
      > What about foo_modinit instead?
      Thanks for the suggestion, the init() is replaced with
      	<algorithm name>_mod_init ()
      and fini () is replaced with <algorithm name>_mod_fini.
      Signed-off-by: default avatarKamalesh Babulal <[email protected]>
      Signed-off-by: default avatarHerbert Xu <[email protected]>
  8. 02 Nov, 2007 1 commit
  9. 26 Jun, 2006 3 commits
  10. 09 Jan, 2006 1 commit
  11. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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!