Page 1 of 1

Issues with passwordless / SSH key authentication

Posted: Fri Aug 24, 2012 9:15 pm
by eordona
I am having an issue setting up passwordless authentication / SSH key authentication. I have read all of the existing threads on this but they don't provide me with a concrete solution. Here is my log:

[01] Fri, 24 Aug 2012 16:53:17 (0000118) SSH session receive user name:myserver
[01] Fri, 24 Aug 2012 16:53:17 (0000118) SSH session receive password of user myserver
[02] Fri, 24 Aug 2012 16:53:17 (0000118) Closed session,disconnected from 10.10.10.113. The reason is:Public key authentication failed.

This particular log shows a connection attempt from another one my internal servers that I KNOW is capable (I have set up passwordless authentication from this server internally across between many of my Linux machines).

I have the password disabled in the account, and the SSH public key path in the account referencing the actual location of the key file in the filesystem.

My health care benefits provider is expecting this to work as we have to set up the automated data integration -- so I need a solution.

Help please!

Re: Issues with passwordless / SSH key authentication

Posted: Sat Aug 25, 2012 4:53 am
by FTP
Please have a look on this KB article: http://www.wftpserver.com/bbs/viewtopic.php?f=5&t=502" rel="nofollow

Re: Issues with passwordless / SSH key authentication

Posted: Mon Aug 27, 2012 8:02 pm
by eordona
Yes, I read that already, that isn't really helpful. As I stated before, I am able to use my existing keys across many different machines already in my environment.

Server side, I keep getting the message "The reason is:Public key authentication failed."

Client side (say, from linux command line), the message I get is:
Read from socket failed: Connection reset by peer
Couldn't read packet: Connection reset by peer


Any other suggestions (other than generate keys using puttygen)?

Re: Issues with passwordless / SSH key authentication

Posted: Mon Aug 27, 2012 8:59 pm
by eordona
I am making progress. I converted my existing public key from the linux client side server (the one trying to connect to WingFTP) from OpenSSH format to SSH2 format using the following command on the client side server:

ssh-keygen -e -f ~/.ssh/id_dsa.pub > ~/.ssh/id_dsa_ssh2.pub

I then moved id_dsa_ssh2.pub over to the WingFTP server (in ~/.ssh/ directory). My WingFTP server runs linux as well. I specified the new key within the user's profile (field "SSH public keypath (optional) field. I left the Enable password field unchecked.

From the remote server, I was able to connect. So, it seems, the key (no pun intended) is to have your public client key format in SSH2 format, not OpenSSH format!

Re: Issues with passwordless / SSH key authentication

Posted: Thu Aug 30, 2012 3:33 am
by FTP
It can be compatible with OpenSSH key in the next release.