From: Markus Armbruster <armbru@redhat.com>
To: Tim Hardeck <thardeck@suse.de>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH] vnc: Clean up vncws_send_handshake_response()
Date: Fri, 25 Jan 2013 10:23:06 +0100 [thread overview]
Message-ID: <87obgdaa6d.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1359104210.6884.5.camel@Thinktank.site> (Tim Hardeck's message of "Fri, 25 Jan 2013 09:56:50 +0100")
Tim Hardeck <thardeck@suse.de> writes:
> Hi Markus,
>
> thanks for your input.
>
> On Wed, 2013-01-23 at 18:16 +0100, Markus Armbruster wrote:
>> Use appropriate types, drop superfluous casts, use sizeof, don't
>> exploit that this particular call of gnutls_fingerprint() doesn't
>> change its last argument.
>
> your patch does work fine but if we expect gnutls_fingerprint to change
> the hash_size there has to be an additional check if the hash_size is
> bigger than SHA1_DIGEST_LEN.
>
> For example:
>
> diff --git a/ui/vnc-ws.c b/ui/vnc-ws.c
> index de7e74c..e64c895 100644
> --- a/ui/vnc-ws.c
> +++ b/ui/vnc-ws.c
> @@ -132,7 +132,7 @@ static void vncws_send_handshake_response(VncState
> *vs, const char* key)
> in.data = (void *)combined_key;
> in.size = WS_CLIENT_KEY_LEN + WS_GUID_LEN;
> if (gnutls_fingerprint(GNUTLS_DIG_SHA1, &in, hash, &hash_size)
> - == GNUTLS_E_SUCCESS) {
> + == GNUTLS_E_SUCCESS && hash_size <= SHA1_DIGEST_LEN) {
> accept = g_base64_encode(hash, hash_size);
> }
> if (accept == NULL) {
Makes sense. I'll respin. Thanks!
prev parent reply other threads:[~2013-01-25 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:16 [Qemu-trivial] [PATCH] vnc: Clean up vncws_send_handshake_response() Markus Armbruster
2013-01-24 15:51 ` Tim Hardeck
2013-01-25 8:56 ` Tim Hardeck
2013-01-25 9:23 ` Markus Armbruster [this message]
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=87obgdaa6d.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thardeck@suse.de \
/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.