-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unknown OID was met when running cmsparse #1701
Comments
严格按《GB/T 35275-2017 信息安全技术 SM2密码算法加密签名消息语法规范》来讲,国密SignedData里的 |
It is actually A correct Signature algorithm sm2-with-sm3, but gmssl cmsparse just failed to treat it.
|
看起来本项目只支持国密CMS,也就是《GB/T 35275-2017 信息安全技术 SM2密码算法加密签名消息语法规范》中定义的OID,不支持国际标准。 |
gmssl should just parse and print it if it failed to recognize it. |
这应该是项目定位问题,它不是一个通用的ASN.1数据Parse工具,无可厚非。 |
I deleted some codes :
|
when I run "gmssl cmsparse " on a pkcs 7 formated signature, I got output of
Unknown OID: (unknown) (1.2.156.10197.1.501)
E:\Download\GmSSL-master\src\asn1.c:1239:asn1_oid_info_from_der():
E:\Download\GmSSL-master\src\x509_alg.c:119:x509_digest_algor_from_der():
E:\Download\GmSSL-master\src\cms.c:926:cms_digest_algors_print():
The problem is that the give signature is malformed not sticking to GB/T 35275(thank emmansun ) ,
and concurrently gmssl is strict to the format. The signature took a signature oid (1.2.156.10197.1.501) as an hash oid (1.2.156.10197.1.401), and gmssl just parsed it as wrong.
I suggest gmssl be more adaptive to such inconsistence.
The text was updated successfully, but these errors were encountered: