Bug 44811

Summary: [UPDATE] net/tightvnc
Product: Ports & Packages Reporter: molter <molter>
Component: Individual Port(s)Assignee: freebsd-ports (Nobody) <ports>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description molter 2002-11-01 18:20:00 UTC 
    The Xvnc server of port net/tightvnc fails to bind to an address when
    invoked with the -localhost or -interface options.
    
    This means that one cannot force the connections to the server to be
    only thru SSH port forwarding, degrading system security.
    
    Following easy patch fixes the problem. I also sent the patch to
    the tightvnc developers.

Fix: Put following patch in
    net/tightvnc/files/patch-Xvnc::programs::Xserver::hw::vnc::sockets.c

    You may also want to bump the revision number in the port Makefile.

How-To-Repeat: 
    [note that vncserver is a wrapper for Xvnc]

    $ vncserver -localhost
    or
    $ vncserver -interface <ipaddress>
Comment 1 Patrick Li freebsd_committer freebsd_triage 2002-11-02 18:32:09 UTC 
State Changed
From-To: open->closed

Committed, Thanks!