Hi again, Good to know I'm not alone in this boat, I'll give a shot with a local Xauthority and fall back to xlock in case I'm not satisfied with the outcome. Anyway many thanks for the answers you all provided, this mailing list sure is useful.
Merry Christmas to all! Thomas. On Wed, Dec 22, 2010 at 8:58 PM, Andrew Deason <[email protected]>wrote: > On Wed, 22 Dec 2010 14:35:05 -0500 (EST) > "Thomas M. Payerle" <[email protected]> wrote: > > > I do not see any good ways to get around this. Allowing something > > w/out user's tokens read access to ~/.Xauthority seems rather > > questionable, plus awkward as needs some access to ~ as well. Could > > probably hack gnome-screensaver to pass the magic cookie, etc. to the > > dialog process to avoid it requiring access to ~/.Xauthority, but I > > doubt gnome-screensaver maintainers would be interested in supporting > > that sort of change for a small user base of AFS users. > > Store the user's Xauthority on local disk, not in AFS (/tmp, /var/tmp, > et al work fine). GDM and other display managers have an option for > this; it's typically recommended whenever $HOME is on any network > filesystem. > > -- > Andrew Deason > [email protected] > > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info >
