The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Xu Jia <xujia39@huawei.com>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
	<kuba@kernel.org>, <linux-kernel@vger.kernel.org>,
	<netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/2] xfrm: Add support for SM3 and SM4
Date: Wed, 29 Dec 2021 11:18:12 +0100	[thread overview]
Message-ID: <20211229101812.GP3272477@gauss3.secunet.de> (raw)
In-Reply-To: <1640164019-42341-1-git-send-email-xujia39@huawei.com>

On Wed, Dec 22, 2021 at 05:06:57PM +0800, Xu Jia wrote:
> These patches add xfrm support for SM3 and SM4 algorithms which are
> cryptographic standards published by China State Cryptography 
> Administration.
> 
> SM3 secure hash (OSCCA GM/T 0004-2012 SM3) is based on Merkle-Damgard 
> with a thuncation of 256 bits. It could be used for authentication 
> and random number generation.
> 
> SM4 symmetric ciper algorithm (OSCCA GB/T 32097-2016) has at least 128
> bits packet length which is similar to AES ciper algorithm. It is 
> suitable for the use of block ciphers in cryptographic applications.
> 
> As SM3 and SM4 have already been supported by Linux kernel,
> after these patches, we can use them with "ip xfrm" tools easily.
> 
> 
> Xu Jia (2):
>   xfrm: Add support for SM3 secure hash
>   xfrm: Add support for SM4 symmetric cipher algorithm
> 
>  include/uapi/linux/pfkeyv2.h |  2 ++
>  net/xfrm/xfrm_algo.c         | 41 +++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 43 insertions(+)

Series applied to ipsec-next, thanks a lot!

      parent reply	other threads:[~2021-12-29 10:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22  9:06 [PATCH net-next 0/2] xfrm: Add support for SM3 and SM4 Xu Jia
2021-12-22  9:06 ` [PATCH net-next 1/2] xfrm: Add support for SM3 secure hash Xu Jia
2021-12-22  9:06 ` [PATCH net-next 2/2] xfrm: Add support for SM4 symmetric cipher algorithm Xu Jia
2021-12-29 10:18 ` Steffen Klassert [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=20211229101812.GP3272477@gauss3.secunet.de \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xujia39@huawei.com \
    /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