support .ssh/config

Advertisement

bunam
Joined:
Posts:
2

support .ssh/config

Hello,

As i suppose we use more git for windows or other tooling Ubuntu from the market, it could be cool to have a folder "ssh config" that will be automatically populated by the content of the file. Direct editing should be nice but later ?

Also if i have a host named 'srv-ansible' the URL like sftp://srv-ansible/ should go to the right server, with the good user name, using the good id file, like openssh should do ;)

.ssh/config
...
Host ansible srv-ansible
 User ebt
 HostName  172.16.238.120
...

Thank you for having taken the time to read.

Reply with quote E-mail

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
34,137
Location:
Prague, Czechia

Re: support .ssh/config

Thanks for your suggestion.
We will see, if more people ask for this.

Reply with quote

abareptia
Guest

Re: support .ssh/config

I will be good have something like this setup. As we also use git and like to use config file to manage host.

Reply with quote

jpjodoin
Guest

That would be very useful for me also. My openssh config file describe all the servers I need to access on a regular basic (including jumpbox), so it would be awesome if I didn't have to worry about keeping this information in sync with my WinSCP configuration when I need to fetch/upload a file on a machine.

Reply with quote

Advertisement

shawnz
Donor
Joined:
Posts:
5

I think it would be helpful if it were supported as an import source in the "Import sites" dialog box. Of course not all OpenSSH options could be supported, but at least the HostName, Port and User settings could be processed and imported.

However this would still involve a syncing process so maybe it doesn't meet the other poster's needs. But it would be fine for me.

Reply with quote

martin
Site Admin
martin avatar

As above: How exactly do you imagine WinSCP should work with the OpenSSH config?

The config file is not a site manager (while some use like this). It's a pattern matching configuration file.

Reply with quote

shawnz
Donor

I think it would be fine to just ignore any sections that use wildcards. Or maybe options in wildcard sections could affect all imported hosts which match, and ignored otherwise.

Reply with quote

Advertisement

ppr
Joined:
Posts:
2
Location:
Poland

Parsing of wildcards would be also helpful. For me it would be ideal if it would work like this:

  • global configuration - location of ssh config file, ~/.ssh/config by default
  • option to use it as defaults when some value is not explicitly configured in WinSCP
  • matching of entered hostname to `config` entries, with wildcard support
  • support for things that WinSCP can easily work with, i.e. HostName, Port, User, IdentityFile, ServerAliveInterval+ServerAliveCountMax, ProxyJump

Reply with quote

martin
Site Admin
martin avatar

ppr wrote:

Parsing of wildcards would be also helpful. For me it would be ideal if it would work like this:...
That's what I feared. In the end, people will ask for a full support :)

Reply with quote

ppr
Joined:
Posts:
2
Location:
Poland

Well, who in their right mind configures a dozen of identical servers by hand when they can just write "web-worker-*" and then use just a hostname ;)

But what I wrote is more like a layer of defaults, while the OP wanted to treat .ssh/config as a source of easily accessible configurations, more like current import functionality.

Reply with quote

Advertisement

Advertisement

You can post new topics in this forum