From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MM4fb-0002IH-QY
	for qemu-devel@nongnu.org; Wed, 01 Jul 2009 14:36:35 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MM4fV-0002FJ-Op
	for qemu-devel@nongnu.org; Wed, 01 Jul 2009 14:36:34 -0400
Received: from [199.232.76.173] (port=39339 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MM4fV-0002FA-EA
	for qemu-devel@nongnu.org; Wed, 01 Jul 2009 14:36:29 -0400
Received: from mail-ew0-f211.google.com ([209.85.219.211]:62283)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1MM4fV-0002vN-0Z
	for qemu-devel@nongnu.org; Wed, 01 Jul 2009 14:36:29 -0400
Received: by ewy7 with SMTP id 7so1244717ewy.34
	for <qemu-devel@nongnu.org>; Wed, 01 Jul 2009 11:36:28 -0700 (PDT)
Message-ID: <4A4BACA7.5050406@codemonkey.ws>
Date: Wed, 01 Jul 2009 13:36:23 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 0/2] Tunnel character device data over VNC
	(v1)
References: <20090701162114.GB24296@redhat.com>
In-Reply-To: <20090701162114.GB24296@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org

Daniel P. Berrange wrote:
> The following two patches make it possible to tunnel character devices
> over VNC, using a new VNC extension. This is motivated by the existing
> QEMU support for tunnelling audio streams over VNC, and the code follows
> a very similar design.  The key requirement here is that it should not
> be neccessary to specifically configure each character device to make
> it available via VNC. The admin should be able to configure the char
> devices with all current available backends (file, pty, null, tcp, udp,
> unix, etc), and regardless of this config be able to snoop on data from
> any active VNC client on demand.
>   

Shouldn't it just be the character devices put on vc's?

Does snooping imply read-only?  That would be pretty unfortunate.

Regards,

Anthony Liguori