Need to have pam correctly configured:
If you are using PAM, you may need to manually install a PAM control
file as /etc/pam.d/sshd (or wherever your system prefers to keep
them). Note that the service name used to start PAM is __progname,
which is the basename of the path of your sshd (e.g.,
-
| From: Jan Egeriis [mailto:[EMAIL PROTECTED]]
| Sent: Friday, August 10, 2001 9:13 AM
| To: Roy S. Rapoport; [EMAIL PROTECTED]
| Subject: Re: OpenSSH 2.5.2p2, Linux, and not accepting passwords
|
|
| charset=iso-8859-1
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority
Thanks to the myriad of people who pointed to PAM being the culprit here.
Thanks also to the people who pointed out this was in the archives (I'll
admit I was a little confused here because of my lack of clarity as to the
role of the two lists -- ssh@clinet and the secureshell lists). It's all
*Refreshing Sigh*
Another convert ;)
| -Original Message-
| From: Roy S. Rapoport [mailto:[EMAIL PROTECTED]]
| Sent: Monday, August 13, 2001 3:26 PM
| To: [EMAIL PROTECTED]
| Subject: RE: OpenSSH 2.5.2p2, Linux, and not accepting passwords
|
|
| Thanks to the myriad of people who
Roy S. Rapoport wrote:
Well this is bizarre.
Default install of openssh on this linux box (originally RedHat
but I think someone's put a new kernel on it -- it reports itself
as 2.2.12-20 when I do uname -a. Sorry, Solaris is my forte, not
Linux).
It all works.
Oh, except for
Same problem here...
Redhat 6.2 kernel 2.2.19
OpenSSH 2.9p2
Haven't found a solution yet. :-(
regards
Jan
- Original Message -
From: Roy S. Rapoport [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, August 10, 2001 9:56 AM
Subject: OpenSSH 2.5.2p2, Linux, and not accepting
Just a shot in the dark, but you probably compiled without pam support.
./configure --with-pam
Either that or you didn't copy the pam config file from the distribution
(under redhat in contrib) to /etc/pam.d/
--James
Jan Egeriis writes:
Same problem here...
Redhat 6.2 kernel 2.2.19
Looks like when you built it there were some issues
with getting the pam situation worked out.
look at the README or INSTALL docs in the tarfile after
you built the ssh package...
If you are using PAM, you may need to manually install a PAM control
file as /etc/pam.d/sshd (or wherever your