Re: Who will copy the AAD data to dest. buffer

Am Samstag, 3. September 2016, 10:45:08 CEST schrieb Harsh Jain: Hi Harsh, > Thanks Herbert for clarification. It means Libkcapi documentation > needs update of chapter "Aead Cipher API". Fixed, I will release a new version shortly. Thanks for the pointer. Ciao Stephan -- To unsubscribe from

Re: Who will copy the AAD data to dest. buffer

Thanks Herbert for clarification. It means Libkcapi documentation needs update of chapter "Aead Cipher API". Regards Harsh Jain On Fri, Sep 2, 2016 at 8:12 PM, Herbert Xu wrote: > On Fri, Sep 02, 2016 at 08:05:04PM +0530, Harsh Jain wrote: >> Hi Herbert, >> >> Is copy of AAD data to destinati

Re: Who will copy the AAD data to dest. buffer

On Fri, Sep 02, 2016 at 08:05:04PM +0530, Harsh Jain wrote: > Hi Herbert, > > Is copy of AAD data to destination buffer when dst != src is mandatory > requirements for crypto drivers or we can skip this copy. Actually I > am bit confused, In following link Stephen had mentioned caller will > memcp

Who will copy the AAD data to dest. buffer

Hi Herbert, Is copy of AAD data to destination buffer when dst != src is mandatory requirements for crypto drivers or we can skip this copy. Actually I am bit confused, In following link Stephen had mentioned caller will memcpy the AAD to destination buffer but authenc.c also copies the AAD to des