Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Don't disable ports 3000-3999' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Don't disable ports 3000-3999
Authored by: Anonymous on Apr 06, '02 06:20:29PM

There is really no need to close the TCP ports in the 3000-3999 region.

If you close UDP 2222, then no other computers will know which TCP port your copy of word has chosen to listen to (in the 3000-3999 range), because that info is broadcasted in the UDP packets. The protocol is thus: Your copy of word spews it's serial number (encoded) and the TCP port it is listening on in a packed on UDP 2222. Other copies of word on the network get this packet and then respond the your copy of word on the specified TCP port if they have the same serial. Then one copy shuts down.

So no need to block the TCP port range, because other copies of word will never even hear about your copy and thus won't try to contact it.

Sure, some 1337 hax0r could try to crash your copy of word by trying every serial number on all 1000 TCP ports, but that's more or less unlikely.

The reason I recommend against blocking the TCP ports is that things may run on TCP 3000-3999, and you don't want to inadverterntly break those.



[ Reply to This | # ]
Don't disable ports 3000-3999
Authored by: tsaar on May 21, '02 03:44:50PM

Hmm, interesting

But I guess the L337 H4x0r does not have to try I guess.

If he does a portscan on 3000 - 3999 first he'll know what ports you're listening on.....

The thing is: it's just not nice to have 'uncontrolled' listening ports opened up by any program when you are connected to the net 'barenaked' like I am.....

I'm blocking 3000 - 3999 (even if it screws up my ability to use active FTP sessions.....)



[ Reply to This | # ]