problem with publickey authentication

Hello,

I have a business client who is running a SSH Communications SSH Tectia Server on a Windows NT Server.

I need to connect to their server from dozens of FreeBSD servers in my organization using OpenSSH client, using publickey auth only.

During testing, after entering the passphrase for private key, I am being prompted for a password, which has never happened to me before when connecting openssh->openssh.

He claimed that he tested on his side, and was able to connect from a Linux client to his own Windows Tectia SSH box.

So I copied my private key to an old Linux box, and tried that -- it worked as he claimed.

Why does openssh client behave differently between Linux and FreeBSD?

Or is it an issue with the versions of OpenSSH, and something changed?

Is there an option I can pass on my FreeBSD box to get my OpenSSH client to work as it does on the Linux box?

FreeBSD Client (cannot connect to server):
FreeBSD 5.5-RELEASE-p8
OpenSSH_3.8.1p1 FreeBSD-20060930, OpenSSL 0.9.7e-p1 25 Oct 2004


Linux Client (can connect to server):
Red Hat Linux 7.2 2.96-118.7.2) Red Hat 2.4.9-e.27smp
OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f


Windows Server:
Remote protocol version 2.0, remote software version 3.2.9 SSH Secure Shell Windows NT Server


Command on both FreeBSD and Linux Clients (again, works on Linux, fails on FreeBSD):
# sftp -vvv -o IdentityFile=.ssh/testuserkey testuser@xxxxxxxxxxxxx

---------------------------------------------------------------------------------
Logging on Linux:

Enter passphrase for key '.ssh/testuserkey':
debug1: read PEM private key done: type RSA
debug3: sign_and_send_pubkey
debug2: we sent a publickey packet, wait for reply
debug1: ssh-userauth2 successful: method publickey

and then I'm in.

---------------------------------------------------------------------------------
Logging on FreeBSD (notice that I never get a reply from the server as I do when connecting from the Linux box. Why is this?):

Enter passphrase for key '.ssh/testuserkey':
debug1: read PEM private key done: type RSA
debug3: sign_and_send_pubkey
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue:
debug3: start over, passed a different list publickey,keyboard-interactive
debug3: preferred publickey,keyboard-interactive
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug2: we did not send a packet, disable method
debug3: authmethod_lookup keyboard-interactive
debug3: remaining preferred:
debug3: authmethod_is_enabled keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug1: Authentications that can continue:
debug3: userauth_kbdint: disable: no info_req_seen
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied ().


Thanks for any help with this that anybody can provide!

-DW

Relevant Pages

  • Re: Explanation of SSH
    ... I am still unclear on how SSH works exactly. ... Client issues SSH command and names server ... "Shopper" says "server sends back its public host and server keys ... Surely there is only one public key it sends ...
    (comp.security.ssh)
  • Re: ssh security question
    ... In my case - the client is a windows client and the ssh is embedded into the windows nx client. ... Is there any reason I can't run ssh-keygen on the server and copy the private key to the client - and the public key to the "authorised" directory? ... sniffer can catch your passwords, and it would make it trivial to log in ...
    (SSH)
  • Re: Publishing a SSH Server
    ... Your unix box cannot reply to SSH request, ... Create a client address set for your unix box (ip address from to are the ... Jim Harrison [ISA SE] ... In that case the server is a SecureNET client but still it doesn't work.... ...
    (microsoft.public.isa.publishing)
  • Re: FC6 VPN
    ... Then you can run any application you would like off the server by simply running it, or if you want to run a whole session, use gnomesession. ... ssh client that supports X forwarding, which is want you want to be looking at. ... SSH allows you to forward any local port to any remote port. ... If you need to connect to, say a windows share, you would forward your local port to the linux server through the ssh tunnel. ...
    (Fedora)
  • Re: Password less login between client & server, server & client
    ... password less logins on both the ssh client and ssh server. ... Login as the user that is making the connection. ...
    (comp.security.ssh)