Bug 1136 - User not logged off after forced password change in AIX 5.3
Summary: User not logged off after forced password change in AIX 5.3
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: 4.1p1
Hardware: PPC AIX
: P2 normal
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-20 02:34 AEDT by Steve Bassler
Modified: 2006-10-07 11:43 AEST (History)
0 users

See Also:


Attachments
sshd debug output (38.77 KB, text/plain)
2005-12-20 02:41 AEDT, Steve Bassler
no flags Details
sshd_config (2.77 KB, text/plain)
2005-12-20 02:45 AEDT, Steve Bassler
no flags Details
ssh_config (1.25 KB, text/plain)
2005-12-20 02:46 AEDT, Steve Bassler
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Bassler 2005-12-20 02:34:35 AEDT
When logging into an account where a password change is required, the user is prompted for the password change but is not logged off afterward.  The password is changed correctly.  The following message apprears in the syslog after the new password is entered for the second time, and then again a few seconds later:
auth|security:err|error sshd[23438]: error: getsockname failed: A file descriptor does not refer to an open file.

This happens any time root changes the user's password (i.e. the ADMCHG flag is set).  I do not know if it happens when the password expires.

Environment:
AIX 5.3.03
OpenSSH_4.1p1, OpenSSL 0.9.7g 11 Apr 2005
OpenSSH was downloaded from IBM's Sourceforge "OpenSSH on AIX" project
(http://sourceforge.net/projects/openssh-aix)

I do not know what compile options were used.  sshd_config options and sshd debug output will be attached.
Comment 1 Steve Bassler 2005-12-20 02:41:43 AEDT
Created attachment 1045 [details]
sshd debug output

sshd -ddd output for both normal and forced password change sessions
Comment 2 Steve Bassler 2005-12-20 02:45:22 AEDT
Created attachment 1046 [details]
sshd_config
Comment 3 Steve Bassler 2005-12-20 02:46:39 AEDT
Created attachment 1047 [details]
ssh_config
Comment 4 Darren Tucker 2005-12-20 10:42:44 AEDT
IBM's packages have modifications in them and I don't know exactly what those are.
Does the problem occur with 4.2p1 built from the source from http://openssh.com?
Comment 5 Steve Bassler 2005-12-20 23:00:57 AEDT
(In reply to comment #4)
> IBM's packages have modifications in them and I don't know exactly what those
> are.
> Does the problem occur with 4.2p1 built from the source from
> http://openssh.com?

I don't know.  I had been rolling my own for years, but decided to use IBM's package because I tried two or three times, but was not able to compile 4.1 myself.  When I get some time, I'll try again with 4.2.  Is IBM's source not available?
Comment 6 Darren Tucker 2005-12-20 23:25:56 AEDT
(In reply to comment #5)
> I don't know.  I had been rolling my own for years, but decided to use IBM's
> package because I tried two or three times, but was not able to compile 4.1
> myself.  When I get some time, I'll try again with 4.2.

"The source won't compile" is something we can help with, but "some else's binaries don't work" isn't.  I test regularly on AIX with gcc so that usually works, however I no longer have access to any of the IBM native compilers (xlc, vac).  I don't have access to a 5.3 box though, so it could be something peculiar to that version.

Alternatively, I provide precompiled packages of the vanilla source (the most recent one also being 4.1, I never got around to packaging 4.2) at http://www.zip.com.au/~dtucker/openssh/ .  If you trust me (but you shouldn't :-) you could use these on a test box to quickly determine whether or not the problem exists in an unmodified sshd.

> Is IBM's source not available?

There's source (or diffs, I forget which) for some older versions of the package but not the current ones.  I'm reasonably sure that there are some additional changes between the the versions for which source is available.
Comment 7 Darren Tucker 2006-06-23 19:50:41 AEST
Tried reproducing with 4.3p2 on AIX 5200-05 (I don't have access to 5.3) with an account flagged ADMCHG and it worked OK.

Sorry, but we can't help with third-party binary packages, closing bug.  If you can reproduce with vanialla 4.3p2 then please reopen, or if you are still having building 4.3p2 from source please open a new bug for that.
Comment 8 Darren Tucker 2006-10-07 11:43:48 AEST
Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.