On Tue, 19 Aug 2003, Scott Weeks wrote:
on the .pif, .scr, etc. attachments...) Maybe I was just lucky. Most
likely, though, they did not create security zones to keep problems
contained within certain network segments and not let them out to destroy
other networks.
Luck is very important.
On Tue, 19 Aug 2003, Scott Weeks wrote:
- on the .pif, .scr, etc. attachments...) Maybe I was just lucky. Most
- likely, though, they did not create security zones to keep problems
- contained within certain network segments and not let them out to destroy
- other networks.
-Luck is very
The new EDS managed Navy Marine Corps Intranet with 100,000 users has
become so congested by worm traffic it can not be used for useful work
today.
http://www.nwfusion.com/news/2003/0819navy.html
Obviously they didn't filter 135, 137-139, 445, and inbound
Not obvious. I know of several sites that were infected even though they
had filters in place, due to infected laptops being brought on-site.
Vern
Yo Scott!
They better start blocking port 25 too. That has been the big problem
today...
RGDS
GARY
---
Gary E. Miller Rellim 20340 Empire Blvd, Suite E-3, Bend, OR 97701
[EMAIL PROTECTED] Tel:+1(541)382-8588 Fax:
On Tue, 19 Aug 2003 [EMAIL PROTECTED] wrote:
: Obviously they didn't filter 135, 137-139, 445, and inbound
:
: Not obvious. I know of several sites that were infected even though they
: had filters in place, due to infected laptops being brought on-site.
:: The new EDS managed Navy
Obviously they didn't filter 135, 137-139, 445, and inbound
Not obvious. I know of several sites that were infected even though they
had filters in place, due to infected laptops being brought on-site.
Filtering ports 135, 137-139, 445, and only delays the inevitable...
