I think the only choice you have left then is some kind of tunnel. If this is only for you that is, else you need to educate the other users on this method?
What I'd do, is if you can't SSH into your network, I'd wait until I was in the office, SSH to a machine outside your network from the server hosting the SVN repo. This would be no ordinary SSH command though. You would be creating a reverse tunnel.
E.g. If you are on the server hosting the SVN, ssh to you machine like so:
So, what this means is, that I want a SSH tunnel to my "Remote_host_ip". On that machine there will be a tunnel that listens on port 60000, which comes back into your corporate network and allow you to see port 80 of the SVN server.ssh -R 60000:_servers_internal_ip:80 you@Remote_host_ip
All you need to do on the remote host is:
That will connect to you to the SVN server, no problems.svn co http://127.0.0.1:60000/subversion/myrepo/trunk my_repo
Bear in mind that the connection is only valid for the time the tunnel stays up. You can then use any of the SSH modules on CPAN to do this automatically with SSH public/private keys etc.
You could also use the other server , svnserve with SSH.
A bit of a fudge, but if the firewall is totally out of your hands, you've no choice :(
HTH.
In reply to Re: svn without webdav
by ghenry
in thread svn without webdav
by garyaj
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |