From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Ben Aitchison <ben@meh.net.nz>,
qemu-stable@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-stable] [PATCH STABLE 2.5] vnc: fix VNC websockets TLS handshake
Date: Tue, 20 Sep 2016 11:49:34 -0500 [thread overview]
Message-ID: <20160920164934.7471.89469@loki> (raw)
In-Reply-To: <20160914150210.GA9563@redhat.com>
Quoting Daniel P. Berrange (2016-09-14 10:02:10)
> ping
>
> Is qemu-stable dead for the 2.5 branch or was this just
> missed ?
The stable branches generally die once the next major release lands and
I switch over to supporting the new stable tree. Generally there's x.y.1
stable release mid-development cycle for the next major release, and,
depending on the severity/number of fixes or regressions in the x.y.1
release, an x.y.2 that overlaps with the x.y+1.0 major release. There
may be any number of x.y.z.n CVE releases in between, but generally
even for these we still drop support once the next major release has
firmly landed and leave it to the downstreams to handle any LTS beyond
that.
>
> On Tue, Jun 07, 2016 at 03:17:33PM +0100, Daniel P. Berrange wrote:
> > If the VNC websockets TLS handshake blocked, we register a
> > callback to continue it after the socket signals data is
> > available. Unfortunately we were mistakenly registering
> > the wrong method callback, causing us to restart the TLS
> > handshake from the begining, which obviously fails.
> >
> > Reported-by: Ben Aitchison <ben@meh.net.nz>
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > ---
> > ui/vnc-ws.c | 12 ++++++------
> > 1 file changed, 6 insertions(+), 6 deletions(-)
> >
> > NB this is a stable-2.5 only patch, with no equiv in master
> > since the code was totally refactored in 2.6
> >
> > diff --git a/ui/vnc-ws.c b/ui/vnc-ws.c
> > index 175ea50..a8cf180 100644
> > --- a/ui/vnc-ws.c
> > +++ b/ui/vnc-ws.c
> > @@ -22,8 +22,9 @@
> > #include "qemu/main-loop.h"
> > #include "crypto/hash.h"
> >
> > -static int vncws_start_tls_handshake(VncState *vs)
> > +static void vncws_run_tls_handshake(void *opaque)
> > {
> > + VncState *vs = (VncState *)opaque;
> > Error *err = NULL;
> >
> > if (qcrypto_tls_session_handshake(vs->tls, &err) < 0) {
> > @@ -42,22 +43,21 @@ static int vncws_start_tls_handshake(VncState *vs)
> >
> > case QCRYPTO_TLS_HANDSHAKE_RECVING:
> > VNC_DEBUG("Handshake interrupted (blocking read)\n");
> > - qemu_set_fd_handler(vs->csock, vncws_tls_handshake_io, NULL, vs);
> > + qemu_set_fd_handler(vs->csock, vncws_run_tls_handshake, NULL, vs);
> > break;
> >
> > case QCRYPTO_TLS_HANDSHAKE_SENDING:
> > VNC_DEBUG("Handshake interrupted (blocking write)\n");
> > - qemu_set_fd_handler(vs->csock, NULL, vncws_tls_handshake_io, vs);
> > + qemu_set_fd_handler(vs->csock, NULL, vncws_run_tls_handshake, vs);
> > break;
> > }
> >
> > - return 0;
> > + return;
> >
> > error:
> > VNC_DEBUG("Handshake failed %s\n", error_get_pretty(err));
> > error_free(err);
> > vnc_client_error(vs);
> > - return -1;
> > }
> >
> > void vncws_tls_handshake_io(void *opaque)
> > @@ -84,7 +84,7 @@ void vncws_tls_handshake_io(void *opaque)
> > vs);
> >
> > VNC_DEBUG("Start TLS WS handshake process\n");
> > - vncws_start_tls_handshake(vs);
> > + vncws_run_tls_handshake(vs);
> > }
> >
> > void vncws_handshake_read(void *opaque)
> > --
> > 2.5.5
> >
>
> Regards,
> Daniel
> --
> |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
> |: http://libvirt.org -o- http://virt-manager.org :|
> |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
> |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
>
prev parent reply other threads:[~2016-09-20 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 14:17 [Qemu-devel] [PATCH STABLE 2.5] vnc: fix VNC websockets TLS handshake Daniel P. Berrange
2016-06-07 14:47 ` Eric Blake
2016-09-14 15:02 ` Daniel P. Berrange
2016-09-20 16:49 ` Michael Roth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160920164934.7471.89469@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=ben@meh.net.nz \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).