qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: liequan che <liequanche@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH V3] crypto: Introduce SM3 hash hmac pbkdf algorithm
Date: Wed, 30 Oct 2024 11:56:49 +0000	[thread overview]
Message-ID: <ZyIfAd_tWU-FzzbM@redhat.com> (raw)
In-Reply-To: <CAAsfc_puem7rZtC2TkEvP81P9edMvNuT3tVM7TPH3NQbR-VC9g@mail.gmail.com>

On Wed, Oct 30, 2024 at 08:58:21AM +0800, liequan che wrote:
> Introduce the SM3 cryptographic hash algorithm (GB/T 32905-2016).
> 
> SM3 (GB/T 32905-2016) is a cryptographic standard issued by the
> Organization of State Commercial Cryptography Administration (OSCCA)
> as an authorized cryptographic algorithm for use within China.
> 
> Detect the SM3 cryptographic hash algorithm and enable the feature silently
> if it is available.
> 
> Signed-off-by: cheliequan <cheliequan@inspur.com>
> ---
>  crypto/hash-gcrypt.c           |  3 +++
>  crypto/hash-nettle.c           | 14 ++++++++++++
>  crypto/hash.c                  |  3 +++
>  crypto/hmac-gcrypt.c           |  3 +++
>  crypto/hmac-nettle.c           | 11 ++++++++++
>  crypto/pbkdf-gcrypt.c          |  6 ++++++
>  crypto/pbkdf-nettle.c          | 13 ++++++++++++
>  include/crypto/hash.h          |  1 +
>  meson.build                    | 39 ++++++++++++++++++++++++++++++++++
>  qapi/crypto.json               |  3 ++-
>  tests/unit/test-crypto-hash.c  | 16 ++++++++++++++
>  tests/unit/test-crypto-hmac.c  |  8 +++++++
>  tests/unit/test-crypto-pbkdf.c | 16 ++++++++++++++
>  13 files changed, 135 insertions(+), 1 deletion(-)

  Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>

In testing this, I hit a pre-existing bug in our hash availability
detection which causes tests on fail on RHEL/Fedora. Not the fault
of your patch, it merely exposes the problem:

 https://lists.nongnu.org/archive/html/qemu-devel/2024-10/msg05589.html

I'm queuing your patch, but I have to wait for review of the
above two fixes before merging.


BTW, your email here was sent as mixed plain/HTML and your mail client
has applied line-wrapping to the plain text. This prevented git from
applying the patch.

It was easy enough for me to fixup the line wrapping, so no need to
resend this, but in future please ensure to send patches as only
plain text, no HTML, and without line wrapping.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2024-10-30 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30  0:58 [PATCH V3] crypto: Introduce SM3 hash hmac pbkdf algorithm liequan che
2024-10-30 11:56 ` Daniel P. Berrangé [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=ZyIfAd_tWU-FzzbM@redhat.com \
    --to=berrange@redhat.com \
    --cc=liequanche@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).