1. 11 Feb, 2017 1 commit
  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 <keescook@chromium.org>
      Signed-off-by: default avatarMathias Krause <minipli@googlemail.com>
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
  3. 24 Nov, 2014 1 commit
  4. 14 Aug, 2013 1 commit
  5. 01 Aug, 2012 1 commit
  6. 16 Feb, 2010 1 commit
  7. 24 Jul, 2009 1 commit
    • Phil Carmody's avatar
      crypto: aes - Undefined behaviour in crypto_aes_expand_key · 7b4ffcf9
      Phil Carmody authored
      It's undefined behaviour in C to write outside the bounds of an array.
      The key expansion routine takes a shortcut of creating 8 words at a
      time, but this creates 4 additional words which don't fit in the array.
      As everyone is hopefully now aware, GCC is at liberty to make any
      assumptions and optimisations it likes in situations where it can
      detect that UB has occured, up to and including nasal demons, and
      as the indices being accessed in the array are trivially calculable,
      it's rash to invite gcc to do take any liberties at all.
      Signed-off-by: default avatarPhil Carmody <ext-phil.2.carmody@nokia.com>
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
  8. 25 Dec, 2008 1 commit
    • Herbert Xu's avatar
      crypto: aes - Precompute tables · 0ee4a969
      Herbert Xu authored
      The tables used by the various AES algorithms are currently
      computed at run-time.  This has created an init ordering problem
      because some AES algorithms may be registered before the tables
      have been initialised.
      This patch gets around this whole thing by precomputing the tables.
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
  9. 21 Apr, 2008 1 commit
  10. 10 Jan, 2008 3 commits
  11. 10 Oct, 2007 1 commit
  12. 21 Sep, 2006 1 commit
    • Herbert Xu's avatar
      [CRYPTO] api: Get rid of flags argument to setkey · 560c06ae
      Herbert Xu authored
      Now that the tfm is passed directly to setkey instead of the ctx, we no
      longer need to pass the &tfm->crt_flags pointer.
      This patch also gets rid of a few unnecessary checks on the key length
      for ciphers as the cipher layer guarantees that the key length is within
      the bounds specified by the algorithm.
      Rather than testing dia_setkey every time, this patch does it only once
      during crypto_alloc_tfm.  The redundant check from crypto_digest_setkey
      is also removed.
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
  13. 26 Jun, 2006 1 commit
    • Herbert Xu's avatar
      [CRYPTO] all: Pass tfm instead of ctx to algorithms · 6c2bb98b
      Herbert Xu authored
      Up until now algorithms have been happy to get a context pointer since
      they know everything that's in the tfm already (e.g., alignment, block
      However, once we have parameterised algorithms, such information will
      be specific to each tfm.  So the algorithm API needs to be changed to
      pass the tfm structure instead of the context pointer.
      This patch is basically a text substitution.  The only tricky bit is
      the assembly routines that need to get the context pointer offset
      through asm-offsets.h.
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
  14. 21 Mar, 2006 1 commit
    • David McCullough's avatar
      [CRYPTO] aes: Fixed array boundary violation · 55e9dce3
      David McCullough authored
      The AES setkey routine writes 64 bytes to the E_KEY area even though
      there are only 60 bytes there.  It is in fact safe since E_KEY is
      immediately follwed by D_KEY which is initialised afterwards.  However,
      doing this may trigger undefined behaviour and makes Coverity unhappy.
      So by combining E_KEY and D_KEY into one array we sidestep this issue
      This problem was reported by Adrian Bunk.
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
  15. 09 Jan, 2006 3 commits
  16. 27 Jul, 2005 1 commit
  17. 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!