Apologies, long days are affecting my faculties and I didn't make myself too clear. Sorry

<br>
<br>
Yes, the IPchains article is the one I was talking about. You're heading into firewall territory with IPchains, and it's part of the overall point I was trying to make. That is, make sure your server is secure before connecting it up to the 'net.<br>
<br>
Even though Linux/Unix is more secure 'out of the box' than Windows, there are still security issues you need to be aware of. ie, sendmail can be a security hole if you run an old version; rlogin (and other 'r' commands) can be a major security hole if misconfigured; and misconfigured FTP servers can open your box up to all kinds of nasty abuse. Just to name a few ;^)<br>
<br>
Some of these issues aren't Linux/Unix specific, but you need to be security conscious when connecting up a server to the 'net, no matter if it's Linux, FreeBSD, Solaris, HP/UX, or some other OS that might hail from Redmond, WA ;^)<br>
<br>
Regarding the remote port scanning, a better description, as lifted from the CERT web site, is "Distributed Denial of Service Tools" - jump to <A HREF="
TARGET="_new">
for more details. There's also the results of a recent conference discussing this problem at <A HREF="
TARGET="_new">
<br>
<br>
In a nutshell, I don't think there's a fix as such for the problem. The first link above discusses actions to take to prevent your system being abused by the vandals that want to run these sort of programs. Again, in a nutshell, this boils down to "know your system" and "secure your system".<br>
<br>
I'm not trying to scare anybody here, just trying to make you aware that security is important in the modern 'net enabled world

<br>
<br>
Don't be put off by any of the above. While securing your system, you'll also learn a hell of a lot about it, and about Linux and Unix in general. Most of all, it could be fun, so enjoy

<br>
<br>
Hope this helps a little more than my last post.
