From: Ambarus Tudor-Dan-B38632 <b38632@freescale.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>
Subject: Re: variable iv lengths for aes-gcm
Date: Thu, 18 Jun 2015 12:44:06 +0300 [thread overview]
Message-ID: <558292E6.3060708@freescale.com> (raw)
In-Reply-To: <20150618080707.GA29218@gondor.apana.org.au>
On 6/18/2015 11:07 AM, Herbert Xu wrote:
> On Thu, Jun 18, 2015 at 10:43:18AM +0300, Ambarus Tudor-Dan-B38632 wrote:
>>
>> I'm trying to find a method to pass IVs of various lengths to an
>> algorithm. A particular case would be aes-gcm IV. It can have any
>> number of bits between 1 and 2^64.
>>
>> A possible way to do this is to set the ivlen per request. Are there
>> any (better) ways to do this?
>
> Why would you want do this apart from the fact that your hardware
> supports it and you want to export this?
>
The reason is to cover a wide range of applications. Your question also
applies to the gcm NIST publication.
Users may want to use a crypto module that meets the requirements of
FIPS Pub. for various applications that use variable lengths for IV.
ta
next prev parent reply other threads:[~2015-06-18 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 7:43 variable iv lengths for aes-gcm Ambarus Tudor-Dan-B38632
2015-06-18 8:07 ` Herbert Xu
2015-06-18 9:44 ` Ambarus Tudor-Dan-B38632 [this message]
2015-06-19 0:18 ` Herbert Xu
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=558292E6.3060708@freescale.com \
--to=b38632@freescale.com \
--cc=herbert@gondor.apana.org.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.