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.




Network Security Secure-Shell
[Top] [All Lists]

Re: Password authentication fails: SSH secure shell to openssh server

Subject: Re: Password authentication fails: SSH secure shell to openssh server
Date: Wed, 03 Aug 2005 01:23:44 +1000
Andrew Muller wrote:
Problem: Can connect to OpenSSH server from openSSH client but not from SSH Secure Shell Client

I am running OpenSSH_3.8.1p1_FreeBSD_20040419 on my desktop (pc-mullera). I rely on passwords because I've never been able to figure out how to do the other authentication methods. I can ssh to the desktop from my laptop under cygwin (openSSH_4.1p1) but not from the laptop Secure Shell Client under XP (SSH Secure Schell 3.0.0) nor from a linux machine running SSH Secure Shell 3.1.2 under mandrake 9. When I fail to connect I get shut out with "no further authentication methods available" before I have even been asked for my password. I suspect an incompatibility between openSSH's keyboard-interactive method and Secure SSHs password method.

It's not an incompatibility, it's just that your client either does not support keyboard-interactive or has its support disabled and the server does not have SSH password authentication enabled.


On an OpenSSH client, this is controlled by the "PreferredAuthentications" setting. Check the documentation for your client for an equivalent and enable it if it has it. This is the preferred solution.

Alternatively, you could also set "PasswordAuthentication yes" in the server's sshd_config. On a vanilla OpenSSH 3.8.1p1 this will prevent PAM from being used for the authentication, I'm not sure if this is the case for the FreeBSD version.

--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

<Prev in Thread] Current Thread [Next in Thread>