26 Nov, 2014

2 commits

  • This adds the module loading prefix "crypto-" to the template lookup
    as well.

    For example, attempting to load 'vfat(blowfish)' via AF_ALG now correctly
    includes the "crypto-" prefix at every level, correctly rejecting "vfat":

    net-pf-38
    algif-hash
    crypto-vfat(blowfish)
    crypto-vfat(blowfish)-all
    crypto-vfat

    Reported-by: Mathias Krause
    Signed-off-by: Kees Cook
    Acked-by: Mathias Krause
    Signed-off-by: Herbert Xu

    Kees Cook
     
  • To allow automatic loading of the crypto_user kernel module, the netlink
    MODULE_ALIAS is added.

    Signed-off-by: Stephan Mueller
    Signed-off-by: Herbert Xu

    Stephan Mueller
     

25 Nov, 2014

3 commits

  • This can't be NULL and we dereferenced it earlier. Smatch used to
    ignore these things where the pointer was obviously non-NULL but I've
    found that sometimes the intention was to check something else so we
    were maybe missing bugs.

    Signed-off-by: Dan Carpenter
    Acked-by: Tim Chen
    Signed-off-by: Herbert Xu

    Dan Carpenter
     
  • Fix invalid inflights calculation for 64 bytes requests.

    Signed-off-by: Tadeusz Struk
    Signed-off-by: Herbert Xu

    Struk, Tadeusz
     
  • Commit e1bd95bf7c25 ("crypto: algif - zeroize IV buffer") and
    2a6af25befd0 ("crypto: algif - zeroize message digest buffer")
    added memzero_explicit() calls on buffers that are later on
    passed back to sock_kfree_s().

    This is a discussed follow-up that, instead, extends the sock
    API and adds sock_kzfree_s(), which internally uses kzfree()
    instead of kfree() for passing the buffers back to slab.

    Having sock_kzfree_s() allows to keep the changes more minimal
    by just having a drop-in replacement instead of adding
    memzero_explicit() calls everywhere before sock_kfree_s().

    In kzfree(), the compiler is not allowed to optimize the memset()
    away and thus there's no need for memzero_explicit(). Both,
    sock_kfree_s() and sock_kzfree_s() are wrappers for
    __sock_kfree_s() and call into kfree() resp. kzfree(); here,
    __sock_kfree_s() needs to be explicitly inlined as we want the
    compiler to optimize the call and condition away and thus it
    produces e.g. on x86_64 the _same_ assembler output for
    sock_kfree_s() before and after, and thus also allows for
    avoiding code duplication.

    Cc: David S. Miller
    Signed-off-by: Daniel Borkmann
    Signed-off-by: Herbert Xu

    Daniel Borkmann
     

24 Nov, 2014

2 commits


20 Nov, 2014

6 commits


17 Nov, 2014

3 commits


13 Nov, 2014

13 commits


12 Nov, 2014

4 commits


10 Nov, 2014

7 commits