openssh unix dev - Mar 2002 - [Bug 159] Password-Authentication with openssh-3.1p1 fails

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





------- Additional Comments From jason at rndpkt.org  2002-03-13 12:38 -------
Can you please publish your /etc/pam.d/sshd file here?  It sounds like the pam
stack is either not finding the sshd file or else there's an error within
the file.



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

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





------- Additional Comments From jason at rndpkt.org  2002-03-13 12:41 -------
Oops... didn't see it your earlier post.  Please try the following for your
/etc/pam.d/sshd and see if it resolves the problem:

#%PAM-1.0
auth       required     /lib/security/pam_stack.so service=system-auth
auth       required     /lib/security/pam_nologin.so
account    required     /lib/security/pam_stack.so service=system-auth
password   required     /lib/security/pam_stack.so service=system-auth
session    required     /lib/security/pam_stack.so service=system-auth
session    required     /lib/security/pam_limits.so
session    optional     /lib/security/pam_console.so



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

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





------- Additional Comments From fam.muck at telda.net  2002-03-13 19:38 -------
Well, it seems I'm out of luck. pam_stack.so is not included in my pam-
distribution (SuSE Linux) and I'm not able to find the source in the net
except
in RedHat-Distributions. But I don't want to rotate my pam-system with pam
from
another Linux-distribution -  maybe after such an "update" openssh
works, but
many other applications do not so :-) SuSE and RedHat pam-stacks differ in many 
points.

But why do you mean, pam could not find the sshd binary? The identical stack 
worked fine with my previous openssh-version and I didn't change any file-
locations. sshd resides in /usr/sbin/ before and after the update. And the logs 
seem to say that communication between sshd and pam works as it should. 
pam_unix2.so recognizes a wrong password but (of course) you can be sure I use 
the correct password! I'm not a professional but I would think sshd passes a
wrong password to pam (or why should pam detect a wrong password when I type 
the correct one?).

Very strange things seem to happen.
Andreas



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

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

fam.muck at telda.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From fam.muck at telda.net  2002-03-15 06:23 -------
Hallo out there,

seems that the reported phenomenon is not related to openssh. I changed the 
first line from my auth-stack in /etc/pam.d/sshd from

auth     required       /lib/security/pam_unix.so
    to
auth     required       /lib/security/pam_unix_auth.so

and all works. That's why I mean we have to look for the bug in pam_unix.so.
I
wrote a bug report to the maintainer of pam_unix.so.

Thanks for your effort I go on and close the bug on this site.

Ciao
Andreas



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