Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Tight Encoding in OSXvnc' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Tight Encoding in OSXvnc
Authored by: professor on May 02, '02 01:23:23AM


Mahmud Haque has added support for Tight Encoding to OSXvnc and has released his modifed version as OSXvnc 0.7.


With a client like Chicken of the VNC.app which supports Tight Encoding, this makes a huge difference in speed. Really, it's like night and day. Finally, I find VNC usable over the internet (as opposed to on a LAN).


Great stuff!


P.S.: Elsewhere I gave instructions for streamlining the use of VNC over an SSH tunnel. One point I'd like to add to that. If you intend only to access the VNC server via an SSH tunnel, then you can go ahead and firewall access to ports 5900-5910 from the outside. When you connect via an SSH tunnel, you'll be connecting to localhost:5900 on the server machine, which is always allowed. But no one from the outside will be able to connect to your VNC server (unless they can SSH into your machine).


[ Reply to This | # ]