Firewall Wizards mailing list archives
Re: TCP port 7 traffic from DoubleClick
From: David Lang <dlang () diginsite com>
Date: Tue, 13 Jul 1999 17:26:16 -0700 (PDT)
-----BEGIN PGP SIGNED MESSAGE----- I have spoken to Resonate recently on this issue and they report that TCP port 7 has proven to be one of the more effective ports to use (i.e more people block pings). Also for the record the Global Dispatch is a DNS failover/load-balancing bind replacement, not an advertising tool in particular. David Lang On Tue, 13 Jul 1999, Timothy K. Ewing wrote:
Date: Tue, 13 Jul 1999 16:02:05 -0400 From: Timothy K. Ewing <EwingTK () celera com> To: firewall-wizards () nfr net Subject: Re: TCP port 7 traffic from DoubleClick We saw this same kind of behaviour back on May 3, 1999. I contacted Dave Smith at Doubleclick and inquired as to why this was happening. At that time he indicated that his company was using a product called Resonate Global Dispatch, an internet advertising tool, which identifies the closest DNS servers to the client. The program gathers some type of metrics by connecting to DNS servers. He indicated that they had recieved lots of other complaints in addition to mine and that they would probably move to using 'pings' instead. Looks like they may have switched to connecting to the echo port for those systems that have it open (a bad port to have open anyway). I have not called them lately to verify this progression by I suspect that this is what is happening. Timothy K. Ewing Security Analyst Celera Genomics Corp.
"If users are made to understand that the system administrator's job is to make computers run, and not to make them happy, they can, in fact, be made happy most of the time. If users are allowed to believe that the system administrator's job is to make them happy, they can, in fact, never be made happy." - -Paul Evans (as quoted by Barb Dijker in "Managing Support Staff", LISA '97) -----BEGIN PGP SIGNATURE----- Version: PGP for Personal Privacy 5.0 Charset: noconv iQEVAwUBN4vZKj7msCGEppcbAQGFBwf/S0cPZN5B0+2zLcfNEb1V3bGnBc2M6qOu l3PYnAx04t9Sx4PwLGr63Dvq8YEOdLHwVyeiL79HtmBWdtkt9iIEYv93FhZHRNMC W+70k+DGSm82fE4f+9Zk5i9a2RRIatgu0aIOzTC2t6v+92Lw1jlrb7gMGvKR2f2A JUhNhQJHFY6/e3s21/1XNWUSPEk6AdWhXjr+eDOzW+YbdYROgpx6tQnQXo6iLTx+ zQaGmn+1svqS6u5K10t//8Yh2xAG3UTOSAX7n3NL6NkXUwyJ/dJlUBjKthF17z0D 75t8wktCAvPNIpeKmdrA+yoBN0zPOjSv7huKynyna/MmKRNHT6gKNA== =DzlJ -----END PGP SIGNATURE-----
Current thread:
- Re: TCP port 7 traffic from DoubleClick, (continued)
- Re: TCP port 7 traffic from DoubleClick C. Harald Koch (Jul 06)
- Re: TCP port 7 traffic from DoubleClick Joseph S D Yao (Jul 12)
- Re: TCP port 7 traffic from DoubleClick Vern Paxson (Jul 06)
- Re: TCP port 7 traffic from DoubleClick Neil Ratzlaff (Jul 09)
- Re: TCP port 7 traffic from DoubleClick Albert Hopkins (Jul 12)
- Re: TCP port 7 traffic from DoubleClick Neil Ratzlaff (Jul 09)
- Re: TCP port 7 traffic from DoubleClick Vern Paxson (Jul 07)
- RE: TCP port 7 traffic from DoubleClick Mason Begley (Jul 08)
- Re: TCP port 7 traffic from DoubleClick ark (Jul 12)
- Re: TCP port 7 traffic from DoubleClick R. DuFresne (Jul 12)
- Re: TCP port 7 traffic from DoubleClick Timothy K. Ewing (Jul 13)
- Re: TCP port 7 traffic from DoubleClick David Lang (Jul 14)
- Re: TCP port 7 traffic from DoubleClick C. Harald Koch (Jul 06)
