From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_01F9_01C34C71.D9B74D30
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   It works correctly for all valid scenarios.  I agree that the folks =
that made the typo should have recognized it but the typo was one that =
was semantically very similar to what should have been there.  Only if =
one particular line in a file was maliciously constructed is there an =
issue.  None of this is an excuse.  It's a bug.  I'm just pointing out =
the error in George's statement and in the title of the bulletin from =
Microsoft.

Rich

  "Ellen K"  wrote in message =
news:b099ab.f18a79{at}harborwebs.com...
  I would have expected this to be tested, the test to fail, and the =
typo to be
  found at that time.

------=_NextPart_000_01F9_01C34C71.D9B74D30
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   It works
correctly for all =
valid=20
scenarios.  I agree that the folks that made the typo should
have=20 recognized it but the typo was one that was semantically very
similar to = what=20
should have been there.  Only if one particular line in a file
was=20 maliciously constructed is there an issue.  None of this is
an=20 excuse.  It's a bug.  I'm just pointing out the
error in = George's=20
statement and in the title of the bulletin from Microsoft.
 
Rich
 

  "Ellen K" <Ellen.K{at}harborwebs.com>">mailto:Ellen.K{at}harborwebs.com">Ellen.K{at}harborwebs.com>
=
wrote in=20
  message news:b099ab.f18a79{at}harborwebs.=
com...I=20
  would have expected this to be tested, the test to fail, and the typo =
to=20
  befound at that
time.

------=_NextPart_000_01F9_01C34C71.D9B74D30--

--- BBBS/NT v4.01 Flag-4