views:

89

answers:

1

I am trying to setup an SSH tunnel to access Beanstalk (to bypass an annoying proxy server).

I can get this to work, but with one caveat: I have to map my Beanstalk host URL (username.svn.beanstalkapp.com) in my hosts file to 127.0.0.1 (and use the ip in place of the domain when setting up the tunnel).

The reason (I think) is that I am creating the tunnel using the local SSH instance (on Snow Leopard) and if I use localhost or 127.0.0.1 when talking to Beanstalk, it rejects the authorisation credentials. I believe this is because Beanstalk use the hostname specified in a request to determine which account the username / password combination should be checked against. If localhost is used, I think this information is missing (in some manner which Beanstalk requires) from the requests.

At the moment I dig the IP for username.svn.beanstalkapp.com, map username.svn.beanstalkapp.com to 127.0.0.1 in my hosts file, then for the tunnel I use the command:

ssh -L 8080:ip:443 -p 22 -l tom -N 127.0.0.1

I can tell Subversion that the repo. is located at:

https://username.svn.beanstalkapp.com:8080/repo-name

This uses my tunnel and the username and password are accepted.

So, my question is if there is an option when setting up the SSH tunnel which would mean I wouldn't have to use my hosts file workaround?

A: 

I would add an entry to your hosts file that maps 127.0.0.1 to the hostname you need and then use the hostname to connect to your tunnel.

Update The hosts file is IMO your best option.

John Weldon
I'm on Snow Leopard (Mac OS 10.6.3).I'm already do this at the moment to make it function, but I was hoping to see if anybody new of a way to specify the hostname as a parameter to SSH to avoid having to map the domain to 127.0.0.1 in the hosts file.
Tom