Subject: bin/32120: Upgrading to netbsd-3 gives strange prompts for ssh
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org>
From: None <mjl@emsi.priv.at>
List: netbsd-bugs
Date: 11/19/2005 14:38:00
>Number: 32120
>Category: bin
>Synopsis: Upgrading to netbsd-3 gives strange prompts for ssh
>Confidential: no
>Severity: non-critical
>Priority: high
>Responsible: bin-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Nov 19 14:38:00 +0000 2005
>Originator: Martin J. Laubach
>Release: NetBSD 3.0_RC1
>Organization:
>Environment:
System: NetBSD asparagus.emsi.priv.at 3.0_RC1 NetBSD 3.0_RC1 (ASPARAGUS.l) #0: Thu Nov 17 22:54:18 UTC 2005 root@asparagus.emsi.priv.at:/sys30/arch/i386/compile/ASPARAGUS.l i386
Architecture: i386
Machine: i386
>Description:
After upgrading a 2.1 machine to the netbsd-3 branch, ssh started
to sprout strange behaviour at its password prompt:
| % ssh asparagus
| Password: <--- does not even wait for input here
| Response:
| mjl@asparagus's password:
This is somehow related to PAM, since setting "UsePAM no" in sshd.config
restores the previous normal behaviour.
I first thought this might be related to old S/Key data lying around
but Hauke Fath mentions:
| FWIW, I see this on a (pretty vanilla) sparc installation. S/Key has
| never been used on the machine.
I set priority high because this will seriously confuse people who
upgrade to 3.0.
>How-To-Repeat:
ssh into an upgraded machine?
>Fix: