There is a rash of articles about an IE hole (including the one below) that
suggest there was another patch after Tuesday Dec 14 but I'm not clear on
that. The latest patches I could find in microsoft.com were not after Dec.
14.

http://techrepublic.com.com/5100-22_11-5495409.html?part=rss&tag=feed&subj=tr


Norton also had an update for the Bafor worm quite a while ago.

I have XP SP1 - is the new problem just for SP2?

Robert C.

Re: were there any patches after Dec 14 2004? by Bob

Bob
Mon Dec 20 13:07:55 CST 2004

The fix referenced is at
http://support.microsoft.com/default.aspx?scid=kb;en-us;886185

And yes, it is only for SP2 as it effects the scoping of exceptions on the
Windows Firewall. It has nothing to do with IE. The major IE patch was
released out-of-cycle on December 1st. The summary of all the December
bulletins can be found at
http://www.microsoft.com/technet/security/bulletin/ms04-dec.mspx

--
Bob McCoy
* This posting is provided "AS IS" with no warranties, and confers no
rights.
* Please note I cannot respond to email questions. Please use these
newsgroups.


"Robert Chao" <robertjchao@yahoo.com> wrote in message
news:i7SdndMr8-vBvVrcRVn-1w@inreach.com...
> There is a rash of articles about an IE hole (including the one below)
> that
> suggest there was another patch after Tuesday Dec 14 but I'm not clear on
> that. The latest patches I could find in microsoft.com were not after
> Dec.
> 14.
>
> http://techrepublic.com.com/5100-22_11-5495409.html?part=rss&tag=feed&subj=tr
>
>
> Norton also had an update for the Bafor worm quite a while ago.
>
> I have XP SP1 - is the new problem just for SP2?
>
> Robert C.
>
>
>
>



Re: were there any patches after Dec 14 2004? by Robert

Robert
Mon Dec 20 13:22:17 CST 2004

Thanks Bob - By the way, why is the patch mentioned in the first link not
mentioned at all in the second link? Which is one of the pages I always
check.

Also the first link says something about Dec. 18 when the patch was in fact
released Dec. 14.

Robert C.

"Bob McCoy [MSFT]" <bobmccoy@online.microsoft.com> wrote in message
news:u4$xxcs5EHA.3472@TK2MSFTNGP09.phx.gbl...
> The fix referenced is at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;886185
>
> And yes, it is only for SP2 as it effects the scoping of exceptions on the
> Windows Firewall. It has nothing to do with IE. The major IE patch was
> released out-of-cycle on December 1st. The summary of all the December
> bulletins can be found at
> http://www.microsoft.com/technet/security/bulletin/ms04-dec.mspx
>
> --
> Bob McCoy
> * This posting is provided "AS IS" with no warranties, and confers no
> rights.
> * Please note I cannot respond to email questions. Please use these
> newsgroups.
>
>
> "Robert Chao" <robertjchao@yahoo.com> wrote in message
> news:i7SdndMr8-vBvVrcRVn-1w@inreach.com...
> > There is a rash of articles about an IE hole (including the one below)
> > that
> > suggest there was another patch after Tuesday Dec 14 but I'm not clear
on
> > that. The latest patches I could find in microsoft.com were not after
> > Dec.
> > 14.
> >
> >
http://techrepublic.com.com/5100-22_11-5495409.html?part=rss&tag=feed&subj=tr
> >
> >
> > Norton also had an update for the Bafor worm quite a while ago.
> >
> > I have XP SP1 - is the new problem just for SP2?
> >
> > Robert C.
> >
> >
> >
> >
>
>



Re: were there any patches after Dec 14 2004? by Bob

Bob
Tue Dec 21 07:53:53 CST 2004

>>By the way, why is the patch mentioned in the
>>first link not mentioned at all in the second link?

I really don't have a good answer for that one. For whatever reason, MSRC
has not released KB 886185 as a security bulletin. However, it was released
as a Critical Update for Windows XP SP2 under Windows Update and SUS.

--
Bob McCoy
* This posting is provided "AS IS" with no warranties, and confers no
rights.
* Please note I cannot respond to email questions. Please use these
newsgroups.


"Robert Chao" <robertjchao@yahoo.com> wrote in message
news:ONqdnZrkmfj3u1rcRVn-vA@inreach.com...
> Thanks Bob - By the way, why is the patch mentioned in the first link not
> mentioned at all in the second link? Which is one of the pages I always
> check.
>
> Also the first link says something about Dec. 18 when the patch was in
> fact
> released Dec. 14.
>
> Robert C.
>
> "Bob McCoy [MSFT]" <bobmccoy@online.microsoft.com> wrote in message
> news:u4$xxcs5EHA.3472@TK2MSFTNGP09.phx.gbl...
>> The fix referenced is at
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;886185
>>
>> And yes, it is only for SP2 as it effects the scoping of exceptions on
>> the
>> Windows Firewall. It has nothing to do with IE. The major IE patch was
>> released out-of-cycle on December 1st. The summary of all the December
>> bulletins can be found at
>> http://www.microsoft.com/technet/security/bulletin/ms04-dec.mspx
>>
>> --
>> Bob McCoy
>> * This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> * Please note I cannot respond to email questions. Please use these
>> newsgroups.
>>
>>
>> "Robert Chao" <robertjchao@yahoo.com> wrote in message
>> news:i7SdndMr8-vBvVrcRVn-1w@inreach.com...
>> > There is a rash of articles about an IE hole (including the one below)
>> > that
>> > suggest there was another patch after Tuesday Dec 14 but I'm not clear
> on
>> > that. The latest patches I could find in microsoft.com were not after
>> > Dec.
>> > 14.
>> >
>> >
> http://techrepublic.com.com/5100-22_11-5495409.html?part=rss&tag=feed&subj=tr
>> >
>> >
>> > Norton also had an update for the Bafor worm quite a while ago.
>> >
>> > I have XP SP1 - is the new problem just for SP2?
>> >
>> > Robert C.
>> >
>> >
>> >
>> >
>>
>>
>
>