On Wed, Nov 30, 2011 at 11:45 AM, Dan Garton <dan.gar...@gmail.com> wrote:
>
> But I can't get it to connect to TigerVNC server running with
> SecurityType=TLSVnc.
>
> The noVNC developer tells me that *"The problem is that your VNC server
> is only configured to allow VeNCrypt and noVNC only supports standard VNC
> auth (2)."*
> *
> *
> But surely TLSVnc _is_ standard authentication? (as in, VNCAuth +
> encryption ?)
>
I've noticed recently that both the Java client and Fltk viewers report
that the VeNCrypt SecType is being selected even when the server doesn't
offer it or even when it has been disabled altogether. I basically ported
what was in the C-code to the Java client so it's not surprising that they
would behave the same, but I haven't had a chance to dig into whether
something is really broken or it's just a bogus log message.
-brian
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
