From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Mt0Ov-0002lG-0Y
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 10:43:29 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Mt0Op-0002iw-PA
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 10:43:28 -0400
Received: from [199.232.76.173] (port=44817 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Mt0Op-0002it-IM
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 10:43:23 -0400
Received: from mail-bw0-f211.google.com ([209.85.218.211]:42411)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1Mt0Op-0006Db-1u
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 10:43:23 -0400
Received: by bwz7 with SMTP id 7so547743bwz.34
	for <qemu-devel@nongnu.org>; Wed, 30 Sep 2009 07:43:21 -0700 (PDT)
Message-ID: <4AC36E81.901@codemonkey.ws>
Date: Wed, 30 Sep 2009 09:43:13 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] let management expire vnc password
References: <1253609255-13016-1-git-send-email-danken@redhat.com>
	<4AC361E8.6060907@codemonkey.ws> <20090930140312.GB5408@redhat.com>
In-Reply-To: <20090930140312.GB5408@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: Dan Kenigsberg <danken@redhat.com>
Cc: qemu-devel@nongnu.org

Dan Kenigsberg wrote:
> On Wed, Sep 30, 2009 at 08:49:28AM -0500, Anthony Liguori wrote:
>   
>> Dan Kenigsberg wrote:
>>     
>>> After a client connects to vnc server, management may wish to expire the
>>> vnc password, so that an attacker has less time to break into the vm.
>>>   
>>>       
>> I don't understand what the use-case for this is.
>>
>> You want to basically lock out any new clients?  Can't you just set the  
>> password to something random?
>>     
>
> Yes, and actually that's what we currently do. But having a random
> password still opens a crack for guessing it.
>   

Is the requirement, prevent future clients from connecting to the vnc 
server?  Essentially, disabling the vnc server?

Could we do something more direct like add a 'vnc off' monitor command?  
The nice thing about this approach is that we could add a flag to 
disconnect all connected clients since someone else wanted that feature 
in the past.

Can you explain the rationale for doing this though in a management 
tool?  I'd like to better understand what sort of policy you're trying 
to enforce.

Regards,

Anthony Liguori