> On Mar 14, 2018, at 2:43 AM, e...@coderhacks.com wrote:
>
> I am facing some problems with a SMIME where the content is binary encoded
> AND a linefeed (LF) (0x0a) is used for line-separator.
> The CMS_verify failes (CMS
> routines:CMS_SignerInfo_verify_content:verification failure).
>
> It
[mailto:openssl-users-boun...@openssl.org] On Behalf
Of e...@coderhacks.com
Sent: Wednesday, March 14, 2018 02:33
To: openssl-users@openssl.org
Subject: Re: [openssl-users] MIME-canonicalization
I think I found the reason for the problem.
SMIME_read_CMS does convert any single LF to a CRLF.
Have you
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of e...@coderhacks.com
> Sent: Wednesday, March 14, 2018 02:33
> To: openssl-users@openssl.org
> Subject: Re: [openssl-users] MIME-canonicalization
>
> I think I found the reason for the problem.
>
I think I found the reason for the problem.
SMIME_read_CMS does convert any single LF to a CRLF.
If I compare the input to the CMS I get out of SMIME_read_CMS then there
are all LFs replaced with CRLFs.
Thats the problem with the verify. If I manually replace the added CRs
in the CMS and the
Hi!
I am facing some problems with a SMIME where the content is binary
encoded AND a linefeed (LF) (0x0a) is used for line-separator.
The CMS_verify failes (CMS
routines:CMS_SignerInfo_verify_content:verification failure).
It works fine if CRLF (0x0d 0x0a) is line-separator or even if only CR
