Help › In the session › E33

See whether the session is end-to-end encrypted

Which path your session takes and whether the relay could read along — shown in the analysis overlay.

Preview this guide has not yet been clicked through on a real device. Button names and steps come from the program but may differ in details.

For
Technician · Purchasing and accounting
Applies to
Free · Cloud · Own relay
Controlled device
Windows · macOS · Linux
Control from
Program (Windows, macOS, Linux) · Browser
from version
20261010.19

What it is for

A session takes one of three paths: directly between the computers, passed on by the relay (TURN) or — if the network blocks both — as a relay tunnel. Here you see which path is in use and whether it is end-to-end encrypted, that is, whether the relay cannot look inside.

What you need

A running session — with BrowserDesk on a computer or in the browser.

How to do it

  1. Program: switch on Ansicht (View) → Analyse-Overlay (Analysis overlay) in the session bar. Browser: Ansicht → Analyse-Overlay.
  2. Read the first line "Pfad" (path):
DisplayPathEnd-to-end encrypted?
Program: WebRTC · browser: DIREKT … (direct)directly between the computersyes
Browser: RELAY …passed on by the relay (TURN)yes — the relay only passes on encrypted packets
Program: Relay-Tunnel (WebSocket, verschlüsselt) · browser: RELAY-TUNNEL (WebSocket, verschlüsselt) (encrypted)relay tunnel, because the network blocks WebRTCyes, since version 20261010.19 on both sides
Program: Relay-Tunnel (WebSocket, unverschlüsselt) · browser: RELAY-TUNNEL (WebSocket, unverschlüsselt) (unencrypted)relay tunnel with an older other sideno — only encrypted up to the relay (TLS)

How you know it worked

The "Pfad" line is at the top of the overlay and is updated continuously.

Good to know

  • "unverschlüsselt" does not mean open on the internet: the way to and from the relay is always TLS-encrypted. Only the relay itself could read along in the tunnel. With an own relay that stays in-house.
  • Fix for "unverschlüsselt": bring device and viewer to version 20261010.19 or newer. Then the tunnel is end-to-end encrypted as well.
  • In the relay tunnel there is no sound (E13) and no showing of your own screen (E15).
  • What encryption does not do: no path protects against a relay that actively pretends to be the other side — the relay is the trusted intermediary.

If it does not work

You seeMeaning and fix
"Relay-Tunnel (WebSocket, unverschlüsselt)"One side has an older version. Update both.
Always relay tunnelThe network blocks WebRTC. Check firewall and proxy (H10).