Bug 44811 - [UPDATE] net/tightvnc
Summary: [UPDATE] net/tightvnc
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-01 18:20 UTC by molter
Modified: 2002-11-02 18:32 UTC (History)
0 users

See Also:

Attachments
file.diff (487 bytes, patch)
2002-11-01 18:20 UTC, molter 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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!