From: "Rich" 

This is a multi-part message in MIME format.

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

   Assuming we are back to the original report you mentioned and we had =
been discussing, the problem is that IE allowed a remote site to = navigate
to the local file and a distinct IE problem with MIME content = tyoes. 
That's it.  This report is just one complex scenario that = exploited the
IE issues and it is just those and not the whole scenario = that is the
problem.

   To use your analogy, the gun has been removed and you have been =
disarmed while you are trying to argue that the problem is with the =
target and not the gun.

Rich

  "Geo."  wrote in message
news:3e31fe37{at}w3.nls.net...
  How can you claim that?  Being able to create a media file that writes =
code
  to disk and then fires up another application to execute that code is =
an
  exploit IMO. Fixing the program being used to execute the code is not =
the
  solution as maybe next time it will be OE or Excel instead of IE that =
is
  used to run the code.

  I have a gun and a target, you hide the target behind a rock and claim =
I've
  been disarmed, that's not true.

  Geo.

  "Rich"  wrote in message news:3e31eefb$1{at}w3.nls.net...
     It's an IE issue.  There is no WMP issue there.

     There is no data binding in the issue we have been discussing.  =
Maybe you
  realized your lies weren't going over.  In any case you switched topic =
to a
  data binding issue and tried to make the bogus claim that opening an =
HTML
  window is the problem which it is not.

  Rich


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








   Assuming
we are back to =
the original=20
report you mentioned and we had been discussing, the problem is that IE = allowed=20
a remote site to navigate to the local file and a distinct IE problem = with MIME=20
content tyoes.  That's it.  This report is just one
complex = scenario=20
that exploited the IE issues and it is just those and not the whole = scenario=20
that is the problem.
 
   To use
your analogy, the =
gun has been=20
removed and you have been disarmed while you are trying to argue that = the=20
problem is with the target and not the gun.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:3e31fe37{at}w3.nls.net...Ho=
w can=20
  you claim that?  Being able to create a media file that writes =
codeto=20
  disk and then fires up another application to execute that code is=20
  anexploit IMO. Fixing the program being used to execute the code =
is not=20
  thesolution as maybe next time it will be OE or Excel instead of =
IE that=20
  isused to run the code.I have a gun and a
target, you hide =
the=20
  target behind a rock and claim I'vebeen disarmed, that's not=20
  true.Geo."Rich"
<{at}> wrote in message news:3e31eefb$1{at}w3.nls.net...=
  =20
  It's an IE issue.  There is no WMP issue =
there.   There=20
  is no data binding in the issue we have been discussing.  Maybe=20
  yourealized your lies weren't going over.  In any case you =
switched=20
  topic to adata binding issue and tried to make the bogus claim =
that=20
  opening an HTMLwindow is the problem which it is=20
not.Rich

------=_NextPart_000_001E_01C2C3EC.BFE3A2E0--

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