From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LYpN2-0005U7-3O for qemu-devel@nongnu.org; Sun, 15 Feb 2009 17:21:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LYpN0-0005Tm-Gl for qemu-devel@nongnu.org; Sun, 15 Feb 2009 17:21:51 -0500 Received: from [199.232.76.173] (port=36904 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LYpN0-0005Tg-DR for qemu-devel@nongnu.org; Sun, 15 Feb 2009 17:21:50 -0500 Received: from smtprelay0218.hostedemail.com ([216.40.44.218]:36890 helo=smtprelay.hostedemail.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LYpN0-0006k1-4p for qemu-devel@nongnu.org; Sun, 15 Feb 2009 17:21:50 -0500 Received: from filter.hostedemail.com (ff-bigip1 [10.5.19.254]) by smtprelay03.hostedemail.com (Postfix) with SMTP id 2973C2350E12 for ; Sun, 15 Feb 2009 22:21:49 +0000 (UTC) Received: from [192.168.2.184] (cpe-66-66-167-50.rochester.res.rr.com [66.66.167.50]) (Authenticated sender: kressb@moose.net) by omf04.hostedemail.com (Postfix) with ESMTP for ; Sun, 15 Feb 2009 22:21:48 +0000 (UTC) Message-ID: <4998957B.8000807@moose.net> Date: Sun, 15 Feb 2009 17:21:47 -0500 From: Brian Kress MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Support multiple VNC clients References: <4995CECB.1070401@moose.net> <20090215113500.GD4795@redhat.com> <004e01c98fb7$68673070$39359150$@com> In-Reply-To: <004e01c98fb7$68673070$39359150$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 Itamar Heim wrote: >> From: qemu-devel-bounces+iheim=redhat.com@nongnu.org [mailto:qemu-devel- >> > ... > >> Perhaps also add a -vnc command line flag to let us control policy for >> multiple clients interactions ? eg some policies I think of >> >> - Single client, new clients dropped >> - Single client, original client dropped >> - Many clients, first full access, others view only >> - Many clients, all full access >> > [IH] also - how does one specify the password for a specific vnc via the > monitor? > The password (as well as all the other authentication parameters) apply to the display, not a specific client. Even with this patch you still only have one vnc display, so you change the password for that display the same way you did before this patch. -Brian