Fudo One supports connections over RDP, SSH and VNC protocols.

Supported RDP features

Supported client applications:

All official Microsoft clients for Windows and macOS,
FreeRDP 2.0 and newer.

Notes:

RDP protocol implementation supports user authentication over RADIUS in challenge-response mode.
For RDP servers are supported NLA mode and TLS mode.
For RDP listeners is supported Enhanced RDP Security with TLS.

In case the NLA option enabled, Fudo One requires NTLM protocol version 2 or newer. To properly handle NLA authentication connections, enable option to only send NTLMv2 response both on client and server side.

Click Start > All Programs > Accessories > Run.
Type secpol.msc in the Open input field and click OK.
Select Local Policies > Security Options and double-click Network Security: LAN Manager authentication level.
Select Send NTLMv2 response only. Refuse LM & NTLM from the drop-down list.
Click Apply.

Fudo One verifies input language settings when negotiation connection and does not support dynamic language change on the login screen.

Supported SSH features

Connections multiplexing (video export, session termination, pause, join, playback, raw data),
SCP (raw data, session termination, extracting separate files),
SFTP,
2FA,
Port redirection (video export, session termination, pause, session join, playback, raw data),
SSH Agent forwarding (transparent, not recorded),
X11 - within SSH protocol (video export, session termination, pause, session join, playback, raw data),
Shell (video export, session termination, pause, session join, playback, raw data),
Terminal (video export, session termination, pause, session join, playback, raw data).

Supported encryption algorithms:

Server: RSA, DSA
Listener: RSA, DSA

Supported hashing algorithms:

MD5
SHA256

Supported types of SSH keys:

RSA
ED25519, ED25519-SK
ECDSA, ECDSA-SK
DSA (with the Legacy ciphers option enabled)

Supported encoding: UTF-8

SSH protocol implementation supports user authentication over RADIUS in challenge-response mode.

Supported VNC features

Supported client applications:

TightVNC,
RealVNC.

VNC protocol implementation supports user authentication over RADIUS in challenge-response mode.

Connection specifics:

VNC server requires authentication

Regular type of Account: requires user login and password (authentication against Fudo); login substitution string defined in the account is ignored upon establishing connection.
Forward type of Account: requires from a user to input password, defined on the VNC server (login string is ignored).

VNC server does not require authentication

Regular type account: requires user login and password (authentication against Fudo); password substitution string can be left empty as it is not forwarded to the target host.
Forward type account: requires user login and password (authentication against Fudo).