diff options
| author | Tianjia Zhang <tianjia.zhang@linux.alibaba.com> | 2020-02-10 20:44:39 +0800 |
|---|---|---|
| committer | Mimi Zohar <zohar@linux.ibm.com> | 2020-02-18 07:35:49 -0500 |
| commit | 6a30e1b1dcad0ba94fae757f797812d7d8dcb72c (patch) | |
| tree | 9c402f0e210bf00f44c9de6ccc82056fe81d152a /crypto | |
| parent | 3be54d558c75562e42bc83d665df024bd79d399b (diff) | |
crypto: rename sm3-256 to sm3 in hash_algo_name
The name sm3-256 is defined in hash_algo_name in hash_info, but the
algorithm name implemented in sm3_generic.c is sm3, which will cause
the sm3-256 algorithm to be not found in some application scenarios of
the hash algorithm, and an ENOENT error will occur. For example,
IMA, keys, and other subsystems that reference hash_algo_name all use
the hash algorithm of sm3.
Fixes: 5ca4c20cfd37 ("keys, trusted: select hash algorithm for TPM2 chips")
Signed-off-by: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
Reviewed-by: Pascal van Leeuwen <pvanleeuwen@rambus.com>
Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
Diffstat (limited to 'crypto')
| -rw-r--r-- | crypto/hash_info.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/crypto/hash_info.c b/crypto/hash_info.c index c754cb75dd1a..a49ff96bde77 100644 --- a/crypto/hash_info.c +++ b/crypto/hash_info.c @@ -26,7 +26,7 @@ const char *const hash_algo_name[HASH_ALGO__LAST] = { [HASH_ALGO_TGR_128] = "tgr128", [HASH_ALGO_TGR_160] = "tgr160", [HASH_ALGO_TGR_192] = "tgr192", - [HASH_ALGO_SM3_256] = "sm3-256", + [HASH_ALGO_SM3_256] = "sm3", [HASH_ALGO_STREEBOG_256] = "streebog256", [HASH_ALGO_STREEBOG_512] = "streebog512", }; |