Solaris

Yes..It is availalbe in .ssh folder on my server A(i.e server from which I am trying to connect to server B)

Code:

bash-3.00$ pwd
/export/home/.ssh
bash-3.00$ ls -ltr authorized_keys
-rw-------   1 usr1 usr       402 Dec 18 13:54 authorized_keys
bash-3.00$

change the permission to 644. for the authorized_keys file

Do a checksum on the :
- authorized_keys file @ destination
- public key @ Source

Hi,

Many thanks for your feedback.

I have changed the permissions.

cksum is also giving the same output on both servers for public key and authorized_keys file respecitively.

But problem still persists

sometimes SSH version problem might make a different.
if you want to continue to troubleshoot.

- you can try to copy the public key to different user in the same machine or another linux machine
- make sure the user is not locked (sometimes when you setting up passwordless, it will get locked due to multiple failure attempt)
- Try to use DSA key
- increase the key size from 1024 to 2048

hope these can help

Don't. Relaxing the original permissions would just add a new reason for ssh/sftp to fail.

Thanks jlliagre for highlighting, I have mixed up with the public key permission, however, I have just tested with the permission for 644 and 600 on the authorized_keys, both are working.

Indeed. That might depend though on the sshd version and its settings.

@sai_2507 Is a password set to the sftpuser account on the remote server ?