Bug 489170 - --lock/--unlock does not return account to previous state
Summary: --lock/--unlock does not return account to previous state
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: libuser
Version: 10
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miloslav Trmač
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-08 12:16 UTC by Axel Thimm
Modified: 2009-03-12 16:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-03-12 16:40:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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 :)


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