I recently wrote an article about SSH/SCP/SFTP. If you're interested in that, it's located here (requires a Pro membership with System iNetwork):


In my experience, you don't need to get the server's key -- that'll be done by SSH automatically. But you do need to generate your own private/public keys, and install the public key (or have them install it) on the server.

But a lot of it also depends on how the server is configured. Is it configured to allow password logons? Is it configured to allow interactive logons?

If the folks running the server know less about SFTP than you do, how the heck did they set this up?

Steve McKay wrote:
Once again, we're attempting to use SFTP (yes, the one in SSH) to connect to a business partner's server. I've done the ssh-keyscan and have gotten their public key (I think) and have done ssh-keygen and created my private/public keys (I think). Do they have to install my public key on their server?

When I 'call qp2term' and enter 'sftp myuserid@xxxxxxxxxxxxxxx', I get the following response:

Connecting to ftp.theirserver.com...
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,gssapi-with-mic,password).
Connection closed

I presume that I'm connected but don't have access to something on their end. Are the 3 'permission denied' messages a result of a 'retry' or do I not have access to 3 things or what?

The business partner knows less about SFTP than I do (if that's possible), so they're no help.



This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].