Date: Sun, 3 Jan 2010 14:31:46 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: "Karl J. Runge" <runge@karlrunge.com> Cc: freebsd-questions@freebsd.org Subject: Re: Remote assistance for X Message-ID: <alpine.BSF.2.00.1001031430590.1129@wonkity.com> In-Reply-To: <E1NREli-0001Wq-00@haystack.runge.home> References: <E1NREli-0001Wq-00@haystack.runge.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2 Jan 2010, Karl J. Runge wrote: > On Sat, 2 Jan 2010, Warren Block <wblock@wonkity.com> wrote: >> >> Proto: RFB 003.008 >> >> Connected to RFB server, using protocol version 3.8 >> Enabling TightVNC protocol extensions >> Security-Type: 16 (rfbSecTypeTight) >> No authentication needed >> >> Desktop name "" >> ... >> ...and that's it. The TightVNC server shows it's connected, and the >> ssvncviewer console is still busy. But no graphic window. ^C on the >> ssvncviewer window and the TightVNC server beeps and disconnects. >> That's TightVNC 1.3.10 on Vista and ssvnc-1.0.22_1 on FreeBSD. > > This is a bug in ssvncviewer that I will fix in the next release (1.0.26) > > It has to do with the (silly, IMHO) TightVNC security type rfbSecTypeTight > (that has nothing to do with security or encryption; it is used to enable > other features!) > > I believe a workaround for you will be: > > ssvncviewer -listen -rfbversion 3.7 > > this reverts to the previous protocol version where there is no issue. Confirmed, that works fine with TightVNC servers from both of the Windows systems. Thanks! -Warren Block * Rapid City, South Dakota USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1001031430590.1129>