Skip to content
  1. Mar 25, 2015
  2. Mar 24, 2015
  3. Mar 23, 2015
  4. Mar 21, 2015
  5. Mar 20, 2015
    • Dr. Stephen Henson's avatar
      Add AES unwrap test with invalid key. · 77e127ea
      Dr. Stephen Henson authored
      
      
      This tests the unwrap algorithm with an invalid key. The result should
      be rejected without returning any plaintext.
      
      Reviewed-by: default avatarEmilia Käsper <emilia@openssl.org>
      77e127ea
    • Dr. Stephen Henson's avatar
      Fix memory leak. · 5724bd49
      Dr. Stephen Henson authored
      
      
      Reviewed-by: default avatarEmilia Käsper <emilia@openssl.org>
      5724bd49
    • Richard Godbee's avatar
      CRYPTO_128_unwrap(): Fix refactoring damage · e6abba3a
      Richard Godbee authored
      crypto/modes/wrap128.c was heavily refactored to support AES Key Wrap
      with Padding, and four bugs were introduced into CRYPTO_128_unwrap() at
      that time:
      
      - crypto_128_unwrap_raw()'s return value ('ret') is checked incorrectly,
        and the function immediately returns 'ret' in (almost) all cases.
        This makes the IV checking code later in the function unreachable, but
        callers think the IV check succeeded since CRYPTO_128_unwrap()'s
        return value is non-zero.
      
        FIX: Return 0 (error) if crypto_128_unwrap_raw() returned 0 (error).
      
      - crypto_128_unwrap_raw() writes the IV to the 'got_iv' buffer, not to
        the first 8 bytes of the output buffer ('out') as the IV checking code
        expects.  This makes the IV check fail.
      
        FIX: Compare 'iv' to 'got_iv', not 'out'.
      
      - The data written to the output buffer ('out') is "cleansed" if the IV
        check fails, but the code passes OPENSSL_cleanse() the input buffer
        length ('inlen') instead of the number of bytes that
        crypto_12...
      e6abba3a