FISCO-BCOS / FISCO-BCOS/java-sdk
SM2签名为什么不能直接传m而是传的m的哈希值?
Open
question
- Dominant language
- Java
- Stars
- 58
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
根据sm2算法规范
是先计算Z_A,然后拼接m做哈希
如果传参是m的sm3哈希，而不是m本身，会不会不太符合SM2算法规范?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no source file, entry point, or test. Start by locating the SM2 signing API and comparing its expected input with the SM2 specification and the reported pre-hashed m behavior; done means the behavior is confirmed as compliant or corrected and covered by an appropriate test or explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100