Bug 8610 - Using system xhost and xauth isn't robust
Summary: Using system xhost and xauth isn't robust
Status: RESOLVED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VNC (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.20.0
Assignee: Pierre Ossman
URL:
Keywords: prosaic
Depends on:
Blocks:
 
Reported: 2025-06-13 14:28 CEST by Pierre Ossman
Modified: 2025-07-09 10:14 CEST (History)
0 users

See Also:
Acceptance Criteria:
MUST: * ThinLinc should function correctly without xauth or xhost installed on the system SHOULD: * ThinLinc should include the latest versions of xauth and xhost


Attachments

Description Pierre Ossman cendio 2025-06-13 14:28:57 CEST
We require the command line tools xauth and xhost for the session to function correctly. Currently, we try to make sure they are available by having tl-setup install them.

It would be more robust if we included these tools ourselves, like we do for xprop. These are fairly small applications, so it shouldn't be much hassle.

This might become more crucial as distributions move more away from X11 in favour of Wayland.
Comment 1 Pierre Ossman cendio 2025-06-13 14:31:36 CEST
xprop currently lives in vsm/, as that's where the current users are. xauth is also currently only used by things in vsm/. xhost, on the other hand, is used by scripts in tlmisc/.

Since these are fairly general commands, perhaps it's better to gather them in a single place. These are for configuring X11, so placing them next to our X server (i.e. vnc/) probably makes most sense.
Comment 13 Pierre Ossman cendio 2025-07-09 10:14:38 CEST
All done. And seems to work just fine when testing on Ubuntu 24.04. Xauthority is correctly set up without complaints, as is the localuser addition. Also checked that tl-setup didn't complain.

> MUST:
> 
>  * ThinLinc should function correctly without xauth or xhost installed on the system

Yup.

> SHOULD:
> 
>  * ThinLinc should include the latest versions of xauth and xhost

Yup.

Note You need to log in before you can comment on or make changes to this bug.