From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: dhruva Newsgroups: gmane.emacs.devel Subject: Re: What a modern collaboration toolkit looks like Date: Sat, 5 Jan 2008 20:34:22 +0530 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1199545472 1624 80.91.229.12 (5 Jan 2008 15:04:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 5 Jan 2008 15:04:32 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Eli Zaretskii" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 05 16:04:53 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JBAZw-0003Wu-Up for ged-emacs-devel@m.gmane.org; Sat, 05 Jan 2008 16:04:53 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBAZa-0001rV-Gj for ged-emacs-devel@m.gmane.org; Sat, 05 Jan 2008 10:04:30 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBAZW-0001np-RK for emacs-devel@gnu.org; Sat, 05 Jan 2008 10:04:26 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBAZV-0001jX-67 for emacs-devel@gnu.org; Sat, 05 Jan 2008 10:04:26 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBAZV-0001jN-31 for emacs-devel@gnu.org; Sat, 05 Jan 2008 10:04:25 -0500 Original-Received: from wa-out-1112.google.com ([209.85.146.183]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBAZU-0002IZ-Fy for emacs-devel@gnu.org; Sat, 05 Jan 2008 10:04:24 -0500 Original-Received: by wa-out-1112.google.com with SMTP id k34so11086560wah.10 for ; Sat, 05 Jan 2008 07:04:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=DyC76eIIWmtkSg2QP14JfKrEaKs5OZQ2TnSxW7TykDA=; b=fYvATXnZNeFRk3J3SEdmRGuaXcgYCBNXqBj5DNoXrhRBwH5GviGwJ6wb1JhT6PX+kSG8bKkB/eo6L7vKqgCI4B1eCWZfFD6rdFB79LYnDKFzXJ8SVAh4K+U65tkew4vidOxJ8Wx9deOndFqvK/tkUsM8CQw8V0oex1sa+CAZD4I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NjU8OanYb+2kr+3wBHVdnMzXz75K5b9PSKU5StmKVXUj6eACdGB9irUC4olfFGe1PTlBi/zk8j8D+qAxA8VCgGpwjojsL3rXRV+C+Edk7BS5You8Hsq0EJIyQDAB9D3eRWGn/myUDqzHqHNBwzjRE1JZa0X3ym4qqlArBS1ki9Q= Original-Received: by 10.114.52.1 with SMTP id z1mr3327289waz.123.1199545463090; Sat, 05 Jan 2008 07:04:23 -0800 (PST) Original-Received: by 10.115.73.12 with HTTP; Sat, 5 Jan 2008 07:04:22 -0800 (PST) In-Reply-To: Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:86170 Archived-At: Hello, On Jan 5, 2008 7:06 PM, Eli Zaretskii wrote: > > Date: Fri, 4 Jan 2008 15:16:28 +0530 > > From: dhruva > > > > Though a trivial issue that many of you might not be affected (but I > > am). Ability to access CVS from corporate firewalls. I did try to > > inquire why system administrators block the port 2401. > > CVS over SSH does not use 2401, it uses SSH port 22. Does your > firewall block that as well? That is one of among the first they block as port 22 and SSH gives a shell access to a remote machine. > > normal (HTTP/HTTPS) ports that are normally open in most corporate > > firewalls. > > I once had similar problems, and the gnu.org maintainers set up CVS > access through such ports; perhaps it's still there. It all ceased to Savannah has a SSH running on 443 which I can use as I have commit access but this will not work for the general public. There is no anonymous access. > be a problem for me when Subversion started using SSH, and I found > that most firewalls don't block SSH ports. Most corporate firewalls do block SSH port for following reasons. 1. It gives you a shell access to a remote machine out of their network 2. Since it is encrypted connection with your private key, they cannot sniff out the contents! So far, I have worked for 5 different employers and all of them block port 22 and 2401 (and a bunch of other ports used by IRC, NNTP, Yahoo/Gtalk/MSN chat...). Due to this, I was unable to take part in some of the developer chatter on IRC. -dky -- Contents reflect my personal views only!