1
* Sometimes CVS server of Sourceforge have problems preventing anonymous access. In this cases
2
access can be occured truth non-default ports 80 and 443 of cvs-pserver.sourceforge.net
4
How can I access CVS services from behind a firewall? | doc feedback |
7
Access to the project CVS servers is provided via SSH (for developers)
8
and the CVS pserver protocols (for non-developers). SSH uses TCP port 22;
9
CVS pserver uses TCP port 2401. Many firewalls block outbound traffic on
10
these ports, thus preventing SourceForge.net developers and users from
11
accessing the project CVS servers. To work around this limitation, we now
12
offer the ability to connect to the project CVS servers using alternate
13
ports (using different hostnames).
15
To access the project CVS server using SSH from behind a firewall, you
16
may connect to port 443 or port 80 of cvs-ssh.sourceforge.net. Traffic to
17
port 443 and to port 80 of cvs-ssh.sourceforge.net is redirected to
18
cvs.sourceforge.net. The SSH host fingerprint for cvs-ssh.sourceforge.net
19
will match that of cvs.sourceforge.net.
21
To access the project CVS server using anonymous pserver-based access
22
from behind a firewall, you may connect to port 443 or port 80 of
23
cvs-pserver.sourceforge.net. Traffic to port 443 and to port 80 of
24
cvs-pserver.sourceforge.net is redirected to cvs.sourceforge.net.
26
The syntax for specifying an alternate port for pserver-based CVS is as
27
follows. GUI-based CVS clients typically offer a configuration setting for
30
cvs -d:pserver:anonymous@cvs-pserver.sourceforge.net:PORT/cvsroot/PROJECT
34
cvs -d:pserver:anonymous@cvs-pserver.sourceforge.net:443/cvsroot/PROJECTNAME
36
cvs -d:pserver:anonymous@cvs-pserver.sourceforge.net:80/cvsroot/PROJECTNAME