-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi!

> PGP/MIME signed messages occasionally get into trouble with some 
> non-MIME-aware mailing lists, some broken mailing lists, and some 
> archaic mail user agents.
> 
> However, inline PGP messages get into trouble with broken
> character encodings, broken charsets, non-ASCII characters (e.g.
> http://bugs.debian.org/698080), attachments and other common 
> features of the modern e-mail landscape.

What is unclear to me is if inline PGP messages are broken by design.
Bug#698080 more looks like a regression that should be fixable, not an
inherent problem of inline PGP. For attachments, enigmail per default
asks how to send them.

> There is no consensus on the upstream mailing list about whether 
> PGP/MIME or inline PGP should be the default, so upstream's
> default has stayed at inline PGP out of inertia.

As far as I understand from reading a few messages from the upstream
mailing list, any possible default setting has the potential to cause
highly controversial discussions.

> However, debian should try to actively support more than
> english-only e-mail with no attachments.  If there are tools that
> don't cope with PGP/MIME, we should be made aware of them, and we
> should fix those tools rather than expecting all users of
> encryption to limit themselves to english-only e-mail with no
> attachments.
> 
> I think we should default to sending mail in PGP/MIME format.  If
> we can demonstrate that this is functional, this might help break
> the inertia upstream as well.

I not very convinced about deviating from upstream. I could live with
this change if it is acknowledged by upstream, and we treat it as an
experimental change (documented in README.Debian) that we might decide
to take back before the jessie freeze.

WM
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJQ+uDgAAoJEIy+IZx0V22B3twQAJgWcl2ZhEY6K8QzmVrFtxer
fVMZzb4WVzDPOQUhrC1+vJbA3xmwfEKxIIVNlIYZbRRdRNxlvqitYYeyyBKauo0q
cNVWsk34z1it19WSoGR6DeVHv0mPs3wLNHYjj1Y5ma4I2NzeWem0ec+3UWmBsIpQ
KIzOBHHKjzBb2Mk3qo2tTBNWQr3t0SYRJluoQwf0ogzvLVoivRIM86xtQLQObBZU
4eyAF6R8kb0PlBMy5PQSlvepaygJUpw1UCvItq/nLpi6LArZZZENuPwLEw8u866R
4fdst1FA2cEhLvGeNqexpEiWm+brv1fdRu/0Gk4ru1M16ldWIMfxev7Vya0qKQ8l
6LT7niiRGXGaRS3XJFCcWvFIs1J0x8DVQl5lW5Ru3srcqUEqd65T5bbWKfKtMklI
kwcgFjuKKEWo4GE+d5AmjQ1s0q2nEboS5u2SPqNfTV9vJ2NXaA6YFUTYoG8ES/k/
8eRn8ZXbT1Er8a/hUgy1QIkXjhPGSSFkLpa2htgJRPV23ASOBHVdyk9rnsIzBKgK
1Y28btSpqbofYXyrdYxnC2rMuqMLxBQ4fuuQbzMT7xdFfgtPlrjqlFgFY69wZgak
VONzxkIjEzLW3WrxvJmdx0SUXaMMsQ8qXuSPFeK2wRsWC6FNetXrQqHElnwkch0B
4TiOpuV99OhczpIyZZ7V
=CEIV
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to