# Re: How can I specify a non-standard TCP port for a git+ssh connection?

4 messages from 2005-12-02 to 2005-12-03. Participants: linux@horizon.com, Andreas Jochens, Junio C Hamano.
Thread: https://gitlist.dev/t/2732

## linux@horizon.com, 2005-12-02 19:31

Subject: Re: How can I specify a non-standard TCP port for a git+ssh connection?
Message-ID: <20051202193101.29853.qmail@science.horizon.com>
URL: https://gitlist.dev/e/20051202193101.29853.qmail%40science.horizon.com

```
Actually, you don't need any git support.  ssh allows you to set up
"virtual hosts" with any combination of options you like.

Host <virtual>
        HostName <physical>
	Port <nonstandard>
        User <whoever>
        IdentityFile    <custom>
        ForwardAgent    no

So typing "ssh <virtual>" will have the effect of
ssh <whoever>@<physical> -p <nonstandard> -i <custom> -a

Quite often, you let <virtual> == <physical>, so it's "custom settings
for talking to this host", but you can have multiple different virtual
names that all map to the same physical host.

But the point is that as long as you can pass a hostname through to ssh,
you can carry as many custom settings as you like with it.

```

## Andreas Jochens, 2005-12-03 08:06

Subject: Re: How can I specify a non-standard TCP port for a git+ssh connection?
Message-ID: <20051203080620.GA22032@andaco.de>
URL: https://gitlist.dev/e/20051203080620.GA22032%40andaco.de
In-Reply-To: <20051202193101.29853.qmail@science.horizon.com>

```
On 05-Dec-02 14:31, linux@horizon.com wrote:
> Actually, you don't need any git support.  ssh allows you to set up
> "virtual hosts" with any combination of options you like.

> So typing "ssh <virtual>" will have the effect of
> ssh <whoever>@<physical> -p <nonstandard> -i <custom> -a

This is a nice feature, of course. But I still have to edit a separate 
config file. In some cases (e.g. scripts using ad hoc port forwarding) it 
would be much easier if the non-standard port and maybe some other
options could be specified directly on the git command line or 
in .git/branches.

Regards
Andreas Jochens

```

## Junio C Hamano, 2005-12-03 19:09

Subject: Re: How can I specify a non-standard TCP port for a git+ssh connection?
Message-ID: <7vwtimxait.fsf@assigned-by-dhcp.cox.net>
URL: https://gitlist.dev/e/7vwtimxait.fsf%40assigned-by-dhcp.cox.net
In-Reply-To: <20051203080620.GA22032@andaco.de>

```
Andreas Jochens <aj@andaco.de> writes:

> This is a nice feature, of course. But I still have to edit a separate 
> config file. In some cases (e.g. scripts using ad hoc port forwarding) it 
> would be much easier if the non-standard port and maybe some other
> options could be specified directly on the git command line or 

Having something on the command line to make it easy to override
one-shot you might be able to talk me into, but not in a config
file for git; there is a standard place to hold ssh
configuration already.

```

## Andreas Jochens, 2005-12-03 21:43

Subject: Re: How can I specify a non-standard TCP port for a git+ssh connection?
Message-ID: <20051203214336.GA32003@andaco.de>
URL: https://gitlist.dev/e/20051203214336.GA32003%40andaco.de
In-Reply-To: <7vwtimxait.fsf@assigned-by-dhcp.cox.net>

```
On 05-Dec-03 11:09, Junio C Hamano wrote:
> Having something on the command line to make it easy to override
> one-shot you might be able to talk me into, but not in a config
> file for git; there is a standard place to hold ssh
> configuration already.

You are right, a duplication of ssh config file options in git 
config files should not be necessary.

A way to specify a non-standard port for ssh on the command line
would be sufficient. It is possible to specify non-standard
ports for the git, http and rsync protocols on the command line.
Why not for ssh?

Regards
Andreas Jochens

```