Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: GCM aesni and 192/256-bit keys
Date: Mon, 05 Jan 2015 09:51:35 -0800	[thread overview]
Message-ID: <54AACF27.6090300@intel.com> (raw)
In-Reply-To: <20150105100644.GA24595@gondor.apana.org.au>

On 01/05/2015 02:06 AM, Herbert Xu wrote:
> Hi Tadeusz:
> 
> It appears that the GCM aesni implementation does not support
> 192/256-bit keys.  This is not allowed as accelerated drivers
> must support everything supported by the software implementation.
> 
> Could we add 192/256-bit support to it please? If for some reason
> this cannot be done then at least implement a software fallback
> so that it continues to work.
> 
> Thanks,
> 

Hi Herbert,
Yes, you are right. I'll look into it.
Thanks,
Tadeusz

  reply	other threads:[~2015-01-05 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 10:06 GCM aesni and 192/256-bit keys Herbert Xu
2015-01-05 17:51 ` Tadeusz Struk [this message]
2015-01-06 23: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=54AACF27.6090300@intel.com \
    --to=tadeusz.struk@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox