Red Hat Bugzilla – Bug 124602
OpenSSH does not allow users to change expired passwords when privsep is used
Last modified: 2007-11-30 17:07:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4)
Gecko/20030624 Netscape/7.1 (ax)
Description of problem:
This is a followup to bug # 83585
I have clients that are experiencing this problem, because our
security standards dictate that privilege separation be used. The
errata produced for 83585 requires turning this off, so that is not
workable for us.
The OpenSSH developers have fixed this problem in version 3.8. I need
to have this functionality inserted into a supported Red Hat RPM.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have an expired user account
2. Have OpenSSH configured to use privsep
3. Try to login to the system
Actual Results: The connection is dropped.
Expected Results: The user be prompted for their old and new passwords.
Can I get an update on this problem report? It's been almost three
I have the same issue here. I would like to see the same Expected
Results that Mark posted.
I am also having this issue. Per security Standards we need to have
Privledge Separation and Password Expiry working. Can we get a ETA
on a fix for this? I'm pretty sure this is already solved in the
openssh comunity and we just need the backpatches install in this
Created attachment 110500 [details]
This patch should solve the issue - it uses passwd binary to change the
password as in current openssh-3.9p1.
*** Bug 112820 has been marked as a duplicate of this bug. ***
*** Bug 117429 has been marked as a duplicate of this bug. ***
So, do you have a test RPM package we can install and try this out? We'll be
willing to put it on quickly and provide feedback.
You can test them:
Of course they are with the disclaimer that they are purely unofficial and not
tested thoroughly so they can eat your system and so on...
We are seeing the same problem and have the same security requirment
issues (priv seperation on and users passwords pre-expired).
I'd be willing to test the proposed patch, but I'm wondering if the
"*" preceeding the version number is going to mess with up2date? I'd
like to be able to drop in the test and then have up2date roll the
blessed patch over it rather than having to do rpm surgery.
PS Currently using: RHEL R3U4 with openssh-3.6.1p2-33.30.3
The * is a wildcard character meaning client- server- and other packages.
The test kit has been working fine for me for a couple of weeks. Behavior is
to force user to change password, then boot their connection. Next login is
OK with updated password.
it seems the test rpms have moved. can i get a full URL to test them out?
To answer my question- http://people.redhat.com/tmraz/testing/i386/ .
Anyone know when these rpms will come out of testing? T
So does somebody has news about when the rpm will out of testing?
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.