Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Putty to Windows sshd server authentication problem |
|---|---|
| Date: | Wed, 2 Feb 2005 09:15:40 -0500 |
I am having difficulty with public key authentication between a Putty client on one host and a SSH-Textia Windows server on another host. Public key authentication fails, but Password authentication always works. I suspect the problem is that my userid on the host that the Putty client is running is a member of one domain and the userid on the Remote Windows client is a member of a different domain. I generated both RSA and DSA keys using "puttygen" and ftp'd in Ascii first and then Binary to %D/.ssh2 on the Windows host. I then added the keys to the "authorization" file with the format "Key publickeyname". I was able to public key authenticate fine when the Windows SSH-Textia server was on the same host with the Putty client using this same scenario. Should I be able to connect with the same userid on multiple domains and public key authenticate from a Putty client on one host to a Windows SSH-Textia server on another host? The following message from the server log says it all, however I am unclear on how to solve it? 1488:Ssh2AuthPubKeyServer: Received public key (type ssh-dss) not authorized by authorization file. Below is a sample log from the server side. 1488:SshWinuser: ssh_user_free() done 1488:SshWinuser: ssh_user_free() 1488:SshWinuser: ssh_user_free() done 1488:Sshd2: allowed authentications: publickey,password 1488:Ssh2AuthCommonServer: User alclin is allowed to login because username matched with allow list. 1488:Ssh2AuthPubKeyServer: Received public key (type ssh-dss) not authorized by authorization file. 1488:Ssh2AuthCommonServer: User alclin is allowed to login because username matched with allow list. 1488:Ssh2AuthPubKeyServer: Received public key (type ssh-dss) not authorized by authorization file. 1488:Ssh2AuthCommonServer: User alclin is allowed to login because username matched with allow list. 1488:Ssh2AuthPubKeyServer: Received public key (type ssh-rsa) not authorized by authorization file. 1488:Ssh2AuthCommonServer: User alclin is allowed to login because username matched with allow list. 1488:SshWinuser: LogonUser alclin,(null) 1488:SshWinuser: LogonUser() OK 1488:SshWinuser: is 'alclin' admin = 0 1488:EVENTLOG(info): User alclin's local password accepted. 1488:EVENTLOG(info): Password authentication for user alclin accepted. 1488:Sshd2: user 'alclin' service 'ssh-connection' client_ip 'xx.xx.xx.xx' client_port 'xxxx' completed 'password 1488:Sshd2: Using old-style authentication policy configuration. 1488:SshProtoAuthServer: no_more_needed=TRUE 1488:Ssh2Common: Received SSH_CROSS_STARTUP packet from connection protocol. 1488:Ssh2Common: Received SSH_CROSS_ALGORITHMS packet from connection protocol. 1488:Ssh2Common: Received SSH_CROSS_AUTHENTICATED packet from connection protocol.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | OpenSSH and Enhanced Security, Narendra Raavi |
|---|---|
| Next by Date: | Re: OpenSSH shell access failure, Bauer, Henry |
| Previous by Thread: | OpenSSH and Enhanced Security, Narendra Raavi |
| Next by Thread: | Problem compiling openssh 3.9p1 on HP-UX 10.20, peter . kielbasiewicz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |