All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Masami Watanabe <masami.watanabe@jp.fujitsu.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	Anthony Liguori <aliguori@us.ibm.com>,
	xen-devel@lists.xensource.com
Subject: Re: [PATCH][Take 3] VNC authentification
Date: Thu, 5 Oct 2006 00:42:59 +0100	[thread overview]
Message-ID: <20061004234259.GB8593@redhat.com> (raw)
In-Reply-To: <JG200610050824484.801156@jp.fujitsu.com>

On Thu, Oct 05, 2006 at 08:24:48AM +0900, Masami Watanabe wrote:
> Hi all,
> 
> My understanding of main_loop of vl.c was insufficient. 
> I have improved the point to have set the handler doubly.
> The protocol of protocol 3.3 and (UltraVNC's ?)3.4 did not actually
> need the response of the authentification type from the client.
> Therefore, protocol_authtype operated without being called.
> 
> I will post the take 4 patch after this.
> 
> The patch has limited  RFB protocol to 3.3 and 3.4.
> I also think that it should support 3.8 without being support 3.3 in
> the future.
> 
> However, Leaving like non authetification is not good.
> You will think the patch to be provisional action till then.

If you get the basic auth working correctly with RFB protocol 3.3,
IMHO, that will be sufficient for an initial commit to xen-unstable
because it is such a step forward over the current 'no auth'
situation. We can consider extending it to cover protocol 3.8
at a later date when we decide which other auth meachanisms
are particularly important.

> Another.
> ill the RFB protocol still keep evolving in the future?

Its been on 3.8 for a while & clients will negotiate a mutually
supported protocol version with the server, so no need to worry
about future protocol versions at this time.

Regards,
Dan
--
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2006-10-04 23:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 23:24 [PATCH][Take 3] VNC authentification Masami Watanabe
2006-10-04 23:42 ` Daniel P. Berrange [this message]
2006-10-05  0:56 ` Anthony Liguori
2006-10-05  1:28   ` [PATCH][Take 4] " Masami Watanabe
2006-10-10 13:11     ` Daniel P. Berrange
2006-10-10 14:04       ` Anthony Liguori
2006-10-25 18:00         ` Daniel P. Berrange
2006-10-25 20:43           ` Keir Fraser
2006-10-25 21:23             ` Daniel P. Berrange
  -- strict thread matches above, loose matches on Subject: below --
2006-09-26 18:23 Individual passwords for guest VNC servers ? Ian Pratt
2006-09-29  8:47 ` [PATCH][Take 2] VNC authentification Masami Watanabe
2006-09-29 22:11   ` Daniel P. Berrange
2006-09-30 18:53     ` Masami Watanabe
2006-10-02 16:22       ` Daniel P. Berrange
2006-10-02 17:24         ` Anthony Liguori
2006-10-02 18:12           ` Daniel P. Berrange
2006-10-02 19:15             ` Ian Pratt
2006-10-03 16:08               ` [PATCH][Take 3] " Masami Watanabe
2006-10-03 17:56                 ` Anthony Liguori
2006-10-03 18:06                   ` Daniel P. Berrange
2006-10-03 18:49                     ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061004234259.GB8593@redhat.com \
    --to=berrange@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=masami.watanabe@jp.fujitsu.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.