| Summary: | connection closed by remote host | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | godfrey.anderson | ||||||
| Component: | ssh | Assignee: | OpenSSH Bugzilla mailing list <openssh-bugs> | ||||||
| Status: | CLOSED FIXED | ||||||||
| Severity: | normal | ||||||||
| Priority: | P2 | ||||||||
| Version: | -current | ||||||||
| Hardware: | SPARC | ||||||||
| OS: | Solaris | ||||||||
| Attachments: |
|
||||||||
|
Description
godfrey.anderson
2004-04-08 04:41:07 AEST
3.4p1 is quite old, and you reproduce with 3.8p1? Either way, the information most likely to to show what's going on is will be in the server-side debugging. Try: # /path/to/sshd -ddd -p 2222 then connect with $ ssh -p 2022 yourhost then attach (note: use "create new attachment", do not paste into the text fields) the output of sshd on your failing host. Created attachment 599 [details]
output of sshd in debug mode & sshd_config file
Here is the output from the sshd -ddd -p 2222 command.
Note, that I have disguised my IP addresses, as I should have done when I first
submitted the bug.
The content of my sshd_config file is also included.
Comment on attachment 599 [details] output of sshd in debug mode & sshd_config file >debug1: PAM establishing creds >setuid 231: Not owner OK, it looks like it's blowing up inside pam_setcred(). I'm pretty sure that's been fixed in 3.8p1, please try that (note that you'll need to put "UsePAM yes" and "PasswordAuthentication no" into your sshd_config). If that doesn't fix it, what modules do you have in your PAM sshd stack? Created attachment 601 [details]
Content of pam.conf file on problem server
Please find attached the content of the pam.conf file on the problem server.
It is identical to other pam.conf file on servers with the same version of
openssh.
The sshd_config config file is already setup to use PAM with the parameter
"PAMAuthenticationViaKbdInt" set to "yes", I am told is equivalent to
using "UsePAM yes".
Unfortunately the server is question is a Production server in
a sensitive environment, so installing a new version of openssh
is not an option open to me at this time.
PAMAuthenticationViaKbdInt isn't equivalent to UsePAM, but the difference probably isn't going to matter in this case. This is probably caused by the same thing as bug #789. The patches in that bug are quite simple, so you can probably apply those to 3.4p1 with minimal hassle (you will need both attachments #537 and #547). BTW I hope you have applied the buffer patch to your 3.4p1: http://www.openssh.com/txt/buffer.adv Closing this bug: it's an old OpenSSH version, a patch is available and the issue is believed fixed in 3.8.1p1. Please reopen if you can reproduce the problem on 3.8.1p1. |