Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Oct 2006 16:24:03 -0400
From:      "Brian A. Seklecki" <bseklecki@collaborativefusion.com>
To:        =?ISO-8859-1?Q?Andr=E9?= Malo <nd@perlig.de>
Cc:        "Brian J. Creasy" <bcreasy@collaborativefusion.com>, python@FreeBSD.org, az@FreeBSD.org, netops@collaborativefusion.com
Subject:   Re: [netops] Re: svnmailer issue
Message-ID:  <1161030243.37174.64.camel@soundwave.pgh.priv.collaborativefusion.com>
In-Reply-To: <200610162205.48003@news.perlig.de>
References:  <4533E49D.2000005@collaborativefusion.com> <200610162205.48003@news.perlig.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Wow thanks for the quick response!

Very concerning that a double-point version upgrade would change
something as important as MIME quoted-printable settings.  We patched it
because of a vulnerability; perhaps that was related, but I don't really
troll the Phython CVS-commit mailing list of these things.

CC'ing the relative FreeBSD port maintainers.

Affected package: python-2.4.3
Type of problem: python -- buffer overrun in repr() for unicode strings.
Reference:
<http://www.FreeBSD.org/ports/portaudit/fe83eb5b-55e1-11db-a5ae-00508d6a62df.html>;

TIA,
~BAS

On Mon, 2006-10-16 at 22:05 +0200, André Malo wrote:
> * Brian J. Creasy wrote:
> 
> > Greetings,
> >
> > We have been using your svnmailer utility for about a year now on our
> > production repository server.  It has worked perfectly up until Friday
> > when we upgraded python from 2.4.2 to 2.4.3.  When we upgraded, it
> > started to display messages strangely.  If a line is longer than 80
> > characters, it is forced to wrap and a '=' is placed at the end of line.
> >   It also adds "3D" near every instance of a '='.  This presents a
> > problem with URLs to our ViewVC system along with readability of our
> > commit messages.
> 
> Yeah, this is in incompatible change in python 2.4.3 which results in double 
> encoded content (what you see is MIME quoted-printable). You can workaround 
> this problem by configuring
> 
> mail_transfer_encoding = 8bit
> 
> The problem is fixed in version 1.1, which will be released once I find 
> enough time to spare...
> Sorry for the inconvenience.
> 
> nd
-- 
Brian A. Seklecki <bseklecki@collaborativefusion.com>
Collaborative Fusion, Inc.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1161030243.37174.64.camel>