.
.
(To Downloads) (To Quick Start)
The Enhanced TightVNC Viewer,
SSVNC, adds encryption security to VNC connections.
The package provides a GUI for Windows, Mac OS X, and Unix that automatically starts up an STUNNEL SSL tunnel for SSL or ssh/plink for SSH connections to any VNC server, such as x11vnc, and then launches the VNC Viewer to use the encrypted tunnel.
The x11vnc server has built-in SSL support, however SSVNC can make SSL encrypted VNC connections to any VNC Server if they are running an SSL tunnel, such as STUNNEL or socat, at their end. SSVNC's SSH tunnel will work to any VNC Server host running sshd that you can log into.
The Enhanced TightVNC Viewer package started as a project to add some patches to the long neglected Unix TightVNC Viewer. However, now the front-end GUI, encryption, and wrapper scripts features possibly outweigh the Unix TightVNC Viewer improvements (see the lists below to compare).
The SSVNC Unix vncviewer can also be run without the SSVNC
encryption GUI as an enhanced replacement for the xvncviewer,
xtightvncviewer, etc., viewers.
In addition to normal SSL, SSVNC also supports the VeNCrypt SSL/TLS and Vino/ANONTLS encryption extensions to VNC on Unix, Mac OS X, and Windows. Via the provided SSVNC VeNCrypt bridge, VeNCrypt and ANONTLS encryption also works with any third party VNC Viewer (e.g. RealVNC, TightVNC, UltraVNC, etc...) you select via 'Change VNC Viewer'.
The short name for this project is "ssvnc" for SSL/SSH VNC Viewer. This is the name of the command to start it.
There is a simplified SSH-Only mode
(sshvnc). And an even more simplified Terminal-Services mode (tsvnc) for use
with x11vnc on the remote side.
The tool has many additional features; see the descriptions below.
It is a self-contained bundle, you could carry it around on, say, a USB memory stick / flash drive for secure VNC viewing from almost any machine, Unix, Mac OS X, and Windows (and if you create a directory named "Home" in the toplevel ssvnc directory on the drive your VNC profiles and certs will be kept there as well). For Unix, there is also a conventional source tarball to build and install in the normal way and not use a pre-built bundle.
Please read this information on using SSVNC on workstations with Untrusted Local Users.
Wrapper scripts and a tcl/tk GUI were written to create these features for Unix, Mac OS X, and Windows:
repeater://host:port+ID:1234). Multiple proxies may be chained together (3 max).avahi-browse or dns-sd program is available and in your PATH.ssh -D) for servers like x11vnc that print out PORT= at startup.x11vnc -unixpw" type login dialogs.-alpha option)-unixpw ..." for use with "x11vnc -unixpw" type login dialogs.java must be in $PATH). Note that the x11vnc server also supports UltraVNC file transfer.-repeater option).x11vnc -enc blowfish:./my.keyhostname:display one can also supply "exec=command args..." to connect the viewer to the stdio of an external command (e.g. stunnel or socat) rather than using a TCP/IP socket. Unix domain sockets, e.g. /path/to/unix/socket, and a previously opened file descriptor fd=0, work too.-acceptpopup.) The extra info provided by UltraVNC Single Click reverse connections is also supported (-acceptpopupsc)-use64/-bgr222, -use8/-bgr111)-16bpp/-bgr565)-ncache method use the cropping option -ycrop n. This will "hide" the large pixel buffer cache below the actual display. Set to the actual height or use -1 for autodetection (also, tall screens, H > 2*W, are autodetected by default).-sbwidth n, the default is very thin, 2 pixels, for less distracting -ycrop usage. localhost:0 connections is not raw encoding since same-machine connections are pretty rare. Default assumes you are using a SSL or SSH tunnel. Use -rawlocal to revert.-grab/-graball option).-popupfix option).ssvncviewer supports IPv6 natively (no helpers needed.) The list of 3rd party software bundled in the archive files:
ssvnc straight from its directory.
Alternatively, on Unix you can use the conventional source tarball.
You can read all of the SSVNC GUI's Online Help Text here.
The bundle unpacks a directory/folder named: ssvnc.
It contains these programs to launch the GUI:
Windows/ssvnc.exe for Windows MacOSX/ssvnc for Mac OS X Unix/ssvnc for Unix(the Mac OS X and Unix launchers are simply links to the
bin directory).
See the README for more information.
The SSH-Only mode launcher program has name sshvnc.
The Terminal Services mode launcher program (assumes x11vnc 0.8.4
or later and Xvfb installed on the server machine) has name tsvnc.
The Viewer SSL support is done via a wrapper script
(bin/ssvnc_cmd that calls bin/util/ss_vncviewer)
that starts up the STUNNEL tunnel first and then starts the TightVNC
viewer pointed at that tunnel. The bin/ssvnc
program is a GUI front-end to that script. See
this FAQ for more details on
SSL tunnelling. In SSH connection mode, the wrappers start up SSH appropriately.
One user on Windows created a BAT file to launch SSVNC and needed to do this to get the Home directory correct:
cd \ssvnc\Windows start \ssvnc\Windows\ssvnc.exe(an optional profile name can be supplied to the ssvnc.exe line)
WARNING: if you use ssvnc from an "Internet Cafe", i.e. some untrusted computer, please be aware that someone may have set up that machine to be capturing your keystrokes, etc.
These also work: "sshvnc myprofile" and
"sshvnc user@hostname".
To switch from the regular SSVNC mode, click "SSH-Only Mode" under Options.
This mode is less distracting if you never plan to use SSL, manage certificates, etc.
These also work: "tsvnc myprofile" and
"tsvnc user@hostname".
To switch from the regular SSVNC mode, click "Terminal Services" under Options.
This mode requires x11vnc (0.9.3 or later)
installed on the remote machine to find, create, and manage the user
sessions. SSH is used to create the encrypted and authenticated tunnel.
The Xvfb (virtual framebuffer X server) program must also be
installed on the remote system. However tsvnc will
also connect to a real X session (i.e. on the physical
hardware) if you are already logged into the X session; this is a useful
access mode and does not require Xvfb on the remote system.
This mode should be very easy for beginner users to understand and
use. On the remote end you only need to have x11vnc and
Xvfb available in $PATH, and on the local end you just run
something like:
tsvnc myname@myhost.com(or start up the
tsvnc GUI first and then enter myname@myhost.com
and press "Connect").
Normally the Terminal Services sessions created are virtual (RAM-only)
ones (e.g. Xvfb, Xdummy, or Xvnc),
however a nice feature is if you have a regular X session
(i.e displaying on the physical hardware) on the remote machine that
you are ALREADY logged into, then the x11vnc run from
tsvnc will find it for you as well.
Also, there is setting "X Login" under Advanced Options that allows you to attach to a real X server with no one logged in yet (i.e. XDM/GDM/KDM Login Greeter screen) as long as you have sudo(1) permission on the remote machine.
Nice features to soon to be added to the tsvnc mode are easy CUPS printing (working fairly well) and Sound redirection (needs much work) of the Terminal Services Desktop session. It is easier in tsvnc mode because the entire desktop session can be started with the correct environment. ssvnc tries to handle the general case of an already started desktop and that is more difficult.
Proxies:
Web proxies, SOCKS proxies, and the UltraVNC repeater proxy are supported
to allow the SSVNC connection to go through the proxy to the otherwise
unreachable VNC Server. SSH gateway machines can be used in the same
way. Read more about SSVNC proxy support here.
There is also code to detect the display of the regular Unix vncserver(1). It extracts the display (and hence port) from the lines "New 'X' desktop is hostname:4" and also "VNC server is already running as :4". So you can use something like:
PORT= vncserver; sleep 15
or: PORT= vncserver :4; sleep 15
the latter is preferred because when you reconnect with it will
find the already running one. The former one will keep creating
new X sessions if called repeatedly.
If you use PORT= on Windows, a large random port is
selected instead and the
-rfbport
option is passed to x11vnc (it does not work with vncserver).
Patches for Unix Tightvnc viewer:
The rfbNewFBSize support allows the enhanced TightVNC
Unix viewer to resize when the server does (e.g. "x11vnc -R scale=3/4"
remote control command).
The cursor alphablending is described here.
The RealVNC ZRLE encoding is supported, in addition to some low colors modes (16bpp and 8bpp at 256, 64, and even 8 colors, for use on very slow connections). Greyscales are also enabled for the low color modes.
The Popup menu (F8) is enhanced with the ability to change many things on the fly. F9 is added as a shortcut to toggle FullScreen mode.
Client Side Caching:
The x11vnc
client-side caching
is handled nicely by this viewer. The very large pixel cache below
the actual display in this caching method is distracting. Our Unix
VNC viewer will automatically try to autodetect the actual display
height if the framebuffer is very tall (more than twice as high as it
is wide). One can also set the height to the known value via
-ycrop n, or use -ycrop -1 to force autodection.
In fullscreen mode one is not possible to scroll down to the pixel cache
region. In non-fullscreen mode the window manager frame is "shrink-wrapped"
around the actual screen display. You can still scroll down to the
pixel cache region. The scrollbars are set to be very thin (2 pixels)
to be less distracting. Use the -sbwidth n to make them wider.
Probably nobody is interested in the
grabserver patch for old window managers
when the viewer is in fullscreen mode...
This and some other unfixed bugs have been fixed in our patches
(fullscreen toggle works with KDE, -x11cursor has been
fixed, and the dot cursor has been made smaller).
From the -help output:
SSVNC Viewer (based on TightVNC viewer version 1.3.9)
Usage: vncviewer [<OPTIONS>] [<HOST>][:<DISPLAY#>]
vncviewer [<OPTIONS>] [<HOST>][::<PORT#>]
vncviewer [<OPTIONS>] exec=[CMD ARGS...]
vncviewer [<OPTIONS>] fd=n
vncviewer [<OPTIONS>] /path/to/unix/socket
vncviewer [<OPTIONS>] -listen [<DISPLAY#>]
vncviewer -help
<OPTIONS> are standard Xt options, or:
-via <GATEWAY>
-shared (set by default)
-noshared
-viewonly
-fullscreen
-noraiseonbeep
-passwd <PASSWD-FILENAME> (standard VNC authentication)
-user <USERNAME> (Unix login authentication)
-encodings <ENCODING-LIST> (e.g. "tight,copyrect")
-bgr233
-owncmap
-truecolour
-depth <DEPTH>
-compresslevel <COMPRESS-VALUE> (0..9: 0-fast, 9-best)
-quality <JPEG-QUALITY-VALUE> (0..9: 0-low, 9-high)
-nojpeg
-nocursorshape
-x11cursor
-autopass
Option names may be abbreviated, e.g. -bgr instead of -bgr233.
See the manual page for more information.
Enhanced TightVNC viewer (SSVNC) options:
URL http://www.karlrunge.com/x11vnc/ssvnc.html
Note: ZRLE and ZYWRLE encodings are now supported.
Note: F9 is shortcut to Toggle FullScreen mode.
Note: In -listen mode set the env var. SSVNC_MULTIPLE_LISTEN=1
to allow more than one incoming VNC server at a time.
This is the same as -multilisten described below. Set
SSVNC_MULTIPLE_LISTEN=MAX:n to allow no more than "n"
simultaneous reverse connections.
Note: If the host:port is specified as "exec=command args..."
then instead of making a TCP/IP socket connection to the
remote VNC server, "command args..." is executed and the
viewer is attached to its stdio. This enables tunnelling
established via an external command, e.g. an stunnel(8)
that does not involve a listening socket. This mode does
not work for -listen reverse connections.
If the host:port is specified as "fd=n" then it is assumed
n is an already opened file descriptor to the socket. (i.e
the parent did fork+exec)
If the host:port contains a '/' it is interpreted as a
unix-domain socket (AF_LOCAL insead of AF_INET)
-multilisten As in -listen (reverse connection listening) except
allow more than one incoming VNC server to be connected
at a time. The default for -listen of only one at a
time tries to play it safe by not allowing anyone on
the network to put (many) desktops on your screen over
a long window of time. Use -multilisten for no limit.
-acceptpopup In -listen (reverse connection listening) mode when
a reverse VNC connection comes in show a popup asking
whether to Accept or Reject the connection. The IP
address of the connecting host is shown. Same as
setting the env. var. SSVNC_ACCEPT_POPUP=1.
-acceptpopupsc As in -acceptpopup except assume UltraVNC Single
Click (SC) server. Retrieve User and ComputerName
info from UltraVNC Server and display in the Popup.
-use64 In -bgr233 mode, use 64 colors instead of 256.
-bgr222 Same as -use64.
-use8 In -bgr233 mode, use 8 colors instead of 256.
-bgr111 Same as -use8.
-16bpp If the vnc viewer X display is depth 24 at 32bpp
request a 16bpp format from the VNC server to cut
network traffic by up to 2X, then tranlate the
pixels to 32bpp locally.
-bgr565 Same as -16bpp.
-grey Use a grey scale for the 16- and 8-bpp modes.
-alpha Use alphablending transparency for local cursors
requires: x11vnc server, both client and server
must be 32bpp and same endianness.
-scale str Scale the desktop locally. The string "str" can
a floating point ratio, e.g. "0.9", or a fraction,
e.g. "3/4", or WxH, e.g. 1280x1024. Use "fit"
to fit in the current screen size. Use "auto" to
fit in the window size. "str" can also be set by
the env. var. SSVNC_SCALE.
If you observe mouse trail painting errors, enable
X11 Cursor mode (either via Popup or -x11cursor.)
Note that scaling is done in software and so can be
slow and requires more memory. Some speedup Tips:
ZRLE is faster than Tight in this mode. When
scaling is first detected, the encoding will
be automatically switched to ZRLE. Use the
Popup menu if you want to go back to Tight.
Set SSVNC_PRESERVE_ENCODING=1 to disable this.
Use a solid background on the remote side.
(e.g. manually or via x11vnc -solid ...)
If the remote server is x11vnc, try client
side caching: x11vnc -ncache 10 ...
-ycrop n Only show the top n rows of the framebuffer. For
use with x11vnc -ncache client caching option
to help "hide" the pixel cache region.
Use a negative value (e.g. -1) for autodetection.
Autodetection will always take place if the remote
fb height is more than 2 times the width.
-sbwidth n Scrollbar width for x11vnc -ncache mode (-ycrop),
default is very narrow: 2 pixels, it is narrow to
avoid distraction in -ycrop mode.
-nobell Disable bell.
-rawlocal Prefer raw encoding for localhost, default is
no, i.e. assumes you have a SSH tunnel instead.
-notty Try to avoid using the terminal for interactive
responses: use windows for messages and prompting
instead. Messages will also be printed to terminal.
-sendclipboard Send the X CLIPBOARD selection (i.e. Ctrl+C,
Ctrl+V) instead of the X PRIMARY selection (mouse
select and middle button paste.)
-sendalways Whenever the mouse enters the VNC viewer main
window, send the selection to the VNC server even if
it has not changed. This is like the Xt resource
translation SelectionToVNC(always)
-recvtext str When cut text is received from the VNC server,
ssvncviewer will set both the X PRIMARY and the
X CLIPBOARD local selections. To control which
is set, specify 'str' as 'primary', 'clipboard',
or 'both' (the default.)
-graball Grab the entire X server when in fullscreen mode,
needed by some old window managers like fvwm2.
-popupfix Warp the popup back to the pointer position,
needed by some old window managers like fvwm2.
-sendclipboard Send the X CLIPBOARD selection (i.e. Ctrl+C,
Ctrl+V) instead of the X PRIMARY selection (mouse
select and middle button paste.)
-sendalways Whenever the mouse enters the VNC viewer main
window, send the selection to the VNC server even if
it has not changed. This is like the Xt resource
translation SelectionToVNC(always)
-recvtext str When cut text is received from the VNC server,
ssvncviewer will set both the X PRIMARY and the
X CLIPBOARD local selections. To control which
is set, specify 'str' as 'primary', 'clipboard',
or 'both' (the default.)
-graball Grab the entire X server when in fullscreen mode,
needed by some old window managers like fvwm2.
-popupfix Warp the popup back to the pointer position,
needed by some old window managers like fvwm2.
-grabkbd Grab the X keyboard when in fullscreen mode,
needed by some window managers. Same as -grabkeyboard.
-grabkbd is the default, use -nograbkbd to disable.
-bs, -nobs Whether or not to use X server Backingstore for the
main viewer window. The default is to not, mainly
because most Linux, etc, systems X servers disable
*all* Backingstore by default. To re-enable it put
Option "Backingstore"
in the Device section of /etc/X11/xorg.conf.
In -bs mode with no X server backingstore, whenever an
area of the screen is re-exposed it must go out to the
VNC server to retrieve the pixels. This is too slow.
In -nobs mode, memory is allocated by the viewer to
provide its own backing of the main viewer window. This
actually makes some activities faster (changes in large
regions) but can appear to "flash" too much.
-noshm Disable use of MIT shared memory extension (not recommended)
-termchat Do the UltraVNC chat in the terminal vncviewer is in
instead of in an independent window.
-unixpw str Useful for logging into x11vnc in -unixpw mode. "str" is a
string that allows many ways to enter the Unix Username
and Unix Password. These characters: username, newline,
password, newline are sent to the VNC server after any VNC
authentication has taken place. Under x11vnc they are
used for the -unixpw login. Other VNC servers could do
something similar.
You can also indicate "str" via the environment
variable SSVNC_UNIXPW.
Note that the Escape key is actually sent first to tell
x11vnc to not echo the Unix Username back to the VNC
viewer. Set SSVNC_UNIXPW_NOESC=1 to override this.
If str is ".", then you are prompted at the command line
for the username and password in the normal way. If str is
"-" the stdin is read via getpass(3) for username@password.
Otherwise if str is a file, it is opened and the first line
read is taken as the Unix username and the 2nd as the
password. If str prefixed by "rm:" the file is removed
after reading. Otherwise, if str has a "@" character,
it is taken as username@password. Otherwise, the program
exits with an error. Got all that?
-repeater str This is for use with UltraVNC repeater proxy described
here: http://www.uvnc.com/addons/repeater.html. The "str"
is the ID string to be sent to the repeater. E.g. ID:1234
It can also be the hostname and port or display of the VNC
server, e.g. 12.34.56.78:0 or snoopy.com:1. Note that when
using -repeater, the host:dpy on the cmdline is the repeater
server, NOT the VNC server. The repeater will connect you.
Example: vncviewer ... -repeater ID:3333 repeat.host:5900
Example: vncviewer ... -repeater vhost:0 repeat.host:5900
Use, e.g., '-repeater SCIII=ID:3210' if the repeater is a
Single Click III (SSL) repeater (repeater_SSL.exe) and you
are passing the SSL part of the connection through stunnel,
socat, etc. This way the magic UltraVNC string 'testB'
needed to work with the repeater is sent to it.
-rfbversion str Set the advertised RFB version. E.g.: -rfbversion 3.6
For some servers, e.g. UltraVNC this needs to be done.
-ultradsm UltraVNC has symmetric private key encryption DSM plugins:
http://www.uvnc.com/features/encryption.html. It is assumed
you are using a unix program (e.g. our ultravnc_dsm_helper)
to encrypt and decrypt the UltraVNC DSM stream. IN ADDITION
TO THAT supply -ultradsm to tell THIS viewer to modify the
RFB data sent so as to work with the UltraVNC Server. For
some reason, each RFB msg type must be sent twice under DSM.
-mslogon user Use Windows MS Logon to an UltraVNC server. Supply the
username or "1" to be prompted. The default is to
autodetect the UltraVNC MS Logon server and prompt for
the username and password.
IMPORTANT NOTE: The UltraVNC MS-Logon Diffie-Hellman
exchange is very weak and can be brute forced to recover
your username and password in a few seconds of CPU time.
To be safe, be sure to use an additional encrypted tunnel
(e.g. SSL or SSH) for the entire VNC session.
-chatonly Try to be a client that only does UltraVNC text chat. This
mode is used by x11vnc to present a chat window on the
physical X11 console (i.e. chat with the person at the
display).
-env VAR=VALUE To save writing a shell script to set environment variables,
specify as many as you need on the command line. For
example, -env SSVNC_MULTIPLE_LISTEN=MAX:5 -env EDITOR=vi
-noipv6 Disable all IPv6 sockets. Same as VNCVIEWER_NO_IPV6=1.
-noipv4 Disable all IPv4 sockets. Same as VNCVIEWER_NO_IPV4=1.
-printres Print out the Ssvnc X resources (appdefaults) and then exit
You can save them to a file and customize them (e.g. the
keybindings and Popup menu) Then point to the file via
XENVIRONMENT or XAPPLRESDIR.
-pipeline Like TurboVNC, request the next framebuffer update as soon
as possible instead of waiting until the end of the current
framebuffer update coming in. Helps 'pipeline' the updates.
This is currently the default, use -nopipeline to disable.
-appshare Enable features for use with x11vnc's -appshare mode where
instead of sharing the full desktop only the application's
windows are shared. Viewer multilisten mode is used to
create the multiple windows: -multilisten is implied.
See 'x11vnc -appshare -help' more information on the mode.
Features enabled in the viewer under -appshare are:
Minimum extra text in the title, auto -ycrop is disabled,
x11vnc -remote_prefix X11VNC_APPSHARE_CMD: message channel,
x11vnc initial window position hints. See also Escape Keys
below for additional key and mouse bindings.
-escape str This sets the 'Escape Keys' modifier sequence and enables
escape keys mode. When the modifier keys escape sequence
is held down, the next keystroke is interpreted locally
to perform a special action instead of being sent to the
remote VNC server.
Use '-escape default' for the default modifier sequence.
(Unix: Alt_L,Super_L and MacOSX: Control_L,Meta_L)
Here are the 'Escape Keys: Help+Set' instructions from the Popup Menu:
Escape Keys: Enter a comma separated list of modifier keys to be the
'escape sequence'. When these keys are held down, the next keystroke is
interpreted locally to invoke a special action instead of being sent to
the remote VNC server. In other words, a set of 'Hot Keys'.
To enable or disable this, click on 'Escape Keys: Toggle' in the Popup.
Here is the list of hot-key mappings to special actions:
r: refresh desktop b: toggle bell c: toggle full-color
f: file transfer x: x11cursor z: toggle Tight/ZRLE
l: full screen g: graball e: escape keys dialog
s: scale dialog +: scale up (=) -: scale down (_)
t: text chat a: alphablend cursor
V: toggle viewonly Q: quit viewer 1 2 3 4 5 6: UltraVNC scale 1/n
Arrow keys: pan the viewport about 10% for each keypress.
PageUp / PageDown: pan the viewport by a screenful vertically.
Home / End: pan the viewport by a screenful horizontally.
KeyPad Arrow keys: pan the viewport by 1 pixel for each keypress.
Dragging the Mouse with Button1 pressed also pans the viewport.
Clicking Mouse Button3 brings up the Popup Menu.
The above mappings are *always* active in ViewOnly mode, unless you set the
Escape Keys value to 'never'.
If the Escape Keys value below is set to 'default' then a default list of
of modifier keys is used. For Unix it is: Alt_L,Super_L and for MacOSX it
is Control_L,Meta_L. Note: the Super_L key usually has a Windows(TM) Flag
on it. Also note the _L and _R mean the key is on the LEFT or RIGHT side
of the keyboard.
On Unix the default is Alt and Windows keys on Left side of keyboard.
On MacOSX the default is Control and Command keys on Left side of keyboard.
Example: Press and hold the Alt and Windows keys on the LEFT side of the
keyboard and then press 'c' to toggle the full-color state. Or press 't'
to toggle the ultravnc Text Chat window, etc.
To use something besides the default, supply a comma separated list (or a
single one) from: Shift_L Shift_R Control_L Control_R Alt_L Alt_R Meta_L
Meta_R Super_L Super_R Hyper_L Hyper_R or Mode_switch.
New Popup actions:
ViewOnly: ~ -viewonly
Disable Bell: ~ -nobell
Cursor Shape: ~ -nocursorshape
X11 Cursor: ~ -x11cursor
Cursor Alphablend: ~ -alpha
Toggle Tight/Hextile: ~ -encodings hextile...
Toggle Tight/ZRLE: ~ -encodings zrle...
Toggle ZRLE/ZYWRLE: ~ -encodings zywrle...
Quality Level ~ -quality (both Tight and ZYWRLE)
Compress Level ~ -compresslevel
Disable JPEG: ~ -nojpeg (Tight)
Pipeline Updates ~ -pipeline
Full Color as many colors as local screen allows.
Grey scale (16 & 8-bpp) ~ -grey, for low colors 16/8bpp modes only.
16 bit color (BGR565) ~ -16bpp / -bgr565
8 bit color (BGR233) ~ -bgr233
256 colors ~ -bgr233 default # of colors.
64 colors ~ -bgr222 / -use64
8 colors ~ -bgr111 / -use8
Scale Viewer ~ -scale
Escape Keys: Toggle ~ -escape
Escape Keys: Help+Set ~ -escape
Set Y Crop (y-max) ~ -ycrop
Set Scrollbar Width ~ -sbwidth
XGrabServer ~ -graball
UltraVNC Extensions:
Set 1/n Server Scale Ultravnc ext. Scale desktop by 1/n.
Text Chat Ultravnc ext. Do Text Chat.
File Transfer Ultravnc ext. File xfer via Java helper.
Single Window Ultravnc ext. Grab and view a single window.
(select then click on the window you want).
Disable Remote Input Ultravnc ext. Try to prevent input and
viewing of monitor at physical display.
Note: the Ultravnc extensions only apply to servers that support
them. x11vnc/libvncserver supports some of them.
Send Clipboard not Primary ~ -sendclipboard
Send Selection Every time ~ -sendalways
Nearly all of these can be changed dynamically in the Popup menu (press F8 for it):
For Windows, SSL Viewer support is provided by a GUI
Windows/ssvnc.exe that prompts for the
VNC display and then starts up STUNNEL followed by the Stock TightVNC
Windows Viewer. Both are bundled in the package for your convenience.
The GUI has other useful features. When the connection
is finished, you will be asked if you want to terminate the STUNNEL
program. For SSH connections from Windows the GUI will use PLINK
instead of STUNNEL.
A user
reports that SSVNC works properly in remote helpdesk mode using UltraVNC
Single-click in Windows Vista.
Unix and Mac OS X:
Run the GUI (ssvnc, see above) and let me know how it goes.
Hopefully this tool will make it convenient for people to help test and use the built-in SSL support in x11vnc. Extra testing of this feature is much appreciated!! Thanks.
Please Help Test the newly added features:
http://www.karlrunge.com/x11vnc/faq.html#faq-smb-shares
http://www.karlrunge.com/x11vnc/faq.html#faq-cups
http://www.karlrunge.com/x11vnc/faq.html#faq-sound
Downloading: Downloads for this project are hosted at Sourceforge.net.
Choose the archive file bundle that best suits you (e.g. no source code, windows only, unix only, zip, tar etc).
A quick guide:
On some flavor of Unix, e.g. Linux or Solaris? Use "ssvnc_unix_only" (or "ssvnc_no_windows" to recompile).
On Mac OS X? Use "ssvnc_no_windows".
On Windows? Use "ssvnc_windows_only".
ssvnc_windows_only-1.0.29.zip Windows Binaries Only. No source included (6.2MB) ssvnc_no_windows-1.0.29.tar.gz Unix and Mac OS X Only. No Windows binaries. Source included. (10.1MB) ssvnc_unix_only-1.0.29.tar.gz Unix Binaries Only. No source included. (7.2MB) ssvnc_unix_minimal-1.0.29.tar.gz Unix Minimal. You must supply your ownvncviewerandstunnel. (0.2MB) ssvnc-1.0.29.tar.gz All Unix, Mac OS X, and Windows binaries and source TGZ. (16.1MB) ssvnc-1.0.29.zip All Unix, Mac OS X, and Windows binaries and source ZIP. (16.4MB) ssvnc_all-1.0.29.zip All Unix, Mac OS X, and Windows binaries and source AND full archives in the zip dir. (19.2MB)
Here is a conventional source tarball:
ssvnc-1.0.29.src.tar.gz Conventional Source for SSVNC GUI and Unix VNCviewer (0.5MB)
it will be of use to those who do not want the SSVNC "one-size-fits-all" bundles.
For example, package/distro maintainers will find this more familiar and useful to
them (i.e. they run: "make config; make all; make install"). Note that it does not
include the stunnel source, and so has a dependency that the system stunnel
is installed.
Read the README.src file for more information on using the conventional source tarball.
Note: even with the Unix bundles, e.g. "ssvnc_no_windows"
or "ssvnc_all", you may need to run the "./build.unix"
script in the top directory to recompile for your operating system.
Here are the corresponding 1.0.30 development bundles (Please help test them):
ssvnc_windows_only-1.0.30.zip ssvnc_no_windows-1.0.30.tar.gz ssvnc_unix_only-1.0.30.tar.gz ssvnc_unix_minimal-1.0.30.tar.gz ssvnc-1.0.30.tar.gz ssvnc-1.0.30.zip ssvnc_all-1.0.30.zip ssvnc-1.0.30.src.tar.gz Conventional Source for SSVNC GUI and Unix VNCviewer (0.5MB)
For any Unix system, a self-extracting and running file for the "ssvnc_unix_minimal" package
is here: ssvnc.
Save it as filename "ssvnc", type "chmod 755 ./ssvnc",
and then launch the GUI via typing "./ssvnc".
Note that this "ssvnc_unix_minimal" mode requires you install the "stunnel"
and "vncviewer" programs externally (for example, install your
distros' versions, e.g. on debian: "apt-get install stunnel4 xtightvncviewer".)
It will work, but many of the SSVNC features will be missing.
Previous releases:
Release 1.0.18 at Sourceforge.net
Release 1.0.19 at Sourceforge.net
Release 1.0.20 at Sourceforge.net
Release 1.0.21 at Sourceforge.net
Release 1.0.22 at Sourceforge.net
Release 1.0.23 at Sourceforge.net
Release 1.0.24 at Sourceforge.net
Release 1.0.25 at Sourceforge.net
Release 1.0.26 at Sourceforge.net
Release 1.0.27 at Sourceforge.net
Release 1.0.28 at Sourceforge.net
Release 1.0.29 at Sourceforge.net
Please help test the UltraVNC File Transfer support in the native Unix VNC viewer! Let us know how it went.
Current Unix binaries in the archives:
Linux.i686
Linux.x86_64
Linux.ppc64 X (removed)
Linux.alpha X (removed)
SunOS.sun4u
SunOS.sun4m
SunOS.i86pc
Darwin.Power.Macintosh
Darwin.i386
HP-UX.9000 X (removed)
FreeBSD.i386 X (removed)
NetBSD.i386 X (removed)
OpenBSD.i386 X (removed)
(some of these are out of date, marked with 'X' above, because I no
longer have access to machines running those OS's. Use the
"build.unix" script to recompile on your system).
Note: some of the above binaries depend on libssl.so.0.9.7,
whereas some recent distros only provide libssl.so.0.9.8
by default (for compatibility reasons they should install both by default
but not all do). So you may need to instruct your distro to install the
0.9.7 library (it is fine to have both runtimes installed simultaneously
since the libraries have different names).
Update: I now try to statically link libssl.a
for all of the binaries in the archive.
You can also run the included build.unix script to try to
automatically build the binaries if your OS is not in the above list or
the included binary does not run properly on your system. Let me know
how that goes.
http://stunnel.mirt.net
http://www.stunnel.org
http://www.openssl.org
http://www.chiark.greenend.org.uk/~sgtatham/putty/
http://www.tightvnc.com
http://www.realvnc.com
http://sourceforge.net/projects/cotvnc/