You guys are gonna LOVE *this*.
I'd forgotten about "grc.com", and have never tried it with my Linux system. (thanks to whoever reminded me...)
Guess what (get ready for THIS...)
The GRAPHICS on Gibson's site won't display on MY machine, and I'm seeing the SAME BEHAVIOR out of his site!!!!! I'm getting repeated port access attempts from "image.grc.com" on ports in the 32xxx (and now 33xxx) range, failing to connect to some service...
Of course, none of GRC's port analysis goes up that far and he doesn't discuss those ports (which, as someone pointed out, are *unassigned*).
So!! The bottom line is, Gibson Research, purveyor of all paranoias about open ports, is demanding that a port be open in order to see the graphics on their page!
That just takes the pot. (I can still get their analysis to work by clicking on the "red X's".
This is getting REAL interesting... I guess I'm going to have to track down that wacked-out port access behavior (and find out why it's linked to graphic access).
Just what I need. Another case of extreme nerdism. Like I don't have ENOUGH problems. And all because I wanted to look at that broad in the gold dress! There's a lesson in this. God is trying to tell us something. !@#$%^&!!!!!
You may have to wait until Feb 1st to see her - the server has reached its monthly bandwidth limit - Free Republic is just too popular (much like the one in the Gold Dress...)
If you check the source of the graphic, it's: http://image.grc.com which is a secure directory on the grc website. The directory on the rfny.us server is also a secure directory (using Apache/1.3.33 Server at www.rfny.us)
Come on guys - y'all know you can't access secure sites without authentication, which means that since FR is the only authenticated referrer, your browser MUST pass referrer info to the secure site. If your system is configured to prevent that, you are not going to get the pics.
MSDN indicates that when configuring services running on a server, one can specify the port or port range that the service will use, & those with lower priority should use the higher range. It also indicates that, if not specified, additional ports (over common assigned ports) are assigned a random range.
I don't see the problem here. If you guys still want more answers, I recommend you check the following resources:
A tech security discussion forum on grc.com: http://www.grc.com/discussions.htm
The solution is simple - either enable website tracking in your firewall or other security software, or not.
Or just get a packet sniffer and see what info is transmitted on the port in question.