Re: Bug? Problems with sending signed messages to mailing lists

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--===============8896770068300717044==
Content-Type: multipart/signed;
    boundary="=_pte5-5986-1601638188-0003";
    micalg=pgp-sha1; protocol="application/pgp-signature"

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_pte5-5986-1601638188-0003
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Sam Varshavchik writes:

> Linux-Fan writes:
>
>> I have tried to debug the problem a little and it seems to be related =
to the
>> handling of whitespace in the e-mails: Throughout transmission, the e-=
mails
>> are re-encoded (?) from "Content-Transfer-Encoding: 7bit" (sent) to
>> "Content-Transfer-Encoding: quoted-printable". The trailing spaces add=
ed by
>
> Whatever is doing that is unaware of signed mail, that's the real probl=
em.
>
>> Now I wonder: Many other people are successfully sending signed messag=
es
>> through the mailing lists. Is there any possibility of changing someth=
ing in
>> Cone such that its messages are less prone to being altered in a way t=
hat
>> makes signature checks fail (i.e. without hampering security, of cours=
e)?
>> Have I overlooked some relevant configuration option or maybe need to =
adjust
>> some GPG settings?
>
> No, you haven't overlooked anything. Cone already uses quoted-printable =
when =20
> the message contains 8-bit characters.
>
> There is no valid reason whatsoever to reencode 7-bit only mail content=
. I =20
> cannot find any documentation that specifies any restrictions on signed =20
> mail, other than to avoid 8-bit content. I cannot assume that the issue =
is =20
> the trailing spaces, that's merely a guess, so after burning time to fi=
ddle =20
> with that, or the other, the likely result is that it makes no differen=
ce =20
> whatsoever. Who knows what's the real bug with whatever is transcoding =
mail =20
> into quoted-printable, for no valid reason whatsoever.
>
> Trying to work around someone else's bugs is a major waste of time. The =20
> correct solution is for someone else to fix the bug.

[...]

Thanks for the quick response! In the meantime I discovered that the =20
workaround is exactly to use some 8-bit characters which will avoid the r=
e-=20
encoding throughout transmission.

My previous mail's signature is invalid.
This mail's signature should be valid.

8-bit-chars: =E2=94=80=E2=94=80 =C3=B6 =C2=A7 =C3=B6 =E2=94=80=E2=94=80

I do not think the spaces are the actual issue here. It is just the =20
discovery that during the re-encoding process they are removed mkaing it =20
impossible to invert that process.

Do I summarize correctly that it is not a bug in cone, but most likely in =20
some software across the transmission?

Thanks again
Linux-Fan

--=_pte5-5986-1601638188-0003
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEkKMBOo1F/f2B6jfK+Elw7bKeCLUFAl93DywACgkQ+Elw7bKe
CLWDhA/9Hz3WP2EewdEafQqQE8T8L4TsPV3sHt3vTNDKLxdXN7ePu7daAA40p1k6
mIixyqQ9lMKLdapTXejGBjQl4sAAwtd6A4SR7rtomUD03xAy6bIj0fe1fkm9Knqo
iR7FhKSIGaz3RP8eDSloLTh+8DeBrFx0TyrlIlYn4VhMMFCRYX2p9fqZLIucWmEf
ES4h4OArLctE0zxItYPhQKLs6vTW2LNhsGIDE3GbYCHAW4sMLLbvwgFKpcl0cm9Z
S/F7m25gU71KZnd+9Viaqt7/B18J9I4rPjJXe8hOKYe0p3jK6fue8ReebCiL9Eqm
ZgfeN5uoxB1sieYHlXiYKpxmLMFDvJfz8dyienxyc2KGusi1P2a7WbmuwwXCoLji
3yzG9vCyNd4/tSC6PouJyjWtcbkEtnAW3CKFliiH45NDPYSqbaYI4DZ0P7R8b9sM
0ATGozkjJABI+yf2QuiFGMFnRiBm5v3e3BRg169i4FrTN46EJQiKnzQ+JP/nJDGy
j9WOGMYWORoOFCcempl35rxrujLWqdMqlb6pffBKAF8Cyjf7jw/jETNg8ctusjCN
Bvv5ll6UrmUNKRd1jfVdiFXH/Mba8NGEs0ge9c/sX25Bn2PmORfv8gyy6dDUT6MY
ZhmWXfhD3jGY0EATZMSA+z/bprk2OTPXCaH3X68ruwPIQX2+Fmk=
=BfkA
-----END PGP SIGNATURE-----

--=_pte5-5986-1601638188-0003--


--===============8896770068300717044==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============8896770068300717044==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Courier-cone mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-cone

--===============8896770068300717044==--