Linux – TigerVNC viewer: no matching security types

linuxraspberry pirealvncvncvnc-viewer

I'm trying to remote control the desktop of a Raspberry Pi (Raspbian Jessie) from a Samsung Chromebook (ARM Arch Linux).

The VNC server running on the Pi is RealVNC.

The VNC viewer on the Chromebook is TigerVNC

I'm getting the following error when I try to connect to the server:

$ vncviewer

TigerVNC Viewer 32-bit v1.7.1
Built on: 2017-01-23 06:48
Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.

Sat Apr  1 17:25:49 2017
 DecodeManager: Detected 4 CPU core(s)
 DecodeManager: Creating 4 decoder thread(s)
 CConn:       conectado a puerto 192.168.1.200 de origen 5900
 CConnection: Server supports RFB protocol version 5.0
 CConnection: Using RFB protocol version 3.8
 CConnection: No matching security types
 CConn:       No matching security types

As far as I understood by reading the man pages, vncviewer attempts by default every supported scheme:

   -SecurityTypes sec-types
          Specify  which security schemes to attempt to use when authenti‐
          cating with the server.  Valid values are a comma separated list
          of  None,  VncAuth,  Plain, TLSNone, TLSVnc, TLSPlain, X509None,
          X509Vnc and X509Plain. Default is  to  attempt  every  supported
          scheme.

Does RealVNC use some encryption scheme that is not supported by TigerVNC?

Best Answer

Assuming RealVNC is not supported on the platform you are using (which is my case with arm64 Arch) I found the following solution.

  1. As root, edit the config file in /root/.vnc/config.d/vncserver-x11
  2. Insert the following at the bottom of the file
Authentication=VncAuth
Encryption=AlwaysOff
Password=e0fd0472492935da
  1. Restart RealVNC sudo systemctl restart vncserver-virtuald.service (or just reboot)
  2. Change the password (which is apparently foobar but never leave a password to something that has been posted.) with
sudo vncpasswd -service

You can now use another VNC client to access you RealVNC server. You will get a warning that the connection is not secure, that is the cost of access as far as I can tell; but, inside my LAN it is probably OK.

Related Question