Hide Forgot
Clone of QEMU bug to track libvirt enablement tasks for native TLS encryption with NBD channel used for disk access. +++ This bug was initially created as a clone of Bug #1300772 +++ +++ This bug was initially created as a clone of Bug #1300770 +++ Description of problem: The NBD protocol currently runs in clear text, offering no security protection for the data transferred, unless it is tunnelled over some external transport like SSH. Such tunnelling is inefficient and inconvenient to manage, so there is a desire to add explicit support for TLS to the NBD clients & servers provided by QEMU. A particular focus is on the need to have encryption of NBD channels used for disk copy during migration. Latest patch series implementing TLS for NBD is https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg03440.html
Added upstream by: commit 2be3732dfb1edad9acfcaad376c9b09c80d469f5 Author: Peter Krempa <pkrempa@redhat.com> Date: Tue May 29 13:57:17 2018 +0200 qemu: domain: Add support for TLS for NBD https://bugzilla.redhat.com/show_bug.cgi?id=1544869 Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> commit bd0694bfd3c172ff907a6778d8d4ce405cecaf2c Author: Peter Krempa <pkrempa@redhat.com> Date: Thu May 31 20:21:48 2018 +0200 qemu: conf: Add qemu.conf knobs for setting up TLS for NBD Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
Oops, I've posted commit IDs from a private branch. The upstream commit IDs are: commit 8ac9db0e5497aa0d374865c7f849bfa27e73c98b Author: Peter Krempa <pkrempa@redhat.com> Date: Tue May 29 13:57:17 2018 +0200 qemu: domain: Add support for TLS for NBD commit ca108ab78949152dbc325d6874959049ad7d2acc Author: Peter Krempa <pkrempa@redhat.com> Date: Thu May 31 20:21:48 2018 +0200 qemu: conf: Add qemu.conf knobs for setting up TLS for NBD
Verified as:https://bugzilla.redhat.com/show_bug.cgi?id=1300772#c6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:3113