Bug 1020044 - accountsservice needs fix for gnome unlock screen
Summary: accountsservice needs fix for gnome unlock screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: accountsservice
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-16 21:00 UTC by Ray Strode [halfline]
Modified: 2014-09-13 18:57 UTC (History)
2 users (show)

Fixed In Version: accountsservice-0.6.35-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:56:03 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ray Strode [halfline] 2013-10-16 21:00:04 UTC
GNOME's unlock screen will avoid locking if it thinks the user has no password.  accountsservice incorrectly says the user has no password for remote users.

We need this fix:

http://cgit.freedesktop.org/accountsservice/commit/?id=631c57790fe79ee70d79522eb1b3e461e2899d82

user: treat NULL shadow entry as "password handled remotely"

Right now we set the password mode of a user based on the password hash in shadow. SSSD (and other remote login facilities presumably) don't send the password hash over the wire to the client, but of course those users do have a password set. This commit changes the code to notice when there's no shadow entry for a user and treat that case conservatively (assume user has a password). 

Related to: https://bugzilla.gnome.org/show_bug.cgi?id=708997 
https://bugs.freedesktop.org/show_bug.cgi?id=70005 

Though, if bug 1019488 goes through, we can just close this bug, since 0.6.35 includes the fix.

Comment 1 Ray Strode [halfline] 2013-10-28 14:10:27 UTC
(bug 1019488 went through, so we can close this one too)

Comment 5 Ludek Smid 2014-06-13 09:56:03 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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