Alternative port for CVS access

We are currently anticipating some restructuring in our mall server farm. We'll look into this after that is done.

i'm sitting here at a client site, blocked as bummed. bump.

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?

@kbahey - i thnk most people want write access too. start a different issue for the read only svn (which advantagelabs nicely provides aalready, BTW)

Got a link to that advantage labs thing? Didn't know about it.

http://svn.advantagelabs.com/documents/show/1

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!

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

I'd also like to file a request for an alternate port, same reasons (firewall blockage).

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=443
greg@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.

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 443
Trying 140.211.166.54...
telnet: Unable to connect to remote host: Connection refused

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

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?

Let's see what the OSUOSL replies to http://drupal.org/node/199412.

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.

Is there any progress on this issue? I too would like access via port 443.

same here. subscribing.

Any news on this? My trying to work, but this network blocks 2401 (or what ever the default is). Requesting pserver access for port 443.

I already tried and it doesn't work =(

Hi,

I have the same problem, which is annoying for a maintainer. As it's simply a question to match ports, I use Tor, a router that allows privacy and security for people in the world.

So now I use command line as these one (with Linux):

torify cvs -d:pserver:myLogin@cvs.drupal.org:/cvs/drupal-contrib login

That works fine for me. I hope the same for you.

Regards,

Daniel Berthereau

I'm less and less enthusiastic about this "solution". Whatever port we choose could be blocked and the "real solution" is to use ssh port forwarding or something like Tor. We can't use 443, so we can jettison that idea right now. We already use that port.

Running a r/o SVN wouldn't be a bad idea to get around this.

subscribing. just got the new office job and everything is blocked. i can't even generate patches.

@drewish: can you rsync? ;) You can always rsync the d.o CVS repo locally and then generate patches against that. I find that's actually vastly easier for dealing with core, anyway, since you can trivially generate patches that add/remove files that way. ;)

I am still trying to figure out who'd hire a developer and block the CVS port, but we'll work on providing an alternative port.

@drewish Good timing actually, we are just rebuilding cvs.drupal.org.

Any word on what ports arn't blocked?

oh i wish i could rsync... for some inexplicable reason dns lookups don't seem to work form the command line. the nbc network admins are a cruel bunch.

DNS resolves don't work from the command line? Thats just broken :)

From Rome, I'm getting blocked on port 2401 as well. I am connected via an SSH tunnel to a server back in the states, but I don't know if I'm able to route the CVS traffic through that tunnel to work locally on my Mac... would be nice to have port 443 or 8080.

We can't use 443 or 8080 since we already use them. We can only make up our own port.

I just added a new port, 3401.

-N

Sweet! Thanks for doing that... is this in the docs or handbook anywhere? If not, we should probably stick it in there.

I don't know that it's documented anywhere yet, please find a good spot and go for it.

When you do, be sure to document that the most recent versions of CVS use the CVS_CLIENT_PORT environment variable, not CVS_PSERVER_PORT as mentioned in the comments above.

Also, you can set the port directly in your CVSROOT, e.g:

CVSROOT=:pserver:anonymous:anonymous@cvs.drupal.org:3401/cvs/drupal-contrib

In case anyone else is looking for help on CVS connections, and can't get ports 2401 or 3401 to work, I just found this little tutorial on tunneling CVS through SSH: http://www.darrenmothersele.com/drupal-blog/access-drupal-cvs-behind-fir...