R. David Murray added the comment:

Well, there are two problems here, I think (it's been a while since I looked at 
this): we should indeed be adding a crlf between mime boundary lines.  But also 
the clients should technically be handling it not being there, as well as the 
case of extra whitespace being added between the end of the delimiter and the 
following crlf (which I'm guessing they don't, since the logical way to handle 
that would be to ignore anything after the end of the delimiter string, in 
which case this problem wouldn't arise).

Specifically:

   The boundary may be followed by zero or more characters of linear
   whitespace. It is then terminated by either another CRLF...

and:

   NOTE TO IMPLEMENTORS:  Boundary string comparisons must compare the
   boundary value with the beginning of each candidate line.  An exact
   match of the entire candidate line is not required; it is sufficient
   that the boundary appear in its entirety following the CRLF.

So it seems to me that the PGP spec is not RFC conformant...but if we were 
following the RFC it wouldn't be an issue.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue14983>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to