From: Herbert Xu <herbert@gondor.apana.org.au>
To: Harsh Jain <harshjain.prof@gmail.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: Max data limit for AEAD operation
Date: Fri, 22 Jul 2016 12:40:19 +0800 [thread overview]
Message-ID: <20160722044019.GA17416@gondor.apana.org.au> (raw)
In-Reply-To: <CAFXBA==j+6fGuWrjNroGWnnBc13ev+6EB2Ae7SnwAVVxjTWBrw@mail.gmail.com>
Harsh Jain <harshjain.prof@gmail.com> 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 <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2016-07-22 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 12:12 Max data limit for AEAD operation Harsh Jain
2016-07-22 4:40 ` Herbert Xu [this message]
2016-07-22 4:45 ` Harsh Jain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160722044019.GA17416@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=harshjain.prof@gmail.com \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox