>FUD! FUD! FUD!

Just to be clear. The bug exists -- and has been duplicated -- from an
interactive session. I'm saying that I don't see why it wouldn't exists
too in batch.


>"if a user visits a malicious website"

OK, perhaps I didn't make my point clear. We're speaking of servers
here, not clients. I'm speaking of bugs that can infect a machine on an
Inbound request to port 80 (443 for SSL). 

If you don't have a firewall blocking all but port web traffic to a web
server, you should be taken out back and shot. If you are browsing the
web from a server you should be taken out back and shot. If you are
running outlook on a server, you should be taken out back and shot. If
you haven't followed best-practices for locking down IIS and running
(and re-running) baseline security analysis you should be taken out back
and shot!

JMTCW. 

-Walden


------------
Walden H Leverich III
President & CEO
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
  


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.