From owner-freebsd-questions@FreeBSD.ORG Sun Jan 3 21:31:48 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 162B4106566B for ; Sun, 3 Jan 2010 21:31:48 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id C2E2C8FC0A for ; Sun, 3 Jan 2010 21:31:47 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o03LVksd001133; Sun, 3 Jan 2010 14:31:46 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id o03LVkYQ001130; Sun, 3 Jan 2010 14:31:46 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 3 Jan 2010 14:31:46 -0700 (MST) From: Warren Block To: "Karl J. Runge" In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (wonkity.com [127.0.0.1]); Sun, 03 Jan 2010 14:31:46 -0700 (MST) Cc: freebsd-questions@freebsd.org Subject: Re: Remote assistance for X X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2010 21:31:48 -0000 On Sat, 2 Jan 2010, Karl J. Runge wrote: > On Sat, 2 Jan 2010, Warren Block 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