| |||||||||||||||||||||
|
Need to Block Instant Messaging? Members of the ISP-Security list find that it's quite difficult to block most instant messaging programs, and suggest personal rather than technical solutions for businesses that lack the bandwidth to keep staff on instant messengers all day.
On the ISP-Security list in October, EC inquired,
A couple of respondents had specific suggestions for EC's concerns: [JR offered] "ICQ is pretty easy to block, or at least the older version was. Just block UDP 4000: if it can't connect to the main server, it's unable to send messages beyond that. You could also block incoming ports above 1024, and this stops ICQ as well." [CS added] "The only way to effectively do this is to block the destination hosts that these services use. This will be a difficult-to-maintain solution because the services can change these at will. Several of these services use clients that tunnel over normally allowed ports plus lots of others. They don't have a single well-known port that they all use." KW warned that none of these solutions would be simple:
Others noted that there might be less technical ways to deal with concerns regarding instant messaging: [CS observed] "This isn't a technology problem, it's an administrative one. If people aren't allowed to use these services, enforcement via logs might be a better option. After a few folks are busted, others will simply stop." [BL concurred] "You would be better advised to treat this as a staff policy issue rather than attempting to block it-unless they only want HTTP and mail, in which case it would be easier to simply block everything except the ports which those require. Don't forget, also, that many software packages have anti-firewall features which will allow them to be used on ports under 1024."
End
|
|
|||||||||||||||||||
|
|
|||||||||||||||||||||