From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LfMpy-0005OK-7B for qemu-devel@nongnu.org; Thu, 05 Mar 2009 18:18:46 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LfMpw-0005ND-E2 for qemu-devel@nongnu.org; Thu, 05 Mar 2009 18:18:45 -0500 Received: from [199.232.76.173] (port=37941 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LfMpw-0005N9-9r for qemu-devel@nongnu.org; Thu, 05 Mar 2009 18:18:44 -0500 Received: from phong.sigbus.net ([65.49.35.42]:53587) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LfMpw-0007CX-1u for qemu-devel@nongnu.org; Thu, 05 Mar 2009 18:18:44 -0500 Received: from [192.168.0.3] (c-71-202-202-194.hsd1.ca.comcast.net [71.202.202.194]) by phong.sigbus.net (Postfix) with ESMTPSA id 0A27695C0B4 for ; Thu, 5 Mar 2009 15:18:42 -0800 (PST) Subject: Re: [Qemu-devel] [PATCH] support for unsetting the VNC password from the monitor. From: Nolan In-Reply-To: 49B035E4.1010403@us.ibm.com Content-Type: text/plain Date: Thu, 05 Mar 2009 15:18:41 -0800 Message-Id: <1236295121.7115.152.camel@voxel> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Anthony wrote: > Nolan wrote: > > Add monitor support for setting the VNC password to "", disabling VNC. > > > > The magic sentinel value is "<>" which is not a valid VNC > > password by virtue of being 9 characters long. > > That's a little too magical for me. If you want to disable VNC, can't > you just say change vnc none? If you start with "-vnc :0,password", you will have no password set (thus logins are disabled), but qemu is listening on the port (keeping it occupied). "vnc change none" will close the socket. The intent of "change vnc password <>" is to leave the socket open, but disallow logins until the password is reset. Basically the goal is to provide a way to get back into state we were in immediately after process start. This is currently possible with the interactive "change vnc password" command, but not possible with the non-interactive variant.