Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 79770 - xlockmore enables .xlockrc unconditionally if USE="-pam"
Summary: xlockmore enables .xlockrc unconditionally if USE="-pam"
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Jonathan Smith (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-27 13:11 UTC by Stefan Sperling
Modified: 2005-06-22 15:00 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
patch adding a local xlockmore use flag (xlockmore.diff,831 bytes, patch)
2005-01-27 13:12 UTC, Stefan Sperling
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Sperling 2005-01-27 13:11:49 UTC
I just installed xlockmore, and upon trying to lock my screen it prompts
me for a password. I want it to use my user's system password though, so I read the man page to find out whats going on. It says that on systems with shadow passwords, xlock _may_ not be able to get a user's password and ask for an alternate password to be stored in ~/.xlockrc. It does not say anything about
how to make xlock at least try to use system passwords.

I don't have pam in my use flags. xlockmore-5.12.ebuild passes --enable-xlockrc
to configure if pam is disabled. But since /usr/bin/xlock is installed suid
root anyway, it can read /etc/shadow just fine. If I remove --enable-xlockrc from the ebuild's $myconf, xlock behaves as expected. I can enter my user's password to unlock the screen.

Is there a way to make xlockmore always use the system password even if
xlockrc is enabled? If not, may I propose locally use-flagging this (eg USE="xlockrc")?
Comment 1 Stefan Sperling 2005-01-27 13:12:40 UTC
Created attachment 49686 [details, diff]
patch adding a local xlockmore use flag
Comment 2 Jonathan Smith (RETIRED) gentoo-dev 2005-06-22 15:00:05 UTC
fixed in 5.17-r1, but i didn't use your patch since it didn't apply cleanly