From: Anthony Liguori <anthony@codemonkey.ws>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Luke-Jr <luke-jr@utopios.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU: VNC
Date: Thu, 22 Feb 2007 11:29:21 -0600 [thread overview]
Message-ID: <45DDD2F1.7070405@codemonkey.ws> (raw)
In-Reply-To: <Pine.LNX.4.63.0702221744140.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Thu, 22 Feb 2007, Anthony Liguori wrote:
>
>
>> Johannes Schindelin wrote:
>>
>>> On Thu, 22 Feb 2007, Luke-Jr wrote:
>>>
>>>
>>>> Yes. The authentication is not really secure. It only uses 16 bits if I
>>>> remember correctly, so even without access to <filename>, it can be
>>>> easily broken.
>>>>
>>>> The common practice is to block after 3 attempts, but there are ways
>>>> around that, too.
>>>>
>>>>
>
> [Why do you quote me as if Luke was quoted?]
>
Because thunderbird sucks and did it automagically.
>> For all practical purposes, it's a plain-text equivalent authentication
>> mechanism. However, it's widely supported, and provides a useful
>> feature so it's worth supporting.
>>
>
> This invariably leads to user confusion. ("But I _did_ use encryption?
> What do you mean, it is not encrypted, and the handshake is weak?")
>
I understand. The solution is education. The documentation for vnc
auth support should make it very clear that it's plain-text equivalent.
Regards,
Anthony Liguori
> Ciao,
> Dscho
>
> BTW Anothony, now that I already have you on the subject of VNC, do you
> have any plans on making the documentation on
> http://www.realvnc.com/docs/rfbproto.pdf a little more useful for the
> extensions you registered?
>
>
>
next prev parent reply other threads:[~2007-02-22 17:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 5:19 [Qemu-devel] QEMU: VNC Luke-Jr
2007-02-22 16:22 ` Johannes Schindelin
2007-02-22 16:35 ` Anthony Liguori
2007-02-22 16:39 ` Christopher Olsen
2007-02-22 17:18 ` Johannes Schindelin
2007-02-22 17:29 ` Anthony Liguori [this message]
2007-02-22 17:35 ` Johannes Schindelin
2007-02-22 17:55 ` Leonardo Reiter
[not found] ` <200702221044.48581.luke@dashjr.org>
2007-02-22 17:27 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2007-02-16 19:02 Christopher Olsen
2007-02-16 20:57 ` Anthony Liguori
2007-02-18 20:36 ` Christopher Olsen
2007-02-18 23:08 ` Anthony Liguori
2007-02-18 23:53 ` Christopher Olsen
2007-02-19 0:14 ` Johannes Schindelin
2007-02-19 0:30 ` Christopher Olsen
2007-02-19 0:41 ` Johannes Schindelin
2007-02-19 2:01 ` Anthony Liguori
2007-02-19 2:11 ` Johannes Schindelin
2007-02-19 2:48 ` Anthony Liguori
2007-02-19 12:19 ` Christopher Olsen
2007-02-19 14:53 ` Johannes Schindelin
2007-02-19 17:16 ` Christopher Olsen
2007-02-19 17:30 ` Daniel P. Berrange
2007-02-19 17:41 ` Christopher Olsen
2007-02-19 19:09 ` Daniel P. Berrange
2007-02-19 19:29 ` Christopher Olsen
2007-02-19 22:52 ` Fabrice Bellard
2007-02-19 23:37 ` Christopher Olsen
2007-02-20 0:36 ` Daniel P. Berrange
2007-02-20 0:45 ` Anthony Liguori
2007-02-20 0:53 ` Christopher Olsen
2007-02-20 1:05 ` Daniel P. Berrange
2007-02-20 1:11 ` Johannes Schindelin
2007-02-20 1:18 ` Christopher Olsen
2007-02-20 19:46 ` Joe Batt
2007-02-19 23:58 ` Johannes Schindelin
2007-02-19 0:11 ` Johannes Schindelin
2007-02-19 0:25 ` Christopher Olsen
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=45DDD2F1.7070405@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Johannes.Schindelin@gmx.de \
--cc=luke-jr@utopios.org \
--cc=qemu-devel@nongnu.org \
/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.