Firefox/Mozilla exploit semi-permanenet fix

[Roger Oberholtzer]

On Fri, 2005-02-11 at 15:39, Net Llama! wrote:
> On Fri, 11 Feb 2005, Roger Oberholtzer wrote:
> > On Fri, 2005-02-11 at 13:20, David Bandel wrote:
> > > On Fri, 11 Feb 2005 08:05:16 +0100, Roger Oberholtzer <roger at opq.se> wrote:
> >
> > > > You just need to learn your keyboard's modifiers (which may or may not
> > > > be enabled). You misht have a ~ character on a key. On mine, I can press
> > > > that once (nothing prints), followed by a normal n, and I get ???. In X, I
> > > > think these are called compose keys. Same with the ^, `, ??? and ???
> > > > modifiers. I do not recall which ones, if any, are on a US keyboard. But
> > > > I do know that you can define keys to be compose keys. Maybe it is a
> > > > different X keymap.
> > >
> > > Yes.  I need the ???, so my XF86Config-4 has a keymap called us_intl
> > > rather than the usual us keymap.
> >
> > David,
> >
> > When this message came back from you, the characters in question were
> > garbled. When replies come form others, this is not the case. I see that
> > my posts contain:
> >
> > 	Content-Type: text/plain; charset=ISO-8859-1
> >
> > in the headers. Your envelope around that in the reply contains
> >
> > 	Content-Transfer-Encoding: quoted-printable
> >
> > I would have thought that my e-mailer (evolution) would have dealt with
> > your wrapper (quoted-printable), and then used the nested
> > charset=ISO-8859-1 for the text I wrote.
> >
> > Maybe the interleaving of your reply with my text confused the issue?
> >
> > How odd. Anyone else see odd characters (not the original I sent) in
> > David's reply? Also, David's ?? (an 'n with a tilde in case there is more
> > of this) came as something totally different.
> >
> > I do not think the mailing list is doing this as my posts with these
> > characters look correct when I receive them back from the mailing list.
> > It is only David's post.
> >
> > All not really an issue. More of a curiosity.
> 
> Its your mail client.  The tilde ~ looked fine in the original from David,
> however is now munged in your reply.

Perhaps... The message that 'worked' came from home running a newer
version of evolution. The one with the messy characters came from an
older evolution I use at work. But that is not the whole story.

I think it could be the interaction between different content type
settings. I see that the messages have a mixture of:

	Content-Type: text/plain; charset=iso-8859-1

	Content-Transfer-Encoding:  8bit

	Content-Transfer-Encoding:  quoted-printable

The first two are what my text messages use, as that is the encoding we
use in these parts. And, my evolution mailer seems to have that setting
for both character encoding and character set on messages originating
here. The quoted-printable is from elsewhere. It looks to me that
whoever is making the message quoted-printable is doing this to the
content - BUT leaving the original 8-bit encoding label as well. It
cannot be both at the same time. I am sure there is a rule for the order
these are used in parsing a message. Maybe my old evolution has it
wrong. But I am not sure...


+????????????????????????????+???????????????????????????????+
? Roger Oberholtzer          ?   E-mail: roger at opq.se        ?
? OPQ Systems AB             ?      WWW: http://www.opq.se/  ?
? Nybrogatan 66 nb           ?    Phone: Int + 46 8   314223 ?
? 114 41 Stockholm           ?   Mobile: Int + 46 733 621657 ?
? Sweden                     ?      Fax: Int + 46 8   314223 ?
+????????????????????????????+???????????????????????????????+