Installation and Setup Guide

Use the view.sslVerificationMode property to set the default verication mode:
n
1 implements Full Verification.
n
2 implements Warn If the Connection May Be Insecure.
n
3 implements No Verification Performed.
To congure the mode so that end users cannot change the mode, set the view.allowSslVerificationMode
property to "False" in the /etc/vmware/view-mandatory-config le on the client system. See “Horizon
Client Conguration Seings and Command-Line Options,” on page 29.
Configuring Advanced TLS/SSL Options
You can select the security protocols and cryptographic algorithms that are used to encrypt communications
between Horizon Client and servers, or between Horizon Client and the agent in the remote desktop.
These options are also used to encrypt the USB channel (communication between the USB service daemon
and the agent).
With the default seing, cipher suites use 128- or 256-bit AES, remove anonymous DH algorithms, and then
sort the current cipher list in order of encryption algorithm key length.
By default, TLS v1.0, TLS v1.1, and TLS v1.2 are enabled. SSL v2.0 and v3.0 are not supported.
N If TLS v1.0 and RC4 are disabled, USB redirection does not work when users are connected to
Windows XP desktops. Be aware of the security risk if you choose to make this feature work by enabling
TLS v1.0 and RC4.
If you congure a security protocol for Horizon Client that is not enabled on the server to which the client
connects, a TLS/SSL error occurs and the connection fails.
I At least one of the protocols that you enable in Horizon Client must also be enabled on the
remote desktop. Otherwise, USB devices cannot be redirected to the remote desktop.
On the client system, you can use either conguration le properties or command-line options for these
seings:
n
To use conguration le properties, use the view.sslProtocolString and view.sslCipherString
properties.
n
To use command-line conguration options, use the --sslProtocolString and --sslCipherString
options.
For more information, see “Using the Horizon Client Command-Line Interface and Conguration Files,” on
page 28 and look up the property and option names in the table in “Horizon Client Conguration Seings
and Command-Line Options,” on page 29.
Configuring Specific Keys and Key Combinations to Send to the Local
System
Starting with Horizon Client, if you use PCoIP, or, starting with Horizon Client 4.0, it you use VMware Blast
or PCoIP, you can create a view-keycombos-config le to specify which individual keys and key
combinations should not be forwarded to the remote desktop.
You might prefer to have some keys or key combinations handled by your local client system when working
in a remote desktop. For example, you might want to use a particular key combination to start the screen
saver on your client computer. You can create a le located at /etc/vmware/view-keycombos-config and
specify the key combinations and individual keys.
VMware Horizon Client for Linux Installation and Setup Guide
44 VMware, Inc.