From: Greg KH <gregkh@linuxfoundation.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
ebiggers@kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v4] wusb: switch to cbcmac transform
Date: Tue, 18 Jun 2019 08:53:07 +0200 [thread overview]
Message-ID: <20190618065307.GA15206@kroah.com> (raw)
In-Reply-To: <20190617081848.23614-1-ard.biesheuvel@linaro.org>
On Mon, Jun 17, 2019 at 10:18:48AM +0200, Ard Biesheuvel wrote:
> The wusb code takes a very peculiar approach at implementing CBC-MAC,
> by using plain CBC into a scratch buffer, and taking the output IV
> as the MAC.
>
> We can clean up this code substantially by switching to the cbcmac
> shash, as exposed by the CCM template. To ensure that the module is
> loaded on demand, add the cbcmac template name as a module alias.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> v4: - update Kconfig dependencies accordingly (and fix whitespace)
> v3: - add missing #include to fix build error spotted by kbuild test robot
> v2: - use finup()/digest() where possible, and process b0+b1 using a single
> call to update()
> - make 'stv_hsmic_hs' static const and remove comment regarding GCC 4.1
>
> NOTE: I don't have any hardware to test this, but the built-in selftest
> still passes.
>
> crypto/ccm.c | 1 +
> drivers/usb/wusbcore/Kconfig | 8 +-
> drivers/usb/wusbcore/crypto.c | 169 +++++---------------
> 3 files changed, 48 insertions(+), 130 deletions(-)
I've queued this up in the usb-next tree now, thanks.
greg k-h
prev parent reply other threads:[~2019-06-18 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 8:18 [PATCH v4] wusb: switch to cbcmac transform Ard Biesheuvel
2019-06-18 6:53 ` Greg KH [this message]
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=20190618065307.GA15206@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-usb@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.