From owner-freebsd-questions@FreeBSD.ORG Sun Jan 3 00:56:56 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 32452106568B for ; Sun, 3 Jan 2010 00:56:56 +0000 (UTC) (envelope-from runge@karlrunge.com) Received: from holmes.jfku.edu (holmes.jfku.edu [66.117.151.7]) by mx1.freebsd.org (Postfix) with ESMTP id 031368FC08 for ; Sun, 3 Jan 2010 00:56:55 +0000 (UTC) Received: from haystack.runge.home (runge@localhost [127.0.0.1]) by holmes.jfku.edu (8.9.3p3.JFKU/8.9.1) with ESMTP id QAA21595; Sat, 2 Jan 2010 16:56:30 -0800 Received: from runge by haystack.runge.home with local (Exim 3.36 #1 (Debian)) id 1NREli-0001Wq-00; Sat, 02 Jan 2010 19:56:30 -0500 To: wblock@wonkity.com, runge@karlrunge.com In-Reply-To: Mail from 'Warren Block ' dated: Sat, 2 Jan 2010 16:59:03 -0700 (MST) From: "Karl J. Runge" Message-Id: Date: Sat, 02 Jan 2010 19:56:30 -0500 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 00:56:56 -0000 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.