On Thu, May 03, 2018 at 10:05:49 +0200, Jiri Denemark wrote:
On Wed, May 02, 2018 at 10:36:57 +0200, Jiri Denemark wrote:
> On Wed, May 02, 2018 at 09:44:08 +0200, Peter Krempa wrote:
> > Signed-off-by: Peter Krempa <pkrempa(a)redhat.com>
> > ---
> > docs/news.xml | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/docs/news.xml b/docs/news.xml
> > index caeda159a8..af57751e0c 100644
> > --- a/docs/news.xml
> > +++ b/docs/news.xml
> > @@ -157,6 +157,18 @@
> > </change>
> > </section>
> > <section title="Bug fixes">
> > + <change>
> > + <summary>
> > + qemu: TLS migration now enforces use of TLS for the NBD connection
> > + </summary>
> > + <description>
> > + When the VIR_MIGRATE_TLS flag was used with the migration API
libvirt
> > + did not ensure that the NBD connection was using TLS as well. The
code
> > + now rejects such migration as the TLS transport for NBD is not
ready
> > + yet, but prevents a false sense of security that TLS would be used.
> > + The support TLS for NBD will be added soon.
> > + </description>
> > + </change>
> > </section>
> > </release>
> > <release version="v4.1.0" date="2018-03-05">
>
> Reviewed-by: Jiri Denemark <jdenemar(a)redhat.com>
Oops, I didn't notice you documented this for an older release. This
should be moved to the v4.3.0 section.
Me neither. I noticed that in the release announcement. I was thinking
of a way how to prevent this though.