++added: Ultimate block All those methods are based on a single feature: when https access is allowed, there's no way to analyse the (encrypted) traffic. In particular, URL-based filtering doesn't work with https. So you can do whatever you want on remote port 443.
However, I've already seen networks where https was simply disallowed, probably for that reason. Only port 80 was available and thus the only choice available to you was: talk the network administrator into allowing outgoing CVS access. So don't believe those tricks can work in the long term. Some admins are already blocking Tor nodes, disabling port 443 is just the next step. The only real work around is talking with your system administrator. -- forwarded from https://savannah.gnu.org/maintenance/[EMAIL PROTECTED]://savannah.gnu.org/maintenance _______________________________________________ Savannah-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/savannah-cvs
