> -----Original Message----- > From: 'Klaus Ethgen' [mailto:kl...@ethgen.de] > Sent: Sunday, January 01, 2017 12:23 > To: Jason Pyeron > Cc: 'Willi Mann'; 849...@bugs.debian.org; > logwatch-de...@lists.sourceforge.net > Subject: Re: Bug#849531: [Logwatch-devel] Bug#849531: > Possible security problem,new logwatch sends mails with charset UTF-8 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Am So den 1. Jan 2017 um 17:38 schrieb Jason Pyeron: > > > What do you want to say with that? Your input is not in UTF-8. > > > > That is the point. The OP complaines about ASCII being sent > when labeld as UTF8, as such it created invalid UTF8 sequences. > > No, I complain about non UTF-8 being send as UTF-8. > > Namelly, bytes values 0-255.
Yes, 8-bit ASCII, here is a translation table. ASCII|UTF-8 00 | 00 01 | 01 ... 7E | 7e 7F | 7f 80 | c2 80 81 | c2 81 ... BE | c2 be BF | c2 bf C0 | c3 80 C1 | c3 81 ... FE | c3 be FF | c3 bf > > Below 128 it is not a problem as UTF-8 is transparent in this > range. But > above 128 it _is_ a problem. No, only when not ENCODED properly. UTF-8 is very, very, likely going to stay. -Jason
