Re: 5.20.2 beta works great but...
@Guest: That's quite difficult to interpret/parse. Btw, why aren't you using
ProxyJump
?
ProxyJump
?
ProxyCommand
as tunneling configurations as well.
Host Aliyun-Windows
HostName 47.94.59.xxx
User Administrator
PasswordAuthentication no
Host GXKJ-a100
HostName 12.2.20.xxx
User kdyhn_gxkj
ProxyCommand ssh -W %h:%p Aliyun-Windows
~
: I have fixed this:
%HOMEPATH%
that breaks it. And as it's not allowed in OpenSSH config
file anyway, no point "fixing" it. With the original ~
and the above fix, it should work now too.
.ssh/config
, which would be great for me, since I have lots of keys and connections configured there.
~\.ssh\keyfilename
, WinSCP could not read a keyfile, I changed it to %HOMEPATH%\.ssh\keyfilename
in one connection, keyfile could be read.
windows user path\.ssh\keyfilename
(I wonder if this would have been the case if I installed just for the current user and not for all users?).
ssh
config
file would be a very fundamental and important feature for any serious user, developers, and testers.
ssh
config
file. I would not want to be be able to edit my ssh
config
from the WinSCP application to avoid unanticipated corruption.
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
, and convenient names set up for each. So, I pretty much live by this file, because it's a standard way to specify SSH connections.
~/.ssh/config
(or the path specified by a system variable?).
ssh
config
file support.
web-worker-*
and then use just a hostname ;)
.ssh/config
as a source of easily accessible configurations, more like current import functionality.
ssh
config
file, ~/.ssh/config
by default
config
entries, with wildcard support
HostName
, Port
, User
, IdentityFile
, ServerAliveInterval
+ ServerAliveCountMax
, ProxyJump
config
?
config
file is not a site manager (while some use like this). It's a pattern matching configuration file.
config
?
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 would do ;)
...
Host ansible srv-ansible
User ebt
HostName 172.16.238.120
...