-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paula,
On Tue, 18 Sep 2001 22:02:34 -0400, you contributed this to our
collective wisdom:
...
P> Here's a related question that is on topic. It's being reported that
P> this Nimda worm when received in an email will execute when the
P> message is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paula,
On Tue, 18 Sep 2001 22:02:34 -0400, you wrote these comments:
...
P> Here's a related question that is on topic.
Good. :-)
P> It's being reported that this Nimda worm when received in an email
P> will execute when the message is opened, t
Here's a related question that is on topic. It's being reported that
this Nimda worm when received in an email will execute when the
message is opened, that is, that it doesn't require opening an
attachment. I've seen, at least one report that said the attachment is
not even apparent. The attachm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Rob,
On Tue, 18 Sep 2001 23:57:27 +0200, you wrote these words of wisdom:
...
R> it's only dangerous if you're running IIS ... over the past half
R> hour i had 7 IP's probing port 80 several times ; it seems to be a
R>
Hello all,
on Tue, 18 Sep 2001, at 16:33:35 local time (GMT -0600), Douglas wrote:
DH> none of them are coming in with atGuard stopping any and all attempts,
it's only dangerous if you're running IIS ...
over the past half hour i had 7 IP's probing port 80 several times ; it
Hello Rob & others on this TB! list & following this thread,
Tuesday, September 18, 2001, you stated regarding Port 80:
DH>> I use the atGuard firewall and have been getting a high number of
DH>> "inbound TCP network communications" to http port 80,
R> probab
Hello all,
on Tue, 18 Sep 2001, at 11:54:40 local time (GMT -0600), Douglas wrote:
DH> I use the atGuard firewall and have been getting a high number of
DH> "inbound TCP network communications" to http port 80,
probably CodeRed(II) probes ; i'm still getting them too ..
Hello Thomas & others on this TB! list & following this thread,
Tuesday, September 18, 2001, you stated regarding Port 80:
TF> ... You should not have any traffic on your local port 80, unless
TF> you run your own server, as Lars said.
I had already allowed calls by Opera &am
Hello Douglas,
On Tue, 18 Sep 2001 12:43:54 -0600 GMT (19/09/2001, 02:43 +0800 GMT),
Douglas Hinds wrote:
>> This is probably due to a new worm out there, trying to infect all web
>> servers. It attempts to connect on port 80 (the port web servers listen
>> to), and then
Hello Douglas,
On Tue, 18 Sep 2001 12:24:25 -0600 GMT (19/09/2001, 02:24 +0800 GMT),
Douglas Hinds wrote:
DH> Thanks. OTOH, what would happen I made a rule to allow all instances
DH> of it.
You will be able to browse the WWW.
DH> When you say "the remote address" you are describing the url
DH>
Hello Lars, Otto & others on this TB! list & following this thread,
Tuesday, September 18, 2001, you stated regarding Port 80:
LG> Port 80 is used for incoming HTTP connections. So, if you don't run a
LG> web server on your box, it's OK to drop all incoming packets wi
Hallo Douglas,
DH> What would happen if I ruled out *any* TCP network communication to
DH> http port 80?
That depends. :-)
Are you running a service on your computer that listens to port 80?
That could be something like a proxy- or a web-server. Are you running
any server-applications
Hello Ottar,
On Tue, 18 Sep 2001 19:28:14 +0200 GMT (19/09/2001, 01:28 +0800 GMT),
Ottar Grimstad wrote:
OG> Does not this mean that as long as he does not run a web-server, it
OG> will be OK to block INCOMING traffic to port 80 on his own machine?
Yes, but since he mentioned Op
Hi Douglas,
On Tue, 18 Sep 2001, at 11:54:40 -0600, you wrote:
DH> I use the atGuard firewall and have been getting a high number of
DH> "inbound TCP network communications" to http port 80, with no
DH> application being identified as the source. The IP numbers vary, as
Hello Thomas & others on this TB! list & following this thread,
Tuesday, September 18, 2001, you answered my query regarding Port
80 as follows:
DH>> What would happen if I ruled out *any* TCP network communication to
DH>> http port 80?
TF> You wouldn't be able to
Hello Thomas,
Tuesday, September 18, 2001, 7:10:08 PM, you wrote:
DH>> What would happen if I ruled out *any* TCP network communication
DH>> to http port 80?
TF> You wouldn't be able to browse the web.
DH>> Does TB! use it?
TF> No, but your web browser does. S
Hello Douglas,
On Tue, 18 Sep 2001 11:54:40 -0600 GMT (19/09/2001, 01:54 +0800 GMT),
Douglas Hinds wrote:
DH> What would happen if I ruled out *any* TCP network communication to
DH> http port 80?
You wouldn't be able to browse the web.
DH> Does TB! use it?
No, but your web br
Hello other TB! List subscribers more technically informed than I
regarding this issue,
I use the atGuard firewall and have been getting a high number of
"inbound TCP network communications" to http port 80, with no
application being identified as the source. The IP numbers var
18 matches
Mail list logo
