From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH] cipher: add AES-CMAC hashing support
Date: Tue, 28 May 2019 20:32:13 -0500 [thread overview]
Message-ID: <77166303-c2ea-5822-e36a-d52517e79840@gmail.com> (raw)
In-Reply-To: <20190529004949.25387-1-brian.gix@intel.com>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
Hi Brian,
On 05/28/2019 07:49 PM, Brian Gix wrote:
> The algorythm is supported in the kernel, and it is used heavily by
> Bluetooth Mesh, and is the one Mesh required algorythm missing from ELL.
> ---
> ell/cipher.c | 88 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ell/cipher.h | 16 ++++++++++
> unit/test-cipher.c | 74 +++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 178 insertions(+)
>
Please be aware of our patch submission guidelines found in HACKING.
E.g. the unit test should be in a separate commit.
Have you checked whether l_checksum_new_cmac_aes() satisfies your needs?
Regards,
-Denis
next prev parent reply other threads:[~2019-05-29 1:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 0:49 [PATCH] cipher: add AES-CMAC hashing support Brian Gix
2019-05-29 1:32 ` Denis Kenzior [this message]
2019-05-29 3:04 ` Gix, Brian
2019-05-29 3:25 ` Gix, Brian
2019-05-29 10:52 ` =?unknown-8bit?q?Micha=C5=82?= Lowas-Rzechonek
2019-05-29 15:29 ` Gix, Brian
2019-05-29 19:26 ` michal.lowas-rzechonek
2019-05-29 20:07 ` Gix, Brian
2019-05-29 16:14 ` Denis Kenzior
2019-05-31 17:28 ` ELL building broken for 32bit systems Gix, Brian
2019-05-31 17:41 ` Gix, Brian
2019-05-31 19:53 ` Denis Kenzior
2019-05-31 20:28 ` Gix, Brian
2019-05-31 20:44 ` Denis Kenzior
2019-05-31 23:12 ` Gix, Brian
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=77166303-c2ea-5822-e36a-d52517e79840@gmail.com \
--to=denkenz@gmail.com \
--cc=ell@lists.01.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.