From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: Re: [Qemu-devel] vnc port selection
Date: Sun, 24 Aug 2008 11:01:29 +0100 [thread overview]
Message-ID: <20080824100128.GB24946@shareable.org> (raw)
In-Reply-To: <48B121D6.6060008@qumranet.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
> >
> >>Alternatively, have the management application pass an fd denoting
> >>the socket.
> >
> >If you are allocating the ports in the management tool, then just tell
> >QEMU what port to open up. I don't think you gain anything passing an
> >fd.
> >
>
> It prevents races, allows listening on non-traditional sockets (vnc over
> unix-domain), and allows privilege separation.
Agreed: races are particularly irksome.
I have the same problem in another application, where one program
allocates a fee port, but another (SSH tunnel) opens it. It's very
annoying that the second program fails from time to time, due to the
race.
-- Jamie
WARNING: multiple messages have this Message-ID (diff)
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: Re: vnc port selection
Date: Sun, 24 Aug 2008 11:01:29 +0100 [thread overview]
Message-ID: <20080824100128.GB24946@shareable.org> (raw)
In-Reply-To: <48B121D6.6060008@qumranet.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
> >
> >>Alternatively, have the management application pass an fd denoting
> >>the socket.
> >
> >If you are allocating the ports in the management tool, then just tell
> >QEMU what port to open up. I don't think you gain anything passing an
> >fd.
> >
>
> It prevents races, allows listening on non-traditional sockets (vnc over
> unix-domain), and allows privilege separation.
Agreed: races are particularly irksome.
I have the same problem in another application, where one program
allocates a fee port, but another (SSH tunnel) opens it. It's very
annoying that the second program fails from time to time, due to the
race.
-- Jamie
next prev parent reply other threads:[~2008-08-24 10:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 16:37 [Qemu-devel] vnc port selection Gerd Hoffmann
2008-08-21 16:37 ` Gerd Hoffmann
2008-08-21 17:31 ` [Qemu-devel] " Anthony Liguori
2008-08-21 14:34 ` acue
2008-08-21 14:34 ` acue
2008-08-21 18:30 ` [Qemu-devel] " Avi Kivity
2008-08-21 18:35 ` Anthony Liguori
2008-08-21 19:53 ` [Xen-devel] " Daniel P. Berrange
2008-08-21 19:53 ` Daniel P. Berrange
2008-08-24 8:54 ` Avi Kivity
2008-08-24 10:01 ` Jamie Lokier [this message]
2008-08-24 10:01 ` Jamie Lokier
2008-08-26 10:15 ` [Xen-devel] Re: [Qemu-devel] " Ian Jackson
2008-08-26 10:15 ` Ian Jackson
2008-08-21 19:52 ` [Xen-devel] " Daniel P. Berrange
2008-08-21 19:52 ` Daniel P. Berrange
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=20080824100128.GB24946@shareable.org \
--to=jamie@shareable.org \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.