ENGINE-207: fixed verification problem - for some unknown reason, post libetpan parse, Outlook has CRLFs in the next, whereas Linux, Android, etc, appear not to. Tricky. We now handle both around boundary delimiters, and sig verification of AppleMail works! ENGINE-207
authorkrista
Mon, 08 May 2017 15:48:46 +0200
branchENGINE-207
changeset 18939e648c792083
parent 1756 f46ce946ede9
child 1896 bd4d52d8a71f
ENGINE-207: fixed verification problem - for some unknown reason, post libetpan parse, Outlook has CRLFs in the next, whereas Linux, Android, etc, appear not to. Tricky. We now handle both around boundary delimiters, and sig verification of AppleMail works!
src/message_api.c
     1.1 --- a/src/message_api.c	Mon May 08 15:32:57 2017 +0200
     1.2 +++ b/src/message_api.c	Mon May 08 15:48:46 2017 +0200
     1.3 @@ -1503,7 +1503,9 @@
     1.4      if (!end_boundary)
     1.5          return PEP_UNKNOWN_ERROR;
     1.6  
     1.7 -    end_boundary--; // See RFC3156 section 5... FIXME: could be 2? CRLF?
     1.8 +    end_boundary--; // See RFC3156 section 5...
     1.9 +	if (*(end_boundary - 1) == '\r')
    1.10 +		end_boundary--;
    1.11  
    1.12      *ssize = end_boundary - start_boundary;
    1.13      *stext = start_boundary;