Releases/FeatureVirtSecurity

From FedoraProject

Jump to: navigation, search

Contents

Virtualization Security

Summary

There are no secure remote management capabilities in Xen, KVM or QEMU. All areas where management of Xen, KVM or QEMU involves network connections need to be run with TLS encryption, and client/server certificate checking. The scope of this extends to management APIs, remote console (VNC) and guest migration between hosts.

Owner

Current status


Usage cases/rationale

Scope

Requires working with upstream libvirt, Xen, QEMU and KVM communities to achieve a consistent approach to security throughout the software stack. At very least must allow TLS encryption to be viable for large scale enterprise use. Supporting tunnelling over SSH connections is also desirable, but lower priority.

Test Plan

Dependencies

libvirt, xen, qemu, kvm, virt-manager.

Details

REQUIRED

virt-manager (Complete)

gtk-vnc (Complete)

virt-install (Complete)

virt-viewer (Complete)

libvirt

xen

KVM

QEMU

OPTIONAL

virt-manager

libvirt

Contingency Plan

The basic level of TLS support at the libvirt API layer is already complete. If the QEMU VNC TLS patches are not completed in time, virt-maanger will be restricted to only use SSH tunnels, rather than offering choice of TLS vs SSH.

Migration support is already optional bonus point and thus requires no contingency plan.

Documentation

Release Notes

TODO list: