X-Spam-Check-By:	sourceware.org
Message-ID:	<44E5A775.1080202@ukf.net>
Date:	Fri, 18 Aug 2006 12:41:41 +0100
From:	Max Bowsher <maxb1 AT ukf DOT net>
Reply-To:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Is cygwin-ml softwere altering message content?
References:	<44E424EE DOT 4070700 AT sh DOT cvut DOT cz> <44E46C29 DOT 3050005 AT ukf DOT net> <44E47377 DOT 4030304 AT scluk DOT com>
In-Reply-To:	<44E47377.4030304@scluk.com>
OpenPGP:	id=C0F2C580
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

--------------enig09A015B8B638B3F40B64EC4F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Al Slater wrote:
> Max Bowsher wrote:
>>> V=E1clav Haisman wrote:
>>>> I have noticed that sometimes my PGP signed messages do not arrive
>>>> intact from cygwin-ml.
>>>> Is this a cygwin-ml software problem?
>>> Yes, something in the ML software seems to like re-wrapping lines. It's
>>> breaking my PGP signatures too.
>=20
> Your signature looks good from here

Amusingly ironic :-)

Seems that that particular message lacked any lines long enough to
trigger the re-wrap.

Let me try to force a re-wrap to occur here:
>23456789A123456789B123456789C123456789D123456789E123456789F123456789G12345=
6789H

The specific nature of the problem seems to be that quoted-printable
MIME parts seem to be getting unencoded and then re-encoded by the
sourceware mail system. In doing so, the wrapping policy applied by the
original mailer is destroyed, and sourceware's own is imposed.

Clearly this is a bad thing, since unless the results of the policies
are identical, the validity of any signature is destroyed.

Is there a suitable sourceware administrator watching this thread, or
should I summarize the issue to overseers@ ?

Max.



--------------enig09A015B8B638B3F40B64EC4F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)

iD8DBQFE5ad7fFNSmcDyxYARAmwpAKClF6xXxIFDlic/Ffru0h9X1FO5YwCfenT1
0MMhoYoSiAD3Z5EnxF9VrnA=
=ZEd5
-----END PGP SIGNATURE-----

--------------enig09A015B8B638B3F40B64EC4F--

- Raw text -