On Mon, Nov 28, 2016, Wim Lewis wrote: > > However, I think the other half of my problem remains: if I'm putting > another CMS object into a SignedData, AuthEnvelopedData, or other kind of > wrapper, the OCTET STRING should contain the encoding of that object's > structure (e.g. a BER-encoded AuthEnvelopedData, SignedData, > ContentWithAttributes, etc. structure), not a ContentInfo *containing* that > structure, right? How do I get OpenSSL to give me that encoded object > without an enclosing ContentInfo? > It's my understanding that the content should be a ContentInfo but I can't see a definitive reference to this. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
