git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Llinux@horizon.com <linux@horizon.com>
Date
Dec 2, 2005, 19:31 UTC
Message-ID
<20051202193101.29853.qmail@science.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.

Next: Andreas Jochens
Message 1 of 4 in “Re: How can I specify a non-standard TCP port for a git+ssh connection?”
  1. linux@horizon.comDec 2, 2005
  2. Andreas JochensDec 3, 2005
  3. Junio C HamanoDec 3, 2005
  4. Andreas JochensDec 3, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.