[Bug 648] Cannot login using SecureCRT since openssh 3.7p1

[bugzilla-daemon at mindrot.org]

http://bugzilla.mindrot.org/show_bug.cgi?id=648





------- Additional Comments From simon at igrin.co.nz  2003-09-18 11:12 -------
>I'm not seeing how --with-md5-password implies broken --with-pam.  Pam is now 
>a run-time option.  Therefor if you do 'UsePam no'  it will failback to trying 
>to handle the /etc/shadow password directly.

Not sure I understand your comment, or that it even makes sense. For me, PAM 
authentication no longer works when it worked fine under 3.4p1. Thats why I 
refer to it as broken. (Please see my attached debug output)

UsePam no in sshd_config did not help either.

>  If you use md5.. you need to 
>tell OpenSSH about it.

Well we use PAM, its only because PAM support isn't working that I resorted to 
trying MD5 support. How exactly is one supposed to enable MD5 support when 
building RPM's ? The supplied openssh.spec file doesn't provide a way to do it 
without hacking the SPEC as I did.

At the end of the day, the PAM support is still broken in 3.7.1p1 on my 
systems...(I've had a couple of emails from people saying they're also having 
the same problem)



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.