From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [PATCH][Take 3] VNC authentification
Date: Tue, 03 Oct 2006 13:49:37 -0500
Message-ID: <4522B0C1.60902@us.ibm.com>
References: <3AAA99889D105740BE010EB6D5A5A3B202A3D2@paddington.ad.cl.cam.ac.uk>	<JX200609291747343.1765484@jp.fujitsu.com>	<20060929221145.GE8564@redhat.com>	<JH200610010353334.2150046@jp.fujitsu.com>	<20061002162232.GB1730@redhat.com>
	<45214B54.8060805@us.ibm.com>	<20061002181231.GC1730@redhat.com>	<3AAA99889D105740BE010EB6D5A5A3B202A4F0@paddington.ad.cl.cam.ac.uk>	<JZ200610040108511.216281@jp.fujitsu.com>	<4522A44F.1020700@us.ibm.com>
	<20061003180611.GB29356@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20061003180611.GB29356@redhat.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com, Masami Watanabe <masami.watanabe@jp.fujitsu.com>
List-Id: xen-devel@lists.xenproject.org

Daniel P. Berrange wrote:
> On Tue, Oct 03, 2006 at 12:56:31PM -0500, Anthony Liguori wrote:
>   
>> Masami Watanabe wrote:
>>     
>>> +static int vnc_auth(VncState *vs)
>>> +{
>>> +    extern char vncpasswd[64];
>>> +    extern unsigned char challenge[AUTHCHALLENGESIZE];
>>> +
>>> +    if (*vncpasswd == '\0') {
>>> +	/* AuthType is None */
>>> +	vnc_write_u32(vs, 1);
>>> +	vnc_flush(vs);
>>> +	vnc_read_when(vs, protocol_client_init, 1);
>>> +    } else {
>>> +	/* AuthType is VncAuth */
>>> +	vnc_write_u32(vs, 2);
>>> +	vnc_flush(vs);
>>> +
>>> +	/* Read AuthType */
>>> +	vnc_read_when(vs, protocol_authtype, 1);
>>>  
>>>       
>> As I mentioned before, you cannot have to vnc_read_when()'s execution 
>> path without returning the the mainloop.
>>
>> protocol_authtype() cannot possibly be invoked.  If the code is working 
>> now, it's pure luck.
>>     
>
> Yeah, the impl of protocol_authtype() in there is a no-op too - it should
> be rejecting auth types which aren't supported, even if it was being invoked.
> With the code as it is, protocol_authtype never runs & the server starts
> doing VNCAuth regardless of what the client says it wants to do, which is
> clearly not correct.
>   

Another thing to keep in mind, is that the reason I did 3.3 instead of 
3.8 is that I knew there was only one auth type we would be supporting.  
If we do support multiple auth types, we really ought to move to using 
the 3.8 protocol since that provides a negotiation mechanism.

Regards,

Anthony Liguori

> Dan.
>