Bug 489170

Summary:	--lock/--unlock does not return account to previous state
Product:	[Fedora] Fedora	Reporter:	Axel Thimm <axel.thimm>
Component:	libuser	Assignee:	Miloslav Trmač <mitr>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10	CC:	mitr
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-12 16:40:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Axel Thimm 2009-03-08 12:16:55 UTC

Description of problem:
When an account is locked with

lusermod --lock

and later unlocked with

lusermod --unlock

The account is still not working.

The account was originally encoded with SMD5 (according to openldap). Maybe libuser is only suited for certain encodings? I have crypt_style=md5 in the config.

Comment 1 Miloslav Trmač 2009-03-12 16:40:25 UTC

Thanks for your report.

This happens with LDAP, right?  libuser supports only {crypt}; {smd5}xxx would be treated as a plain-text password and re-encrypted before locking.

The next release of libuser (after the F11 translation deadline) will report an error instead of re-encrypting LDAP passwords in that way.

If you use libuser to change passwords, it will always use {crypt}; to support other schemes, libuser should probably support RFC3062 (although that doesn't support locking/unlocking accounts at all).  Patches accepted :)