Date: Sat, 02 Jan 2010 18:11:30 -0500 From: "Karl J. Runge" <runge@karlrunge.com> To: wblock@wonkity.com, runge@karlrunge.com Cc: freebsd-questions@freebsd.org Subject: Re: Remote assistance for X Message-ID: <E1NRD86-0007sp-00@haystack.runge.home> In-Reply-To: Mail from 'Warren Block <wblock@wonkity.com>' dated: Fri, 1 Jan 2010 22:58:47 -0700 (MST)
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 1 Jan 2010, Warren Block <wblock@wonkity.com> wrote: > [SSL mode for x11vnc] > > I've tried it now and it does just what is needed for my setup! Very good. > Finally, a little feedback: > > On a Windows Vista system, AVG screamed that the netcat.exe from > ssvnc_windows_only-1.0.25.zip was a virus (don't think it is, just > mentioning it). Yes, that is for the little used port-knocking feature (you can delete it if it causes a persistant annoyance.) AV software tends to have a knee-jerk reaction to netcat because it is often in a rootkit. OTOH on Unix netcat/nc is often installed by default (and so SSVNC uses the system one there.) I don't feel like writing C program for Windows to do what I need from netcat.exe only to avoid the AV triggers. > The TightVNC server on that Vista machine will connect with the > FreeBSD ssvncviewer, and the ssvncviewer console window shows status > information, but no graphic window opens on the FreeBSD system. Could you show me (via this thread or private email) the ssvncviewer console window printout for when this happens? I might spot a problem. Please include all of the output from the very beginning. (BTW, if you don't know how to scroll or select all of the text in xterm feel free to ask me.) > The FreeBSD TightVNC vncviewer opens a window but has real trouble > keeping the display updated, no doubt due to Vista. Finally, the > UltraVNC server with special Vista video drivers works usably with > ssvncviewer. I've seen things like this. > Can SSL be used with a Windows VNC server? Yes. In a SSVNC Windows bundle look for an the the stunnel example provided in: Windows/util/stunnel-server.conf You run stunnel.exe on that conf file (modified to your needs), and the traffic goes thru stunnel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1NRD86-0007sp-00>