On Sat, 2021-10-09 at 21:08 +0800, Tianjia Zhang wrote: > According to https://tools.ietf.org/id/draft-oscca-cfrg-sm3-01.html, > SM3 always produces a 256-bit hash value and there are no plans for > other length development, so there is no ambiguity in the name of > sm3. For the TPM we're following the TPM Library specification https://trustedcomputinggroup.org/resource/tpm-library-specification/ Which is very clear: the algorithm name is TPM_ALG_SM3_256 We're using sm3 as our exposed name because that's what linux crypto uses, so there should be no problem in what the end user sees, but changing to non standard TPM definitions is only going to cause confusion at the kernel level. James
