Hi All,
There is maximum limit of data which crypto user can send(in encrypt)
to get TAG in AEAD operations. We do not have update/final like
implementation for AEAD algo's. why is this so?
Regards
Harsh Jain
Harsh Jain <[email protected]> wrote:
>
> There is maximum limit of data which crypto user can send(in encrypt)
> to get TAG in AEAD operations. We do not have update/final like
> implementation for AEAD algo's. why is this so?
Because our users haven't needed it so far. Also algorithms like CCM
cannot support such an operation.
If you have a valid use case for it then I'll consider it.
Cheers,
--
Email: Herbert Xu <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Hi,
Thank for reply. As such I don't have any use case. But the use case I
can think of is AEAD operation on large file using AF_ALG interface.
If user tried this he/she will get invalid TAG value.
Regards
Harsh Jain
On Fri, Jul 22, 2016 at 10:10 AM, Herbert Xu
<[email protected]> wrote:
> Harsh Jain <[email protected]> wrote:
>>
>> There is maximum limit of data which crypto user can send(in encrypt)
>> to get TAG in AEAD operations. We do not have update/final like
>> implementation for AEAD algo's. why is this so?
>
> Because our users haven't needed it so far. Also algorithms like CCM
> cannot support such an operation.
>
> If you have a valid use case for it then I'll consider it.
>
> Cheers,
> --
> Email: Herbert Xu <[email protected]>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt