Thanks Chris and Kevin.
When I try my sftp command here is what I get. (Below I try it again with a -v to get more info.)
sftp st.concursolutions.com
Password Authentication
Password Authentication
Password Authentication
Received disconnect from 12.129.29.5: 11: Too many bad authentication attempts!
Disconnected from 12.129.29.5
Connection closed
I tried what Kevin said and got this. Does this mean it did or did not work?
ssh-keyscan st.concursolutions.com >> /home/ccuser/.ssh/known_hosts
# st.concursolutions.com:22 SSH-2.0-SSHD
# st.concursolutions.com:22 SSH-2.0-SSHD
# st.concursolutions.com:22 SSH-2.0-SSHD
I did the sftp command again with -v to get debug data. The userid I'm using is ccuser. In Navigator I see files id_rsa, id_rsa.pub, and known_hosts in directory /home/ccuser/.ssh.
Don't the lines below that I've marked with '<<<<<<<' indicate that the connection was made and the host key was found in my known_hosts file? Isn't that enough to make the connection?
sftp -v st.concursolutions.com
OpenSSH_6.9p1, OpenSSL 1.0.2k 26 Jan 2017
debug1: Reading configuration data /QOpenSys/QIBM/ProdData/SC1/OpenSSH/openssh-4.7p1/etc/ssh_config
debug1: Connecting to st.concursolutions.com [12.129.29.5] port 22.
debug1: Connection established.
debug1: identity file /home/ccuser/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ccuser/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ccuser/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ccuser/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ccuser/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ccuser/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ccuser/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory n
debug1: identity file /home/ccuser/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9
debug1: Remote protocol version 2.0, remote software version SSHD
debug1: no match: SSHD
debug1: Authenticating to st.concursolutions.com:22 as 'ccuser'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-sha1 none
debug1: kex: client->server aes128-ctr hmac-sha1 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<7680<8192) sent
debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: got SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: ssh-rsa SHA256:wbb2bQRmDJqQaLbuYKsnGdxQ40mIIedeXChRsAYC3ig <<<<<<<<<<<<<<<<
debug1: Host 'st.concursolutions.com' is known and matches the RSA host key. <<<<<<<<<<<<<<<<
debug1: Found key in /home/ccuser/.ssh/known_hosts:1 <<<<<<<<<<<<<<<<
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: password,publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/ccuser/.ssh/id_rsa
debug1: Authentications that can continue: password,publickey,keyboard-interactive
debug1: Trying private key: /home/ccuser/.ssh/id_dsa
debug1: Trying private key: /home/ccuser/.ssh/id_ecdsa
debug1: Trying private key: /home/ccuser/.ssh/id_ed25519
debug1: Next authentication method: keyboard-interactive
Password Authentication
debug1: read_passphrase: can't open /dev/tty: No such device or address
debug1: Authentications that can continue: password,publickey,keyboard-interactive
Password Authentication
debug1: read_passphrase: can't open /dev/tty: No such device or address
debug1: Authentications that can continue: password,publickey,keyboard-interactive
Password Authentication
debug1: read_passphrase: can't open /dev/tty: No such device or address
Received disconnect from 12.129.29.5: 11: Too many bad authentication attempts!
Disconnected from 12.129.29.5
------------------------------
message: 4
date: Tue, 8 May 2018 18:21:55 +0000
from: Christopher Bipes <chris.bipes@xxxxxxxxxxxxxxx>
subject: RE: Setting Up sFTP for a Second Vendor - Host key
That is normal. At that point, you can cancel. You now have the remote server key in your known_host file. Your regular sFTP should work from this point forward.
Try your SFTP with your key file to connect to them. If they are set up correctly, you should not be prompted for a password.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
Confidentiality Notice: This email from Qualicaps (including all attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, copying, or distribution is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit
http://www.symanteccloud.com
_________________________________________________________
midrange.com
