|
Hello,
Am 07.06.2023 um 15:32 schrieb gio.cot via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:
I have taken a step forward . running " ssh myuser@xxxxxxxxxxxxxxxx ", i was able to create the file known_hosts with the information relative to sftp.SFTPSRV.COM; after that if i try to run "sftp myuser@xxxxxxxxxxxxxxxx " i receive :This can happen for different reasons:
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
Connection closed
Any suggestion for this messages ?
- Remote server does not offer password authentication (anymore),
- Local rights for ssh key authentication are too permissive, so ssh clients (such as sftp, or scp) choose to ignore the key.
The latter can be found out in client debug mode and observing the output for permission-related messages.
>From your previous problems with a changed host key I assume that the remote server has changed somehow. Please check with your supplier to rule out that something nasty is happening and you're connecting in fact to the desired remote server. They should be able to tell if they made changes to their server infrastructure and if password authentication is still allowed.
To enable key authentication, you'd need to check with them, anyways. You will need to create a local keypair (private and public key) and send them the text string from the public key. This topic has been discussed numerous times in this list, so please search the archives.
:wq! PoC
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.