Alternative port for CVS access
catch - March 29, 2007 - 09:12
| Project: | Drupal.org infrastructure |
| Component: | CVS |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Port 2401, is blocked by the firewall at my workplace. There's almost no chance of them opening that port so I can access it, so I'm filing this feature request for an alternative port. The obvious one would be 443 (and 22, although 22 is also blocked for me), I understand this is used by openldap and sourceforge for the same reason in addition to the standard port.
I'm not a very prolific contributor, (partly for this reason) although I'm working on it, but I'm sure this would help a lot of people in restricted environments (whether at work or in internet cafés and hotspots) to contribute more.
#1
We are currently anticipating some restructuring in our mall server farm. We'll look into this after that is done.
#2
thanks!
#3
i'm sitting here at a client site, blocked as bummed. bump.
#4
I don't want to stir the pot, but if we were to use SVN, it runs fine over port 80 with the Apache DAV extension.
Maybe it is time to have a read only SVN repository that is synced once a day with Drupal's CVS?
#5
@kbahey - i thnk most people want write access too. start a different issue for the read only svn (which advantagelabs nicely provides aalready, BTW)
#6
Got a link to that advantage labs thing? Didn't know about it.
#7
http://svn.advantagelabs.com/documents/show/1
#8
I'd also like to request an alternative port as I have to jump thru' hoops at my workplace if I want access to non-standard ports!
443 would be the obvious choice as you don't find many firewalls blocking https!
#9
Sure, I'll set this up when CVS is moved (soon). It will have to be 443, as the ViewVC webapp will be running on port 80 on the same box.
-Eric
#10
I'd also like to file a request for an alternate port, same reasons (firewall blockage).
#11
Did this get implemented yet? I'm currently blocked as well.
I wasn't sure so I tried
greg@greg:/var/www/m/drupal6$ export CVS_PSERVER_PORT=443greg@greg:/var/www/m/drupal6$ cvs up
But that didn't help. I state the commands because I'm not sure whether the problem is with my commands or with the lack of the service.
#12
change "cvspserver" from "2401/tcp" to "443/tcp" in your /etc/services file. Then do the usual export CVSROOT etc. Contrary to what I said before I edited this post, it doesnt seem though that cvs.drupal.org is listening on 443 for connections
telnet cvs.drupal.org 443Trying 140.211.166.54...
telnet: Unable to connect to remote host: Connection refused
#13
I don't want to give you all a tutorial about how to break out of corporate LANs :), but don't expect changing the port to work for most people. Many networks either use a (transparent) HTTP proxy, and/or a stateful packet inspector, both of which will notice your non-SSL traffic.
You might have better luck using CVS-proxy support
cvs -d:pserver;proxy=proxyhost;proxyport=8080:username@somedomain.tld:/somerepository
See http://cvsman.com/cvs-1.12.12/cvs_28.php
#14
Perhaps it is time that we move to an ssh tunnel based system. It's always surprised/scared me a little bit that commits happen based on a clear-text authentication. Anyone else?
#15
Let's see what the OSUOSL replies to http://drupal.org/node/199412.
#16
I can certainly setup pserver to listen on another port as well, however, the port chosen needs to be not used by another service. Just let me know the port that would be preferred.
However, this is likely an issue that can be solved on the client side as well. You would just need an SSH tunnel through a gateway host somewhere to forward the port for you.
#17
Is there any progress on this issue? I too would like access via port 443.
#18
same here. subscribing.