On Jul 20, 2004, at 3:48 PM, Spiro Trikaliotis wrote:
Unfortunately, depending on whether I'm "inside" the network which containsI've handled this in the past by simply using a standard ssh client to connect to the appropriate server and port, and forwarding port 22 on localhost. So suppose that while on the internal network I connect to hosta, port 111 and while outside the firewall I connect to hostb, port 222. All I do then is:
the repository, or "outside", I have to use different ssh settings. The
machine name, as well as the used port change. I cannot access the
repository server with the "inside" settings from outside, and vice
versa.
Currently, I help myself by utilizing a ~/.ssh/config file, which
contains two entries, namely, CVS-local and CVS-remote, with the correct
settings for each case. Depending of whether I'm "in" or "out", I rename
one of both to "CVS", and only use the ssh server name "CVS" when
working with CVS.
This works, but is annoying. I ask myself if there is another way to perform this? I will ask this on an ssh mailing list, too, but there might be some ideas here which do not depend on ssh, but are cvs related.
Internal: ssh -L:22:hosta:111 -p 111 [EMAIL PROTECTED] cvs -d:ext:[EMAIL PROTECTED]:/path/to/cvsroot co module
External: ssh -L:22:hostb:222 -p 222 [EMAIL PROTECTED] cvs -d:ext:[EMAIL PROTECTED]:/path/to/cvsroot co module
The details of the port forwarding vary, of course, depending on your network. For example, on some networks, you may always be forwarding to the "internal" port (so it'd be -L:22:hosta:111 in both cases with just the part from -p onward changing)...
Note that the cvs commands never change, just the ssh connection that I open on another console.
HTH,
Geoff
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
