Hi,
On 3/24/21 6:14 AM, Ard Biesheuvel wrote:
On Tue, 23 Mar 2021 at 09:36, Tianjia Zhang
<tianjia.zhang@xxxxxxxxxxxxxxxxx> wrote:
The kernel module signature supports the option to use the SM3
secure hash (OSCCA GM/T 0004-2012 SM3).
Signed-off-by: Tianjia Zhang <tianjia.zhang@xxxxxxxxxxxxxxxxx>
A secure hash is not the same as a signature. Looking at the patch,
the asymmetric algorithm that is used to sign the SM3 digest is SM2,
is that correct? How does one create such signed modules?
In any case, please provide more context in the commit log on how this
is intended to be used.
Sorry for the trouble you have caused. You are right. SM2 and SM3 always
appear in pairs. The former is used for signatures and the latter is
used for hashing algorithms. I will add this information in the next
version. It seems This is more appropriate to split into two patches.
Best regards,
Tianjia
