Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions

  




 

 

Red Hat Enterprise Linux 6 Essentials eBook now available in PDF and ePub formats for only $9.99
RHEL 6 Essentials contains 40 chapters and over 250 pages.

19.2. Remote management over TLS and SSL

You can manage virtual machines using TLS and SSL. TLS and SSL provides greater scalability but is more complicated than ssh (refer to Section 19.1, “Remote management with SSH”). TLS and SSL is the same technology used by web browsers for secure connections. The libvirt management connection opens a TCP port for incoming connections, which is securely encrypted and authenticated based on x509 certificates.
TLS/SSL access for virt-manager
The libvirt Wiki contains complete details on how to configure TLS/SSL access: http://wiki.libvirt.org/page/TLSSetup
To enable SSL and TLS for VNC, refer to the libvirt Wiki: http://wiki.libvirt.org/page/VNCTLSSetup. It is necessary to place the Certificate Authority Certificate, Client Certificate, and Client Certificate Private Key, in the following locations:
  • The Certificate Authority Certificate should be placed in /etc/pki/CA/cacert.pem.
  • The Client Certificate, signed by the CA, should be placed in either of:
    • /etc/pki/libvirt-vnc/clientcert.pem for system wide use, or
    • $HOME/.pki/libvirt-vnc/clientcert.pem for an individual user.
  • The Private Key for the Client Certificate should be placed in either of:
    • /etc/pki/libvirt-vnc/private/clientkey.pem for system wide use, or
    • $HOME/.pki/libvirt-vnc/private/clientkey.pem for an individual user.

 
 
  Published under the terms of the Creative Commons License Design by Interspire