On Wed, Sep 03, 2014, Andy Schmidt wrote:
Great, thank you!
The problem is that the API call sequence generates different S/MIME
and/or PKCS7 output between 1.0.1h and 1.0.1i. The attached files are
generated from the same API call sequence, JohnHancock.smime.h with
1.0.1h and
I have found some change in the behavior of the OpenSSL 1.0.1 crypto
library between releases h and i regarding the internal handling of
PKCS7 and X509 structures. Attached is a S/MIME signed message
generated by C calls to the OpenSSL 1.0.1i API. If I take this output
and then on the command line
On Wed, Sep 03, 2014 at 02:01:35PM -0700, Andy Schmidt wrote:
openssl smime -in JohnHancock.smime -pk7out
Decoding the pkcs7 data with asn1parse results in:
0:d=0 hl=4 l=4594 cons: SEQUENCE
4:d=1 hl=2 l= 9 prim: OBJECT:pkcs7-signedData
15:d=1 hl=4
Great, thank you!
The problem is that the API call sequence generates different S/MIME
and/or PKCS7 output between 1.0.1h and 1.0.1i. The attached files are
generated from the same API call sequence, JohnHancock.smime.h with
1.0.1h and JohnHancock.smime.i with 1.0.1i. The h version S/MIME does
On Wed, Sep 03, 2014 at 04:34:05PM -0700, Andy Schmidt wrote:
The problem is that the API call sequence generates different S/MIME
and/or PKCS7 output between 1.0.1h and 1.0.1i. The attached files are
generated from the same API call sequence, JohnHancock.smime.h with
1.0.1h and
