In-Reply-To: <3C8BE35E.9532.44F0C@localhost>
There has been a lot of discussion on this message.
There has been to much emphasis on OS, Browser,
Or Virus scanning technology... (too many opinions.)
These are factors, but the bottom line is really
access and permissions to the "local" file that is
being "remotely" executed. {Whatever the file is..}
The method of the execution is important, but most of
us probably will not disable scripting, simply because
it makes browsing the internet a royal pain, and we
are a convenience driven society...
So lets look at the issue at a much lower level. There
are lots of files that could be executed in this
situation, but if the files were regulated to whom used
then, then malicious activity can be greatly reduced.
Meaning, this situation will only work if the person,
currently logged on, has access to the file trying to be
executed. As in my earlier message, I like to lock
down files that could cause me heartache if someone
got access to them remotely. ( meaning cmd.exe,
telnet.exe, ftp.exe, etc....) Files that should be only
used by the local administrator. Also it is not a good
practice to log on to your box all of the time as admin.
It's just a lazy habit. And a risky one. Just remove all
access to potentially dangerous files, with the
exception of an local admin account. And only log on
when you are performing system maintenance.
Maybe a little over the top, but it works..
My .02
Chad
