moving from PKCS7 to CMS functions

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

moving from PKCS7 to CMS functions

Michael Richardson

I am implementing a module for ruby-openssl to add CMS API access to ruby.
(Once I figure it out, I will likely look at how to refactor PKCS7 API code,
but I don't care about that yet)

PKCS7 has the PKCS7_SIGNER_INFO object, and it is declared in pkcs7.h with
DECLARE_ASN1_FUNCTIONS().

CMS has the CMS_SignerInfo object, but it is not declared in cms.h, and so
has no _alloc/_free API.

Is this an oversight?
Or is there a some difference in the API which I have yet to understand which
would mean that CMS_SignerInfo objects would never be allocated/freed.

(I found it surprising that DECLARE_ASN1_FUNCTIONS() was in the X509_dup.pod
file)

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     [hidden email]  http://www.sandelman.ca/        |   ruby on rails    [





--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

signature.asc (497 bytes) Download Attachment