Bug 489170 - --lock/--unlock does not return account to previous state
--lock/--unlock does not return account to previous state
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: libuser (Show other bugs)
10
All Linux
medium Severity medium
: ---
: ---
Assigned To: Miloslav Trmač
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-08 08:16 EDT by Axel Thimm
Modified: 2009-03-12 12:40 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-03-12 12:40:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Axel Thimm 2009-03-08 08:16:55 EDT
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 12:40:25 EDT
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 :)

Note You need to log in before you can comment on or make changes to this bug.