VMware GSX Server 2.5.2Features | Documentation | Knowledge Base | Discussion Forums The username, password and network packets sent to the GSX Server host over a network connection when using the VMware Remote Console or the VMware Management Interface are not encrypted in GSX Server by default. As the Administrator user (Windows hosts) or root user (Linux hosts), you can enable Secure Sockets Layer (SSL) to encrypt these sessions. When you enable SSL, security certificates are created by GSX Server and stored on your host. However, the certificates used to secure your VMware Management Interface sessions are not signed by a trusted certificate authority; therefore they do not provide authentication. If you intend to use encrypted remote connections externally, you should consider purchasing a certificate from a trusted certificate authority. Caution: GSX Server does not generate the security certificate for the VMware Management Interface on Windows NT 4.0 hosts. See Enabling SSL for the VMware Management Interface on a Windows NT Host. With SSL enabled, the remote console and management interface perform exactly as they would if SSL were disabled. When SSL is enabled for the VMware Remote Console, a lock icon appears in the lower right corner of the console window. Any remote consoles that are already open at the time SSL is enabled do not become encrypted, and the lock icon does not appear in these console windows. These consoles must be closed and new console sessions must be started to ensure encryption. When SSL is enabled for the VMware Management Interface, the URL to connect to the management interface is https://<hostname>:8333. The management interface automatically redirects users to this URL if they use the original URL (http://<hostname>:8222) to connect. In addition, a lock icon appears in the status bar of the browser window. Note: After SSL is enabled on a Windows host, any new management interface connections to the non-secure port (8222) are not redirected. Note: If you disable SSL, users are automatically redirected to http://<hostname>:8222 if they use https://<hostname>:8333 to connect to the management interface. If you prefer, you can use your own security certificate when you enable SSL. On a Windows host, run the Microsoft Management Console (mmc.exe) and select your certificate. When you upgrade the VMware Management Interface on a GSX Server for Windows host, you need to reassign your certificate to the management interface. On a Linux host, the VMware Management Interface certificate must be placed in /etc/vmware-mui/ssl. The management interface certificate consists of 2 files: the certificate itself (mui.crt) and the private key file (mui.key). The private key file should be readable only by the root user. When you upgrade the VMware Management Interface on a Linux host, the certificate remains in place and, in case you removed the management interface, the directory is not removed from your host. You enable SSL in the VMware Management Interface. Remember that the certificates used in these secure sessions are not signed by a trusted certificate authority; therefore they do not provide authentication. If you intend to use encrypted remote connections externally, you should consider purchasing a certificate from a trusted certificate authority.
In order to enable SSL for the VMware Management Interface on a Windows NT host, you must first generate a security certificate. Use Microsoft's Certificate Server to create a certificate in order to secure the management interface with SSL. To create the certificate on a Windows NT host, complete the following steps.
SSL is enabled for your management interface connections. To disable SSL for your management interface connections, go to the Microsoft Management Console and uncheck Require Secure Channel when accessing this resource in the Secure Communications dialog box. You do not need to create a certificate for the remote console manually on a Windows NT 4.0 host. |
