CMS_SIgnedData backwards-compatibility
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: openssl-users@xxxxxxxxxxx
- Subject: CMS_SIgnedData backwards-compatibility
- From: Zachary Lund <admin@xxxxxxxxxxxxxxxx>
- Date: Mon, 16 Aug 2021 22:02:01 -0500
- User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
Hello,
I'm trying to encode some data into a CMS_SignedData structure. The
verifying code, however, doesn't expect the `encapContentInfo` to be
wrapped in an OCTET STRING. In RFC 5652 (5.2.1), they mention a possible
exception to this for the sake of backwards compatibility with PKCS7.
The Authenticode example they gave is basically exactly what I'm
wanting. I was wondering if there was a way to implement this exception
in OpenSSL's CMS API.
Thanks, Zach
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]
[Linux ARM Kernel]
[Linux ARM]
[Linux Omap]
[Fedora ARM]
[IETF Annouce]
[Security]
[Bugtraq]
[Linux]
[Linux OMAP]
[Linux MIPS]
[ECOS]
[Asterisk Internet PBX]
[Linux API]