Messenger Spam Pop-Ups

[a]

that's no good - the XP firewall stops everything from
working, so that's not really an option. Besides, why
should I have to install a spurious level of security
purely because of a Microsoft bug - shouldn't they fix
it ?

>-----Original Message-----
>Go read
>http://support.microsoft.com/default.aspx?id=330904
>
>>-----Original Message-----
>>Does anyone know if Microsoft have any plans to plug
the
>>hole that allows anyone with a modem to grab hold of my
>>pc by using the gaping hole in Microsoft's XP (most
>>commonly illustrated by huge amounts of spam pop-ups
>>being sent to your pc through an "open" port with
>Windows
>>Messenger even when messenger is closed and you don't
>>have email etc etc) ?
>>This is annoying beyond belief, and surely Microsoft
are
>>liable/negligent if they don't fix it as soon as they
>>hear about it ?
>>.
>>
>.
>

[Alun Jones]

In article >, "a" > wrote:
>that's no good - the XP firewall stops everything from
>working, so that's not really an option. Besides, why
>should I have to install a spurious level of security
>purely because of a Microsoft bug - shouldn't they fix
>it ?

No. You should install a firewall, on the simple grounds that any system is
protected well behind a firewall, rather than relying on that system not
being compromised by any and all software you run on it. A firewall, by
comparison with the OS that you use, is really small, and has more of a
chance that its code paths have been checked and secured.

If you were using Linux, or VMS, or any other operating system, and
connected to the Internet, I'd suggest using a firewall.

Now, what is this "everything" that the firewall stops from working? Have
you considered learning how to open up the firewall for those parts that
_you_ want to work? The goal of a secure firewall is to lock everything
down, and then open up only those parts that you authorise to access the
Internet. Apparently, you are upset that the firewall you have installed is
working properly.

You see bugs, where others simply see "software configured by default to a
setting that I wouldn't personally have chosen for my use". Get used to
this. Products in future will arrive locked-down by default, and you will
have to open them up for whatever use you have.

Alun.
~~~~

[Please don't email posters, if a Usenet response is appropriate.]
--
Texas Imperial Software | Find us at http://www.wftpd.com or email
1602 Harvest Moon Place | .
Cedar Park TX 78613-1419 | WFTPD, WFTPD Pro are Windows FTP servers.
Fax/Voice +1(512)258-9858 | Try our NEW client software, WFTPD Explorer.

[Tom Della-Latta]

You are too stupid to use a computer please donate yours to your local home
for the mentally challenged, Someone there could get better use of it.

Tom

"a" > wrote in message
...
> that's no good - the XP firewall stops everything from
> working, so that's not really an option. Besides, why
> should I have to install a spurious level of security
> purely because of a Microsoft bug - shouldn't they fix
> it ?
>
> >-----Original Message-----
> >Go read
> >http://support.microsoft.com/default.aspx?id=330904
> >
> >>-----Original Message-----
> >>Does anyone know if Microsoft have any plans to plug
> the
> >>hole that allows anyone with a modem to grab hold of my
> >>pc by using the gaping hole in Microsoft's XP (most
> >>commonly illustrated by huge amounts of spam pop-ups
> >>being sent to your pc through an "open" port with
> >Windows
> >>Messenger even when messenger is closed and you don't
> >>have email etc etc) ?
> >>This is annoying beyond belief, and surely Microsoft
> are
> >>liable/negligent if they don't fix it as soon as they
> >>hear about it ?
> >>.
> >>
> >.
> >


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.476 / Virus Database: 273 - Release Date: 4/24/2003

[Robert Moir]

a wrote:
> that's no good - the XP firewall stops everything from
> working, so that's not really an option. Besides, why
> should I have to install a spurious level of security
> purely because of a Microsoft bug - shouldn't they fix
> it ?

What bug was that again?