I don't think anything commonly "runs" on these ports. I am also using pmfirewall and found 1024 to be left open by it, so I just put an entry in its conffig file to close it. The test I ran only goes up to 1024, maybe I'll add one for 1025 too. :) vi /usr/local/pmfirewall/pmfirewall.rules.local and copy one of the rules and change the port number like so: $IPCHAINS -A input -p tcp -s $REMOTENET -d $OUTERNET 1024 -j DENY -l It seems to work for me. -s On Wednesday 04 April 2001 11:12 pm, you wrote: > Does anyone know what could possibly be running on ports 1024 and 1025? the > port tester page says it can connect to both ports and I can't figure out > why, I don't run any services and I have PM firewall installed, everything > else is stealthed, why oh why is 1024 and 1025 open?
