@manivela: I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.
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
~/.ssh/config(or the path specified by a system variable?).
.ssh/configas a source of easily accessible configurations, more like current import functionality.
configfile is not a site manager (while some use like this). It's a pattern matching configuration file.
srv-ansiblethe URL like
sftp://srv-ansible/should go to the right server, with the good user name, using the good id file, like OpenSSH would do ;)
Host ansible srv-ansible