Okay for ICQ the problem with it, is that it opens a great number of ports.. On Conseal PC Firewall to enable ICQ you must set two entries one is TCP connection to internal ports > 1024 (you would think they would know how to fork sockets), then you must create a UDP rule that allows for connections on all UDP 4000 If I remember.. it basically opens the complete network to attack. This was honestly a poor design problem on the maker's of ICQ side. For Real Audio it's the same reasoning... except RA Server opens ports above 6900 Now for securing them.. for ICQ. you can use 2 methods of securing them. A) Socks Server configure to connect through it. B) Limit ports that can be used by ICQ for incoming connections. in ICQ. and block all but those ports. For RA manually configure it to use a specific port, by default.. the manually definied port, is 7070 On 23 Dec 99, at 1:40, Firewalls-Digest wrote: > Date: Wed, 22 Dec 1999 23:03:55 -0500 (EST) > From: Dave Wreski <[EMAIL PROTECTED]> > Subject: Re: firewall identification > > > It sounds to me like your firewall is doing its job then. Protocols > > like ICQ and RealAudio open a network up to more risk, and probably > > your administrator is not willing to take that risk. > > Do you happen to know where there is any information on the net that > explains why ICQ/RA is a risk? Something that I can present to > management? > Jason Robertson Network Analyst [EMAIL PROTECTED] http://www.astroadvice.com - [To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe firewalls" in the body of the message.]
