TightGate Viewer for Linux
The TightGate viewer is available free of charge for current Debian-based distributions in the support area of the m-privacy website GmbH.
Installation
The packages provided only install the TightGate Viewer. The programmes required for sound transmission must be installed additionally according to the distribution. All packages for the programme Pulseaudio are required, the further configuration is not necessary.
Configuration
The configuration of the TightGate viewer under Linux is the same as under Windows. Only the configuration files are located in other places in the file system. A system-wide configuration file can be found at /etc/tgpro.cfg, the user-specific files are located at ~/.vnc/tgpro.vnc.
Configuring the Viewer for login with user name and password
As under Windows, before starting the programme for the first time, you can enter the two lines ServerName=<IP-Adresse> and e.g. SecurityTypes=TLSPlain (for password login without checking the server certificate).
Once this has been done, it is sufficient to call up the programme via
tightgateviewer
to establish the connection to the TightGate server.
If neither of the two files exists yet, it is not necessary to create them manually with an editor. Instead, the first call with
tightgateviewer <Auflösbarer DNS-Name von TightGate-Pro>
causes a connection with access data. If the name of TightGate-Pro was entered for the first time, TightGate-Viewer automatically creates a subdirectory .vnc in the home directory of the logged-in user and creates a configuration file tgpro.vnc with the IPv4 address of the server. From now on, to connect to the same server, it is sufficient to enter
tightgateviewer
to get directly to the login dialogue. Alternatively, the TightGate viewer can also be started via the start menu.
Configuring the viewer for certificate-based single sign-on
For the certificate-based single sign-on to TightGate-Pro Server, it should be ensured that the value X509Cert is entered in the user-specific configuration file or (if this is not available) in the system-wide configuration file behind the entry SecurityTypes= . In addition, it is necessary that the corresponding certificates are stored on the workstation PC for each user in his or her directory ~/.vnc.