Hi,
Running 10.2.8.
I'm using Norton Personal Firewall 3.0 and I like it. I was using the built in firewall in OSX for a while and it's allright, but I like the extra stuff that comes with norton. (logging and ease of use)
When I go to www.grc.com and test my firewall with shieldsUp! I get the same result each time... Failed on port 0... the "fake" port. (Explanation of Port 0 Below). Everything else is running in "stealth"
I tried to specify an action on Port 0 to "deny incoming" but Norton Firewall won't let me select Port 0, says Port 0 doesn't exist.
PS - I tried installing brickhouse to configure the OSX firewall, but I got worse results than with just using the OSX interface. More "Closed" ports then stealth ports.
Thanks for your help.
The explanation for Port 0 said:
Name:*
<nil>
Purpose:*
Not a valid port number.
Description:*
"Port Zero" does not officially exist. It is defined as an invalid port number. But valid Internet packets can be formed and sent "over the wire" to and from "port 0" just as with any other ports
Background and Additional Information:
The designers of the original Berkeley UNIX "Sockets" interface, upon which much of the technology and practice we use today is based, set aside the specification of "port 0" to be used as a sort of "wild card" port. When programming the Sockets interface, the provision of a zero value is generally taken to mean "let the system choose one for me". Programmers who specify "port 0" know that it is an invalid port. They are asking the operating system to pick and assign whatever non-zero port is available and appropriate for their purpose.
As a result of this programming convention, there has traditionally been no way for Internet Sockets programmers to generate or receive "port 0" Internet traffic. So port zero was set aside and never defined or used. Although times and technology have changed dramatically, port zero has remained something of an unexplored "no mans's land".
However, with the widespread and growing availability of operating systems offering the "Raw Socket" programming interface which provides the means for deliberately generating port zero packets the presence and security of "port zero" is of growing importance.
The "Port Authority" revision to GRC's ShieldsUP! services and NanoProbe technology offers the generation of port zero probes to enable users to verify, secure, and stealth their system's handling of these potentially troublesome Internet packets.
Running 10.2.8.
I'm using Norton Personal Firewall 3.0 and I like it. I was using the built in firewall in OSX for a while and it's allright, but I like the extra stuff that comes with norton. (logging and ease of use)
When I go to www.grc.com and test my firewall with shieldsUp! I get the same result each time... Failed on port 0... the "fake" port. (Explanation of Port 0 Below). Everything else is running in "stealth"
I tried to specify an action on Port 0 to "deny incoming" but Norton Firewall won't let me select Port 0, says Port 0 doesn't exist.
PS - I tried installing brickhouse to configure the OSX firewall, but I got worse results than with just using the OSX interface. More "Closed" ports then stealth ports.
Thanks for your help.
The explanation for Port 0 said:
Name:*
<nil>
Purpose:*
Not a valid port number.
Description:*
"Port Zero" does not officially exist. It is defined as an invalid port number. But valid Internet packets can be formed and sent "over the wire" to and from "port 0" just as with any other ports
Background and Additional Information:
The designers of the original Berkeley UNIX "Sockets" interface, upon which much of the technology and practice we use today is based, set aside the specification of "port 0" to be used as a sort of "wild card" port. When programming the Sockets interface, the provision of a zero value is generally taken to mean "let the system choose one for me". Programmers who specify "port 0" know that it is an invalid port. They are asking the operating system to pick and assign whatever non-zero port is available and appropriate for their purpose.
As a result of this programming convention, there has traditionally been no way for Internet Sockets programmers to generate or receive "port 0" Internet traffic. So port zero was set aside and never defined or used. Although times and technology have changed dramatically, port zero has remained something of an unexplored "no mans's land".
However, with the widespread and growing availability of operating systems offering the "Raw Socket" programming interface which provides the means for deliberately generating port zero packets the presence and security of "port zero" is of growing importance.
The "Port Authority" revision to GRC's ShieldsUP! services and NanoProbe technology offers the generation of port zero probes to enable users to verify, secure, and stealth their system's handling of these potentially troublesome Internet packets.