sftp - SSH Server confirms Client? -
my company uses commercial (tibco mft) software system handle file transfers, , encountered instance unable connect specific clients sftp server. connect day when going linux terminal on same local server, when trying use software failed authenticate. using simple user/password set connect them. fixed (in software control panel) selecting "use default key"(which way our key)in ssh options, selection had been "none". mind, should have been required use some sort of key, brought attention have lot of sftp push file transfers use server configurations ssh key marked "none". have looked around , not found satisfactory answer. have suspicions though:
- does remote server have file containing keys remote systems (sort of known_hosts?), , if client system not in file, won't let me log in?
- does have "double key exchange" used in ssh2? if customer server using ssh1 not require server key?
i appreciate insight in this.
ssh can setup accept both keys , username/password. target system can support both.
you not have "known_hosts" file verify (with keys) host connect from. verify host you connect to. common limit access host using ip restrictions either via firewall or ssh configuration.
but still might access account on host using keys.
if target system sort of unix have account name accessing it. user account have home directory on server. in account home directory have folder named ".ssh" within folder have file named "authorized_keys". can in file list number of public keys accessing account. if have proper private/public key pair able access account.
so answer specific questions: - no. such restrictions ip based. - no. server key used verify server connect to.
first key exchange verify host connect to. being asked first time connect host. when accept have encrypted session. if allowed enter username/password after this. if host setup use key based authentication must supply keys.
both ssh client , ssh server should provide logs many hints happens.
many unix servers use openssh , can see configuration file at: /etc/ssh/sshd_config
if try connect ssh server requires key based authentication , not accept username/password typically error: "no supported authentication methods avaiable (server sent: public key)".
when using commercial solution suspect ssh stack might old , outdated , not using modern cipher suites. can see ciphers used on linux server searching "ciphers" in "/etc/ssh/sshd_config"
for further troubleshooting recommend connect directly using putty source system. can ferrit out if tibco mft uses outdated stack , needs updating.
you can putty at: http://www.chiark.greenend.org.uk/~sgtatham/putty/
to further need connection logs , configuration files. should have connection error tells wrong.
Comments
Post a Comment