Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#3 problems with quoted-printable messages

closed-fixed
nobody
None
5
2001-12-12
2001-11-05
Disastry
No

mixmaster does not handle quoted-printable messages
well. For example following message does not decrypts
because '=' is replaced with '=3D' and 'F' at beginig
of line with '=46':

From: x <x@x.com>
To: x@x.org
Subject:
Date: Mon, 5 Nov 2001 00:00:00 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

::
Encrypted: PGP

-----BEGIN PGP MESSAGE-----
Version: 2.6.3i

hQCMA3Rg9FKEFTc/AQP7BMKumXyPzzfs7iTiGLpm72vNU+VW5aUO7Dp
UbyvGgy2M
QBHJ3a/UdGKhf/Li5PHlP5J8vjBOGf938/bCGZtimNxf4e99eN5LB/C
GmxQ7SmFS
=469+7/wPEL/D1SD3Ceqv9kU7R+WVKm2E/bBwTSyJPwT5RlVdGARfXp
/+H+A5FG3Kk
GM4Z8DKeG6nH0Y41ryzC94NbeL4tg0JDFw=3D=3D
=3DOOuk
-----END PGP MESSAGE-----

(in this message from, to and date headers are edited)

Discussion

  • Logged In: YES
    user_id=381208

    I have not been lurking in the remailer-society

    recently.

    But, is deactivation of any additional encoding, apart

    from the encryption, not one of the first things you

    should do prior creating anonymous emails, especially

    mixmaster-messages?

    (I remember a day, when I crashed some mixmaster...)

    Okay, has this ever changed or should we just remind

    people to do without quoted-printable and the like?

    For me at least, this is _no_ bug at all.

     
  • Logged In: NO

    well..
    mixmaster have support for multipart quoted-printable
    messages, so it seems strange that single part
    quoted-printable messages are not supported.

    besides, there are some MTAs that converts messages to
    quoted-printable, so sender my even not know that his
    message is quoted-printable.

     
  • Len Sassaman
    Len Sassaman
    2001-12-12

    Logged In: YES
    user_id=29569

    Scott Renfro submitted a patch for this. He says:

    Processing the message in the bug report still fails due
    to the extra line breaks in that message (e.g., following
    "7Dp"), but if you remove these, it works just fine with
    the patch. I assume that these extra line breaks are an
    artifact of the bug submission form. If not, then we can
    make decode() more tolerant of embedded line breaks.

     
  • Len Sassaman
    Len Sassaman
    2001-12-12

    • status: open --> closed-fixed
     
  • Disastry
    Disastry
    2001-12-13

    Logged In: YES
    user_id=363885

    exactly: extra line breaks are an artifact of the bug
    submission form.