On Fri, Feb 18, 2011, Patrick Patterson wrote:
> Hi Steve:
>
> On 2011-02-18, at 1:29 PM, Dr. Stephen Henson wrote:
> >
> > I'm not sure what you mean by "wrapped in an explicit application tag".
>
>
> What I mean is that I have the usual encoding of ContentInfo (as per RFC 3825
> ) of:
>
Hi Steve:
On 2011-02-18, at 1:29 PM, Dr. Stephen Henson wrote:
>
> I'm not sure what you mean by "wrapped in an explicit application tag".
What I mean is that I have the usual encoding of ContentInfo (as per RFC 3825 )
of:
ContentInfo ::= SEQUENCE {
contentType ContentType,
conten
On Fri, Feb 18, 2011, Patrick Patterson wrote:
> Hello all:
>
> I've recently run into a situation where I need to generate a CMS
> ContentInfo Structure, but wrapped in an explicit application tag. I notice
> that with all of the great work that Steve and other's have done, that it's
> now possi
Hello all:
I've recently run into a situation where I need to generate a CMS ContentInfo
Structure, but wrapped in an explicit application tag. I notice that with all
of the great work that Steve and other's have done, that it's now possible, but
I can't see a simple way to code this up.
Are t
> [vstin...@edenwall.com - Fri Feb 18 13:34:58 2011]:
>
> Hi,
>
> A collegue has an issue with SMIME_write_PKCS7() using Python and the
> M2Crypto library for a multipart (MIME) signature. He uses a memory BIO
> as output. He told me that the script works with OpenSSL 0.9.8g, but not
> with OpenS
Hi,
A collegue has an issue with SMIME_write_PKCS7() using Python and the
M2Crypto library for a multipart (MIME) signature. He uses a memory BIO
as output. He told me that the script works with OpenSSL 0.9.8g, but not
with OpenSSL 0.9.8o. In CVS, I saw that PKCS7 and ASN.1 code for SMIME
changed
