This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dkg
Recipients barry, dkg, mitya57, r.david.murray, sjt
Date 2013-09-21.18:20:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379787606.06.0.603139756682.issue14983@psf.upfronthosting.co.za>
In-reply-to
Content
I think the relevant specification for PGP/MIME-signed messages is RFC 3156:

 https://tools.ietf.org/html/rfc3156#page-5

in particular:

      Note: The accepted OpenPGP convention is for signed data to end
      with a <CR><LF> sequence.  Note that the <CR><LF> sequence
      immediately preceding a MIME boundary delimiter line is considered
      to be part of the delimiter in [3], 5.1.  Thus, it is not part of
      the signed data preceding the delimiter line.  An implementation
      which elects to adhere to the OpenPGP convention has to make sure
      it inserts a <CR><LF> pair on the last line of the data to be
      signed and transmitted (signed message and transmitted message
      MUST be identical).
History
Date User Action Args
2013-09-21 18:20:06dkgsetrecipients: + dkg, barry, r.david.murray, sjt, mitya57
2013-09-21 18:20:06dkgsetmessageid: <1379787606.06.0.603139756682.issue14983@psf.upfronthosting.co.za>
2013-09-21 18:20:06dkglinkissue14983 messages
2013-09-21 18:20:05dkgcreate