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
You may also want to bump the revision number in the port Makefile.
[note that vncserver is a wrapper for Xvnc]
$ vncserver -localhost
$ vncserver -interface <ipaddress>