13 Sep, 2016

1 commit

  • The current implementation uses a global per-cpu array to store
    data which are used to derive the next IV. This is insecure as
    the attacker may change the stored data.

    This patch removes all traces of chaining and replaces it with
    multiplication of the salt and the sequence number.

    Fixes: a10f554fa7e0 ("crypto: echainiv - Add encrypted chain IV...")
    Cc: stable@vger.kernel.org
    Reported-by: Mathias Krause
    Signed-off-by: Herbert Xu

    Herbert Xu
     

18 Jul, 2016

1 commit


17 Aug, 2015

2 commits


14 Jul, 2015

1 commit

  • This patch fixes a bug where we were incorrectly including the
    IV in the AD during encryption. The IV must remain in the plain
    text for it to be encrypted.

    During decryption there is no need to copy the IV to dst because
    it's now part of the AD.

    This patch removes an unncessary check on authsize which would be
    performed by the underlying decrypt call.

    Finally this patch makes use of the type-safe init/exit functions.

    Signed-off-by: Herbert Xu

    Herbert Xu
     

22 Jun, 2015

1 commit


04 Jun, 2015

1 commit

  • We currently do the IV seeding on the first givencrypt call in
    order to conserve entropy. However, this does not work with
    DRBG which cannot be called from interrupt context. In fact,
    with DRBG we don't need to conserve entropy anyway. So this
    patch moves the seeding into the init function.

    Signed-off-by: Herbert Xu

    Herbert Xu
     

28 May, 2015

3 commits


25 May, 2015

4 commits


22 May, 2015

1 commit

  • This patch adds a new AEAD IV generator echainiv. It is intended
    to replace the existing skcipher IV generator eseqiv.

    If the underlying AEAD algorithm is using the old AEAD interface,
    then echainiv will simply use its IV generator.

    Otherwise, echainiv will encrypt a counter just like eseqiv but
    it'll first xor it against a previously stored IV similar to
    chainiv.

    Signed-off-by: Herbert Xu

    Herbert Xu