From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: Why Xen 3.1.0 disable the qemu control monitor Date: Tue, 12 Jun 2007 12:40:41 +0100 Message-ID: <20070612114041.GA3031@redhat.com> References: Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Steven Hu Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Jun 12, 2007 at 01:19:04PM +0800, Steven Hu wrote: > Hello, all > I found that in Xen 3.1.0 I can't press Ctrl+ALT+2 to open the console > of qemu to do some administration. The root cause is that the value of > "monitor_device " is "null" now. In Xen 3.0.4, the value is "vc". If > there is no control console, how can I add a usb device to the guest > OS. Could you guys tell me why we disable the console in Xen 3.1.0. > thank. It is a huge security hole if using the VNC server to access the guest console. Anyone who can access the VNC server would be able to trivially root the entire Dom0 host if the monitor is enabled. See CVE 2007 0998 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0998 Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|