Joerg Schilling wrote:
> Alan Coopersmith <[EMAIL PROTECTED]> wrote:
>
>> Joerg Schilling wrote:
>>> Good question, but I don't know. The problem I see with Xscreensaver is that
>>> it is installed suid root on SXCE and thus is unable to read ~/.Xauthority
>>> from NFS mounted home directories. Removing the suid root did fix the
>>> problem
>>> for me.
>> And broke the ability for it to read /etc/shadow for locally-defined
>> users to be able to unlock the screen. We don't make things suid-root
>> without a damn good reason.
>
> A cannot call this a "solution" as it does not work for me the way it is
> delivered
> in SXCE-77.
>
> If you do make things suid root for "good reason", you should also modify the
> source to try again with euid == uid after the attempt to read ~/.Xauthority
> failed.
The upstream is already setuid root, so we shouldn't have to modify a thing
there, and I believe it already does call XOpenDisplay() as the uid (the
program doesn't read .Xauthority, XOpenDisplay() in libX11 does). It's been
a while since I've looked at the xscreensaver code to confirm that though.
Virtually every home directory in Sun is NFS mounted, and yet it works for us,
so it's not as simple an issue as you describe. Nonetheless, since you
haven't filed a bug, the xscreensaver maintainer (not me) has no way of
knowing it's not working for you, and thus won't be fixing it until someone
reports a bug.
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
