Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xauth file / .Xauthority #2

Open
1wilkens opened this issue Dec 28, 2016 · 0 comments
Open

xauth file / .Xauthority #2

1wilkens opened this issue Dec 28, 2016 · 0 comments

Comments

@1wilkens
Copy link
Owner

1wilkens commented Dec 28, 2016

Currently an xauth file is generated and written to disk but not used when launching X, because the concept of .Xauthority is not quite clear. Adding the flag to the launch prevents gtk from opening the display. This is weird because the main ui (via gtk) will always be executed as root and as such should have access to X under all circumstances.

Also it is just not clear what .Xauthority actually does. In theory it should limit access to the X server but the auth file via startx actually contains multiple magic cookies while .Xauthority only contains 1.

More research is required to figure out what the "best practices" are.
Although this is an enhancement it is the de-facto standard in all other display managers so it is a blocker for v0.1

@1wilkens 1wilkens added this to the v0.1 milestone Dec 28, 2016
@1wilkens 1wilkens changed the title xauth file / .Xauthority xauth file / .Xauthority Dec 28, 2016
@1wilkens 1wilkens self-assigned this Dec 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant