Bug 3764 - mutt-1.2.5-alt-8bitpgp.patch breaks RFC 3156
: mutt-1.2.5-alt-8bitpgp.patch breaks RFC 3156
Status: CLOSED FIXED
: Sisyphus
(All bugs in Sisyphus/mutt)
: unstable
: all Linux
: P2 critical
Assigned To:
:
:
:
:
:
  Show dependency tree
 
Reported: 2004-02-29 20:08 by
Modified: 2005-07-13 15:45 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2004-02-29 20:08:14
В результате наложения mutt-1.2.5-alt-8bitpgp.patch сообщения с подписью
отсылаются с Content-Transfer-Encoding: 8bit, что противоречит RFC 3156:

3.  Content-Transfer-Encoding restrictions

   Multipart/signed and multipart/encrypted are to be treated by agents
   as opaque, meaning that the data is not to be altered in any way [2],
   [7].  However, many existing mail gateways will detect if the next
   hop does not support MIME or 8-bit data and perform conversion to
   either Quoted-Printable or Base64.  This presents serious problems
   for multipart/signed, in particular, where the signature is
   invalidated when such an operation occurs.  For this reason all data
   signed according to this protocol MUST be constrained to 7 bits (8-
   bit data MUST be encoded using either Quoted-Printable or Base64).
   Note that this also includes the case where a signed object is also
   encrypted (see section 6).  This restriction will increase the
   likelihood that the signature will be valid upon receipt.

Только что заметил, что smtp.murom.net молча преобразовывает 8bit в
quoted-printable, в результате все подписи, сделанные в mutt, портятся.

Если уж так хочется отсылать сообщения, не соответствуюшие RFC, это должно быть
настраиваемым, и по умолчанию выключено.
------- Comment #1 From 2004-03-03 18:23:19 -------
Убрал этот патч в mutt-1.4.2.1i-alt2