From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HJEEG-0006xg-UM for qemu-devel@nongnu.org; Mon, 19 Feb 2007 14:31:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HJEEE-0006xU-Ed for qemu-devel@nongnu.org; Mon, 19 Feb 2007 14:31:15 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HJEEE-0006xR-9q for qemu-devel@nongnu.org; Mon, 19 Feb 2007 14:31:14 -0500 Received: from vms048pub.verizon.net ([206.46.252.48]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HJEED-0000P8-Kk for qemu-devel@nongnu.org; Mon, 19 Feb 2007 14:31:13 -0500 Received: from [192.168.1.151] ([71.167.55.15]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JDQ005DY67L0Q80@vms048.mailsrvcs.net> for qemu-devel@nongnu.org; Mon, 19 Feb 2007 13:30:58 -0600 (CST) Date: Mon, 19 Feb 2007 14:29:51 -0500 From: Christopher Olsen Subject: Re: [Qemu-devel] QEMU: VNC In-reply-to: <20070219190929.GT31525@redhat.com> Message-id: <200702191429.52197.cwolsen@domainatlantic.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200702161402.23660.cwolsen@domainatlantic.com> <200702191241.54042.cwolsen@domainatlantic.com> <20070219190929.GT31525@redhat.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" , qemu-devel@nongnu.org On Monday 19 February 2007 14:09, Daniel P. Berrange wrote: > Guess you missed the 'unix' directory - I have compiled both server & > client of VeNCrypt on Linux no trouble. > > > I'm gathering the problem here is that VNC is spinning off in many > > directions... So any implementation on the QEMU side will of course > > marry it to a particular VNC branch or I had an alternative idea.. > > I think the crux of the matter is that RealVNC sell a commercial version > of VNC which offers real encryption. So I'm guessing that's why they've > never merged any of the patches to do TLS encryption in the open source > codebase. All the patches for VNC + TLS i've seen posted are iterations > of each other - VeNCrypt is the most complete implenentation of any of > them, so the one I'd go for out of the all the choices. > > Regards, > Dan. I will take some further investigation into VeNCrypt.. I may have looked over it too quickly. If it seams feasible then I will move forward with it later today provide that no wheels are in motion to this and/or there are no real objections to it. -Christopher -- Christopher Olsen cwolsen@domainatlantic.com Tel: 631-676-4877 Fax: 631-249-3036