From: Anthony Liguori <aliguori@us.ibm.com>
To: Masami Watanabe <masami.watanabe@jp.fujitsu.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.xensource.com,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [PATCH][Take 3] VNC authentification
Date: Tue, 03 Oct 2006 12:56:31 -0500 [thread overview]
Message-ID: <4522A44F.1020700@us.ibm.com> (raw)
In-Reply-To: <JZ200610040108511.216281@jp.fujitsu.com>
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.
There was just a very high profile RealVNC vulnerability that was due to
improper authtype handling. It's very important we do this right so we
don't duplicate this bug.
Regards,
Anthony Liguori
> + /* Send Challenge */
> + make_challenge(challenge, AUTHCHALLENGESIZE);
> + vnc_write(vs, challenge, AUTHCHALLENGESIZE);
> + vnc_flush(vs);
> +
> + /* Read Responce */
> + vnc_read_when(vs, protocol_response, AUTHCHALLENGESIZE);
> + }
> +
> + return 0;
> +}
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2006-10-03 17:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 18:23 Individual passwords for guest VNC servers ? Ian Pratt
2006-09-28 1:01 ` Masami Watanabe
2006-09-29 8:47 ` [PATCH][Take 2] VNC authentification Masami Watanabe
2006-09-29 14:01 ` Anthony Liguori
2006-09-30 18:47 ` 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 2:04 ` Masami Watanabe
2006-10-03 16:08 ` [PATCH][Take 3] " Masami Watanabe
2006-10-03 17:56 ` Anthony Liguori [this message]
2006-10-03 18:06 ` Daniel P. Berrange
2006-10-03 18:49 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 23:24 Masami Watanabe
2006-10-04 23:42 ` Daniel P. Berrange
2006-10-05 0:56 ` 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=4522A44F.1020700@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=berrange@redhat.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.