Bug 951743

Summary:	(usermod -U) can't undo (passwd -l)
Product:	Red Hat Enterprise Linux 6	Reporter:	Miloslav Trmač <mitr>
Component:	shadow-utils	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED ERRATA	QA Contact:	Patrik Kis <pkis>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0	CC:	david, mvollmer, pkis
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	shadow-utils-4.1.5.1-2.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-10 23:59:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Miloslav Trmač 2013-04-12 23:55:05 UTC

Description of problem:
Libuser (called passwd) is currently using "!!" to lock passwords, not "!" as usermod expects.  So $summary.

While libuser might be changed, usermod should be modified to handle "!!" (or preferably? do what libuser does in modules/files.c:lock_process) so that passwords previously locked through passwd can be unlocked.

See #853153 for more information.

Comment 3 RHEL Program Management 2013-10-13 23:42:16 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 4 Miloslav Trmač 2014-09-30 14:21:11 UTC

*** Bug 1148008 has been marked as a duplicate of this bug. ***

Comment 7 David Lewis 2015-12-01 17:13:40 UTC

This issue is found in RHEL 7 as well.

Comment 8 Tomas Mraz 2015-12-02 08:46:36 UTC

Yes, that's bug 1185425

Comment 13 errata-xmlrpc 2016-05-10 23:59:47 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0864.html