[OpenAFS] .Xauthority issues

[Neulinger, Nathan]

Simplest approach:

~: system:anyuser l
~/public: system:anyuser rl

Then just link anything to public that needs to be in ~ but has to be
publically readable.

More complicated approach - build custom xdm that puts .Xauthority
somewhere else.

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Martin Schulz [mailto:schulz@iwrmm.math.uni-karlsruhe.de]=20
> Sent: Tuesday, March 12, 2002 12:35 PM
> To: openafs-info@openafs.org
> Subject: [OpenAFS] .Xauthority issues
>=20
>=20
> Hello,=20
>=20
> due to the directory-wise access control in AFS, the files in the
> homedirectory are open for anyone I like to give access to part of my
> data. However, there are several files that are not for public.=20
>=20
> The ususal handling is to move these into a subdirectory with a more
> restrictive ACL and supply a link from the original location pointing
> into that subdirectory.=20
>=20
> That works well for .ssh, but not for ~/.Xauthority. I observed that
> the link gets deleted and replaced by a new file, again open to read.=20
>=20
> I can't be the first one to face that, what are your solutions to this
> problem? I already found out that both {x,g,k)dm and sshd show the
> abovementioned behaviour.=20
>=20
>=20
>=20
> Yours,
> --=20
> Martin Schulz                            =20
> schulz@iwrmm.math.uni-karlsruhe.de
> Uni Karlsruhe, Institut f. wissenschaftliches Rechnen u.=20
> math. Modellbildung
> Engesser Str. 6, 76128 Karlsruhe
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20