As of November 2026 · CODLAB editorial team
Short answer: On Linux with Wayland, remote support usually runs through desktop portals: the person at the device typically grants screen sharing and remote control in a dialog provided by the desktop. For the help desk this means keeping consent, viewing and control deliberately separate, handling server access cleanly over SSH and approving or rejecting commands according to fixed rules.
1. What Wayland changes about remote support
Under the older X11, practically any program could read the screen and send input to other windows. Wayland separates this: the compositor manages screen content and input, and an ordinary application only sees its own windows. The usual route for remote support therefore goes through the interfaces of xdg-desktop-portal: the ScreenCast portal delivers the screen content as a PipeWire stream, and the RemoteDesktop portal relays keyboard and mouse input. When a session starts, the desktop typically shows a dialog in which the person at the device chooses what to share. By default the permission applies only to that session; a program can, however, request that it persist as long as the program is running or until it is explicitly revoked. If that is granted, the person does not have to choose again next time.
This is not an obstacle but a security boundary: screen and input are released at a point where consent can be given or refused. A support tool, however, has to cope with the fact that consent can also be refused, and it decides for itself whether to have a permission stored.
2. Treat consent, viewing and control separately
- Viewing is not control: someone who only needs to show where an error occurs does not need remote control. A good tool falls back to view-only when control is refused, instead of ending the session or forcing permissions.
- Consent per session: even though the portals allow a stored permission, the more cautious rule for remote support is to do without it and have every session confirmed anew. Whoever helps again tomorrow asks again tomorrow.
- Visibility: the person at the device should be able to see at any time that a session is running, and end it.
- Privacy on screen: remote support can show personal data. Agree in advance which applications may be open, and log who was connected and when.
3. Server access: handle SSH cleanly
For servers, remote support usually runs over SSH. The basic rules are well known and worth keeping in daily practice too: log in with keys instead of passwords, use personal accounts instead of shared logins, and grant only the rights that are needed. OpenSSH can bundle several connections over one shared master connection (ControlMaster); this saves logins but requires the bundled connection to be managed as carefully as each individual one. File transfer over SFTP should follow the same access rules.
4. A command gate separates approval, consent and rejection
In remote support, the command that changes something calls for particular care: it acts on the system, not just on the view. A command gate assigns every authorised command to one of three classes: approved automatically, allowed only after explicit consent, or rejected. What matters is that a rejection comes with a reason, and that in case of doubt the command is rejected rather than executed. Time-limited sessions complete the picture, so that permission once given does not keep running unnoticed.
5. AI diagnostics only with a data preview
Many tools now offer diagnostics with language models. For the help desk, the key question is what leaves the device. Before logs or status data go to an AI service, the person should be able to see which data will be sent, and agree. Using your own key for the AI service (BYOK) also keeps the contract with the provider in your hands.
6. Where CardinalHost stands today
CardinalHost, part of the Cardinal family, is listed in our product overview with the status “preview” (provider: CodLab UG (haftungsbeschränkt)): remote support, SSH/SFTP management, file transfer and consent-bound AI diagnostics in one place. Remote support covers Mac, Windows and Linux with session consent and has been field-tested on Fedora 45 / GNOME 51, with view-only mode when the portal request is refused. The command gate knows 18 rejection reasons and separates automatic approval, explicit consent and rejection for authorised commands; the macOS agent uses 30-minute sessions by default. Before every AI diagnosis with your own key, CardinalHost shows a data preview. Before market launch, the following applies: the basis of the command gate sits in the client, node verification, evidence of effect and continuous synchronisation are under construction, and free SSH remains a separate path.
You will find the technical background in our articles on Wayland and video transport and on the command gate with AI consent, and on cardinalhost.org.
Frequently Asked Questions (FAQ)
Under Wayland, an ordinary application cannot freely read the screen of other programs. Screen sharing and remote control usually run through the ScreenCast and RemoteDesktop portals of xdg-desktop-portal; the desktop typically shows a consent dialog. A stored permission can later replace that dialog if the program has requested it.
A good tool then falls back to view-only instead of ending the session. According to our product overview, CardinalHost has been field-tested on Fedora 45 / GNOME 51, with view-only mode when the portal request is refused.
A rule that approves every authorised command automatically, allows it only after explicit consent, or rejects it. According to our product overview, the one in CardinalHost knows 18 rejection reasons; free SSH remains a separate path there.