From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: FW: qemu-dm exit(1) for invalid option '-vncviewer' -- Xen #18023
Date: Fri, 11 Jul 2008 11:46:42 +0100 [thread overview]
Message-ID: <20080711104642.GB15083@redhat.com> (raw)
In-Reply-To: <18551.14417.318546.860543@mariner.uk.xensource.com>
On Fri, Jul 11, 2008 at 11:39:13AM +0100, Ian Jackson wrote:
> Keir Fraser writes ("FW: [Xen-devel] qemu-dm exit(1) for invalid option '-vncviewer' -- Xen #18023"):
> > Conversation: qemu-dm exit(1) for invalid option '-vncviewer' -- Xen #18023
> > Subject: [Xen-devel] qemu-dm exit(1) for invalid option '-vncviewer' -- Xen
> > #18023
>
> This option works (worked) by passing the caller's display and
> xauthority through xm and xend to qemu. qemu then connects to it
> later. This is a very remarkable way of going about things. Its
> security properties are problematic from several points of view.
>
> I had assumed that because it was so strange no-one would be using it,
> so I deliberately dropped that change. Evidently I was wrong. If
> this is a feature that is seriously used then I could reinstate it but
> I think it should come with a health warning.
I think it should be killed - its easy todo it in the 'xm' client code,
after all xm already knows how to spawn 'xm console' for text mode
display - this is just same use case in graphical mode.
> A better place to implement this would be xm or some higher level
> tool, I think, but that wouldn't be sensible at this stage of the
> release cycle.
xm already seems to have some kind of vncviewer support, though its
running it in listen mode, rather than connect mode.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2008-07-11 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 7:54 qemu-dm exit(1) for invalid option '-vncviewer' -- Xen #18023 Li, Haicheng
[not found] ` <C49CD85B.1AD86%keir.fraser@eu.citrix.com>
2008-07-11 10:39 ` FW: " Ian Jackson
2008-07-11 10:46 ` Daniel P. Berrange [this message]
2008-07-11 15:27 ` John Levon
2008-07-11 15:34 ` Daniel P. Berrange
2008-07-11 15:41 ` John Levon
2008-07-11 16:30 ` Trolle Selander
2008-07-11 16:35 ` John Levon
2008-07-11 16:55 ` Trolle Selander
2008-07-11 17:23 ` Samuel Thibault
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=20080711104642.GB15083@redhat.com \
--to=berrange@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir.fraser@eu.citrix.com \
--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.