|
|
I'm afraid...
Well, as already mentioned above, if the app/service/deamon that would respond to the Incoming port is not running, then no service/port is open on that port - unless it's registred with launchd and then auto-open when traffic comes in on that port (as it has told launchd to respond to that port)
I'm afraid...
Well, I do see denied traffic in the ipfw logs for traffic from ports for apps which are currently running. This shows that unless you open up the port manually in the ipfw preferences, there will be denied traffic on these ports.
And leaving the ports open in the ipfw configuration leaves them always open. I've also seen this from denied traffic to these ports logged in the ipfw logs when these apps aren't running. YMMV.
A better solution...
A port is only "open" if an application is listening on the port, and the port is not blocked by a firewall. If the port is not open, you are not vulnerable on that port (unless your network stack itself is vulnerable, in which case you're very, very screwed and a software firewall probably won't save you). |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.11 seconds |
|