Re: Encryption output buffer description in algif_aead.c file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/24/2016 07:01 AM, Stephan Mueller wrote:
Am Freitag, 24. Juni 2016, 17:24:02 schrieb Harsh Jain:

Hi Harsh,


379          * The memory structure for cipher operation has the following
380          * structure:
381          *      AEAD encryption input:  assoc data || plaintext
382          *      AEAD encryption output: cipherntext || auth tag
383          *      AEAD decryption input:  assoc data || ciphertext || auth
tag 384          *      AEAD decryption output: plaintext

Right, it returns AAD prepended to the stated output. Do you want to provide a
patch?

If testmgr.c is any model, the caller is expected to populate the destination buffer with the AAD. Is my understanding correct? And should this comment clarify that point: i.e. the length of the destination is the sum of the lengths of the
aad + ciphertext + tag?

Gary

--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux