Re: Upgrade from woody to sarge - ssh strangeness
Quoting Lionel Elie Mamane <lionel@mamane.lu>:
> On Tue, Jan 16, 2007 at 08:31:12AM +0100, Turbo Fredriksson wrote:
>> Quoting aaron@sysdev.oucs.ox.ac.uk:
>
>>> If memory serves, you need to edit /etc/ssh/sshd_config, uncomment
>>> the "PasswordAuthentication yes" line, and reload ssh.
>
>> With that, I only get:
>
>> Jan 16 08:28:01 pumba sshd[24998]: Failed password for turbo from <windows_machine_behind_linux_NAT_firewall> port 1956 ssh2
>> Jan 16 08:28:13 pumba sshd[25003]: error: Could not get shadow information for turbo
>> Jan 16 08:28:13 pumba sshd[25003]: Failed password for turbo from <windows_machine_behind_linux_NAT_firewall> port 1957 ssh2
>
> Can you login as "turbo" locally on pumba? It seems SSH doesn't find
> the password for turbo. I'd say either /etc/shadow is "strange" or PAM
> is misconfigured for SSH (/etc/pam.d/ssh).
Yes. And with a linux (Ubuntu Dapper) next to the windows machine...
All services work like a charm, just not from an old SecureCRT
client on windows...
So PAM is configured and working fine... I think the problem is that
sshd require 'keyboard-interactive' which the old client can't handle.
The new one works like a charm though. Unfortunatly it's so much
ugglier :). That's why I never upgraded that earlier. Now I don't
have a choice...
Reply to: