Indeed, this is the basic problem in trying to halt social issues
(what employees 'should' and 'should not' use) with technical
solutions. You can block ports, protocols, even destinations... but
there is enough impetus for the software to find ways through your
blocks.
If you don't want employees using these programs... make it a company
policy. Set up a sniffer and fire the first few people who break
policy, it won't eradicate useage... but it will seriously curtail it.
J�rgen Nieveler writes:
> > Or block all udp traffic and then selectively allow what you need
> > (excluding known ICQ ports for example).
>
> That won't help with ICQ2000 anymore... they are able to use TCP. I've seen
> ICQ2k run over Port 23/TCP without Problems... it even scans for Ports it
> could use.
>
> Mit freundlichen Gr��en / Yours sincerely
>
> Juergen Nieveler
> arxes Software Factory AG
> UB eCommerce
> Tel.: +49/241/16008-327
> Fax: +49/241/16008-354
> Email: [EMAIL PROTECTED]
> Web: www.arxes.de
> PGP:
> 2AAB A988 0B80 D53F FC53 3BED 8CC0 2092 922D 8378 (DH)
> 5ADF A15E 91E4 98DB 2391 0D29 8B08 A884 (RSA)
> Disclaimer: Views are mine, not my employers�
>
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
