Bug 124602 (IT_41458)

Summary: OpenSSH does not allow users to change expired passwords when privsep is used
Product: Red Hat Enterprise Linux 3 Reporter: Mark Post <mark.post>
Component: opensshAssignee: Tomas Mraz <tmraz>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: ckloiber, cranschau, ffillion, glafave, k.georgiou, lasalle, lsof, nalin, shanew, tao, tom.webster
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-05-18 13:48:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 132991    
Description Flags
Proposed patch none

Description Mark Post 2004-05-27 20:40:17 UTC
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):

How reproducible:

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.

Additional info:

Comment 1 Mark Post 2004-06-14 16:41:17 UTC
Can I get an update on this problem report?  It's been almost three
weeks.  Thanks.

Comment 7 Cory Ranschau 2005-01-05 16:17:44 UTC
I have the same issue here.  I would like to see the same Expected
Results that Mark posted.

Comment 8 Greg Lafave 2005-01-15 01:23:41 UTC
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 
RPM.  Thanks!

Comment 9 Tomas Mraz 2005-02-01 16:08:22 UTC
Created attachment 110500 [details]
Proposed patch

This patch should solve the issue - it uses passwd binary to change the
password as in current openssh-3.9p1.

Comment 11 Tomas Mraz 2005-02-07 14:35:17 UTC
*** Bug 112820 has been marked as a duplicate of this bug. ***

Comment 12 Tomas Mraz 2005-02-07 15:03:04 UTC
*** Bug 117429 has been marked as a duplicate of this bug. ***

Comment 13 Mark Post 2005-02-07 15:44:56 UTC
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.


Comment 14 Tomas Mraz 2005-02-07 16:29:47 UTC
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...

Comment 16 Tom Webster 2005-02-18 21:10:04 UTC
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


Comment 17 Tomas Mraz 2005-02-18 22:46:38 UTC
The * is a wildcard character meaning client- server- and other packages.

Comment 18 Tom Webster 2005-03-22 18:28:56 UTC
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.

Comment 20 Jurvis LaSalle 2005-04-06 21:52:55 UTC
it seems the test rpms have moved.  can i get a full URL to test them out?

Comment 21 Jurvis LaSalle 2005-04-07 00:39:55 UTC
To answer my question-  http://people.redhat.com/tmraz/testing/i386/ .
Anyone know when these rpms will come out of testing?  T

Comment 23 Francis 2005-04-25 18:42:01 UTC
So does somebody has news about when the rpm will out of testing?

Comment 24 Tim Powers 2005-05-18 13:48:32 UTC
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.