[5873] in RedHat Linux List
Re: xlock, vlock, and shadow passwords
daemon@ATHENA.MIT.EDU (Simon Karpen)
Sun Nov 24 18:01:32 1996
Date: Sun, 24 Nov 1996 17:50:57 -0500 (EST)
From: Simon Karpen <slk@karpes.stu.rpi.edu>
Reply-To: Simon Karpen <slk@karpes.stu.rpi.edu>
To: redhat-list@redhat.com
In-Reply-To: <Pine.LNX.3.95.961124170008.22883A-100000@karpes.stu.rpi.edu>
Resent-From: redhat-list@redhat.com
i've done some more investigation into this problem.
it appears to be a simple permisions problem in both cases, rather than a
PAM related bug.
vlock works just fine if you make it setuid root. it can't be straced when
setuid, so getting root's encrypted password shouldn't be a problem.
from the source, it looks safe enough. (it's a pretty simple program...
the rcs comments take more space than the source half the time)
however, xlock gives up its priveleges after it starts up, so it really
won't work with pam+shadow. has anybody gotten xlock to work properly with
pam+shadow? if not, can anybody give me a few pointers on where to start
(i'm going to grab the latest devel srpm and start looking)
Simon Karpen
karpes@rpi.edu, slk@acm.rpi.edu, slk@karpes.stu.rpi.edu
"I'm not paranoid, it's just that everybody's out to get me."
--Linus Torvalds
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
________________________________________________________________________
http://www.redhat.com/RedHat-FAQ http://www.redhat.com/RedHat-Errata
http://www.redhat.com/RedHat-Tips http://www.redhat.com/mailing-lists
------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null
