| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <200501250513.j0P5Da4H031277@turing-police.cc.vt.edu> From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu) Subject: blocking SkyPE? On Tue, 25 Jan 2005 10:05:23 +0700, Alain Fauconnet said: > I would certainly not call our users a legion of techies (sometimes I wish > they'd be more techies than they are). Setting up a VPN would require > having control of a box outside of our campus, which is not likely for > the vast majority of them. Even if some can still get through, > blocking 80+% of the current SkyPE users is good enough for me. For those of you playing along at home, the actual requirement to set up a VPN is merely that they know somebody who has control of a box outside the campus (or even know where to find a tunnel broker). And Alain is probably quite correct that even that lower standard will stop 80% and be sufficient for his needs. But you need to remember the difference, in case you need *better* than 80%, and your users are either more clued or they know more clued people..... How to give the firewall admin indigestion: Do your dirty work via IPv6, and use a V6-over-V4 tunnel broker to get out to your remote site... :) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 226 bytes Desc: not available Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20050125/a9e2b8ff/attachment.bin
Powered by blists - more mailing lists