diff options
Diffstat (limited to 'x11vnc/README')
| -rw-r--r-- | x11vnc/README | 570 |
1 files changed, 346 insertions, 224 deletions
diff --git a/x11vnc/README b/x11vnc/README index 3b86207..8d4ed68 100644 --- a/x11vnc/README +++ b/x11vnc/README @@ -1,5 +1,5 @@ -x11vnc README file Date: Mon Dec 8 22:48:46 EST 2008 +x11vnc README file Date: Sat Jan 3 19:10:09 EST 2009 The following information is taken from these URLs: @@ -573,12 +573,12 @@ vncviewer -via $host localhost:0 # must be TightVNC vncviewer. SourceForge.net. I use libvncserver for all of the VNC aspects; I couldn't have done without it. The full source code may be found and downloaded (either file-release tarball or CVS tree) from the above - link. As of Oct 2008, the [90]x11vnc-0.9.5.tar.gz source package is - released (recommended download). The [91]x11vnc 0.9.5 release notes. + link. As of Dec 2008, the [90]x11vnc-0.9.6.tar.gz source package is + released (recommended download). The [91]x11vnc 0.9.6 release notes. The x11vnc package is the subset of the libvncserver package needed to build the x11vnc program. Also, you can get a copy of my latest, - bleeding edge [92]x11vnc-0.9.6.tar.gz tarball to build the most up to + bleeding edge [92]x11vnc-0.9.7.tar.gz tarball to build the most up to date one. Precompiled Binaries/Packages: See the [93]FAQ below for information @@ -616,13 +616,13 @@ vncviewer -via $host localhost:0 # must be TightVNC vncviewer. them by default.) If your OS has libjpeg.so and libz.so in standard locations you can - build as follows (example given for the 0.9.5 release of x11vnc: + build as follows (example given for the 0.9.6 release of x11vnc: replace with the version you downloaded): (un-tar the x11vnc+libvncserver tarball) -# gzip -dc x11vnc-0.9.5.tar.gz | tar -xvf - +# gzip -dc x11vnc-0.9.6.tar.gz | tar -xvf - (cd to the source directory) -# cd x11vnc-0.9.5 +# cd x11vnc-0.9.6 (run configure and then run make) # ./configure @@ -864,13 +864,13 @@ make I'd appreciate any additional testing very much. Thanks to those who suggested features and helped beta test x11vnc - 0.9.5 released in Oct 2008! + 0.9.6 released in Dec 2008! - Please help test and debug the 0.9.6 version for release sometime in + Please help test and debug the 0.9.7 version for release sometime in Spring 2009. - The version 0.9.6 beta tarball is kept here: - [113]x11vnc-0.9.6.tar.gz + The version 0.9.7 beta tarball is kept here: + [113]x11vnc-0.9.7.tar.gz There are also some Linux, Solaris, Mac OS X, and other OS test binaries [114]here. Please kick the tires and report bugs, performance @@ -879,7 +879,7 @@ make To aid testing of the [116]built-in SSL/TLS support for x11vnc, a number of VNC Viewer packages for Unix, Mac OS X, and Windows have been created that provide SSL Support for the TightVNC Viewer (this is - done by [117]wrapper scripts and a GUI that start [118]STUNNEL). It + done by [117]wrapper scripts and a GUI that starts [118]STUNNEL). It should be pretty convenient for automatic SSL and SSH connections. It is described in detail at and can be downloaded from the [119]Enhanced TightVNC Viewer (SSVNC) page. The SSVNC Unix viewer also supports @@ -887,7 +887,11 @@ make Encryption Plugin' settings panel.) - Here are some features that will appear in the 0.9.6 release: + Here are some features that will appear in the 0.9.7 release: + * Coming Soon! + + + Here are some features that appeared in the 0.9.6 release: * Support for [121]VeNCrypt SSL/TLS encrypted connections. It is enabled by default in the [122]-ssl mode. VNC Viewers like vinagre, gvncviewer/gtk-vnc, the vencrypt package, and others @@ -917,8 +921,8 @@ make access deployment using a central Certificate Authority (CA) via [131]-sslGenCA and [132]-sslGenCert. This way if a user has his laptop lost or stolen, you only have to revoke his key instead of - creating a new Certificate Authority and redeploying keys to all - of the users. + creating a new Certificate Authority and redeploying new keys to + all users. * The default SSL/TLS mode, "[133]-ssl" (no pem file parameter supplied), is now the same as "-ssl SAVE" and will save the generated self-signed cert in "~/.vnc/certs/server.pem". @@ -7670,16 +7674,24 @@ rm -f $tmp Installation so the Installation can be done remotely? This can be done, but it doesn't always work because it depends on how - the OS does its install. We have to "sneak in" somehow. Usually the OS - install will have to be a network-install in order to have networking - up during the install. Otherwise, you may have a chance to configure - the networking manually (ifconfig(8) and route(8)). + the OS does its install. We have to "sneak in" somehow. Note that some + OS's have a remote install (ssh etc.) built in and so you might want + to use that instead. + + Usually the OS install will have to be a network-install in order to + have networking up during the install. Otherwise, you may have a + (slim) chance to configure the networking manually (ifconfig(8) and + route(8)). To avoid library dependencies problems in the typical minimal (e.g. busybox) installation OS it is a good idea to build a statically linked x11vnc binary. A way that often works is to do a normal build and then paste the final x11vnc link line into a shell script. Then - change the "gcc" to "gcc -static" and run the shell script. + change the "gcc" to "gcc -static" and run the shell script. You may + need to disable features (e.g. "--without-xfixes") if there is not a + static library for the feature available. You may also need to add + extra link options (e.g. "-lXrender") to complete library dependencies + manually. Let's call the binary x11vnc.static. Place it on a webserver somewhere. It may be possible to retrieve it via scp(1) too. @@ -7694,7 +7706,7 @@ rm -f $tmp If it is a Linux install that uses an X server (e.g. SuSE and probably Fedora), then you can often get a shell by pressing Ctrl-Alt-F2 or - similar. Then get the x11vnc binary something like this: + similar. Then get the x11vnc binary via something like this: cd /tmp wget http://192.168.0.22/x11vnc.static chmod 755 ./x11vnc.static @@ -7707,21 +7719,32 @@ rm -f $tmp to connect via a vnc viewer and continue the install. Watch out for the display being :1, etc. + If there is a firewall blocking incoming connections during the + install, use the [932]"-connect hostname" option option for a reverse + connection to the hostname running the VNC viewer in listen mode. + Debian based installs are either console-text or console-framebuffer based. These are install (or expert) and installgui (or expertgui) boot lines, respectively. For the console-text based installs you - probably need to add a boot cmd line option like vga=0x314 to get the - console-text to use the linux framebuffer device properly. + probably need to add a boot cmd line option like vga=0x314 (which is + 800x600x16) to get the console-text to use the linux framebuffer + device properly. For a Debian console-text based install after the network is - configured press Ctrl-Alt-F2 to get a shell. Retrieve via wget as - above. Run it something like this: + configured press Ctrl-Alt-F2 to get a shell. Retrieve the binary via + wget as above and chmod 755 it. Then run it something like this: sleep 10; ./x11vnc.static -forever -nopw -rawfb console then before the sleep is over press Alt-F1 to get back to the install virtual console. You should be able to connect via a VNC viewer and continue with the install. + For a recent (2009) Debian install we booted with "expert vga=0x301" + and "expert vga=0x311" to get console text based installs at 640x480x8 + and 640x480x16, respectively (replace "expert" with "install" if you + like.) Otherwise it was giving a 16 color 640x480x4 (4 bit per pixel) + display which x11vnc could not handle. + For Debian console-framebuffer GUI based installs (installgui or expertgui) we have not be able to enter keystrokes or mouse motions. This may be resolved if the install had the Linux kernel module @@ -7730,8 +7753,8 @@ rm -f $tmp that, you can only do the GUI view-only, which can be handy to watch a long network install from your desk instead of in front of the machine being installed. For these, after the network is configured press - Ctrl-Alt-F2 to get a shell. Retrieve via wget as above. Run it - something like this: + Ctrl-Alt-F2 to get a shell. Retrieve the binary via wget as above and + chmod 755 it. Then run it something like this: sleep 10; ./x11vnc.static -forever -nopw -rawfb console then before the sleep is over press Alt-F5 to get back to the GUI @@ -7746,11 +7769,11 @@ rm -f $tmp As of Jan/2004 x11vnc supports the "CutText" part of the rfb protocol. Furthermore, x11vnc is able to hold the PRIMARY and CLIPBOARD selection (Xvnc does not seem to do this). If you don't want the - Clipboard/Selection exchanged use the [932]-nosel option. If you don't + Clipboard/Selection exchanged use the [933]-nosel option. If you don't want the PRIMARY selection to be polled for changes use the - [933]-noprimary option. (with a similar thing for CLIPBOARD). You can - also fine-tune it a bit with the [934]-seldir dir option and also - [935]-input. + [934]-noprimary option. (with a similar thing for CLIPBOARD). You can + also fine-tune it a bit with the [935]-seldir dir option and also + [936]-input. You may need to watch out for desktop utilities such as KDE's "Klipper" that do odd things with the selection, clipboard, and @@ -7762,7 +7785,7 @@ rm -f $tmp Yes, it is possible with a number of tools that record VNC and transform it to swf format or others. One such popular tool is - [936]pyvnc2swf. There are a number of [937]tutorials on how to do + [937]pyvnc2swf. There are a number of [938]tutorials on how to do this. Another option is to use the vnc2mpg that comes in the LibVNCServer package. An important thing to remember when doing this is that tuning @@ -7777,11 +7800,11 @@ rm -f $tmp (and Windows viewers only support filetransfer it appears... but they do work to some degree under Wine on Linux). - The [938]SSVNC Unix VNC viewer supports UltraVNC file transfer by use + The [939]SSVNC Unix VNC viewer supports UltraVNC file transfer by use of a Java helper program. TightVNC file transfer is off by default, if you want to enable it use - the [939]-tightfilexfer option. + the [940]-tightfilexfer option. UltraVNC file transfer is off by default, to enable it use something like "-rfbversion 3.6 -permitfiletransfer" @@ -7804,7 +7827,7 @@ rm -f $tmp IMPORTANT: please understand if -ultrafilexfer or -tightfilexfer is specified and you run x11vnc as root for, say, inetd or display manager (gdm, kdm, ...) access and you do not have it switch users via - the [940]-users option, then VNC Viewers that connect are able to do + the [941]-users option, then VNC Viewers that connect are able to do filetransfer reads and writes as *root*. The UltraVNC and TightVNC settings can be toggled on and off inside @@ -7823,7 +7846,7 @@ rm -f $tmp these extensions you will need to supply this option to x11vnc: -rfbversion 3.6 - Or use [941]-ultrafilexfer which is an alias for the above option and + Or use [942]-ultrafilexfer which is an alias for the above option and "-permitfiletransfer". UltraVNC evidently treats any other RFB version number as non-UltraVNC. @@ -7835,14 +7858,14 @@ rm -f $tmp * 1/n Server Scaling * rfbEncodingUltra compression encoding - The [942]SSVNC Unix VNC viewer supports these UltraVNC extensions. + The [943]SSVNC Unix VNC viewer supports these UltraVNC extensions. - To disable SingleWindow and ServerInput use [943]-noultraext (the + To disable SingleWindow and ServerInput use [944]-noultraext (the others are managed by LibVNCServer). See this option too: - [944]-noserverdpms. + [945]-noserverdpms. - Also, the [945]UltraVNC repeater proxy is supported for use with - reverse connections: "[946]-connect repeater://host:port+ID:NNNN". Use + Also, the [946]UltraVNC repeater proxy is supported for use with + reverse connections: "[947]-connect repeater://host:port+ID:NNNN". Use it for both plaintext and SSL connections. This mode can send any string before switching to the VNC protocol, and so could be used with other proxy/gateway tools. @@ -7853,12 +7876,12 @@ rm -f $tmp reverse vnc connection from their Unix desktop to a helpdesk operator's VNC Viewer. - Yes, UltraVNC's [947]Single Click (SC) mode can be done fairly well on + Yes, UltraVNC's [948]Single Click (SC) mode can be done fairly well on Unix. We use the term "helpdesk" below, but it could be any sort of remote assistance you want to set up, e.g. something for Unix-using friends - or family to use. This includes [948]Mac OS X. + or family to use. This includes [949]Mac OS X. Assume you create a helpdesk directory "hd" on your website: http://www.mysite.com/hd (any website that you can upload files to @@ -7914,7 +7937,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc So I guess this is about 3-4 clicks (start a terminal and paste) and pressing "Enter" instead of "single click"... - See [949]this page for some variations on this method, e.g. how to add + See [950]this page for some variations on this method, e.g. how to add a password, SSL Certificates, etc. @@ -7926,11 +7949,11 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc A bit of obscurity security could be put in with a -passwd, -rfbauth options, etc. (note that x11vnc will require a password even for - reverse connections). More info [950]here. + reverse connections). More info [951]here. Firewalls: If the helpdesk (you) with the vncviewer is behind a - NAT/Firewall/Router the [951]router will have to be configured to + NAT/Firewall/Router the [952]router will have to be configured to redirect a port (i.e. 5500 or maybe different one if you like) to the vncviewer machine. If the vncviewer machine also has its own host-level firewall, you will have to open up the port there as well. @@ -7940,7 +7963,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc configuring a router to do a port redirection (i.e. on your side, the HelpDesk). To avoid modifying either firewall/router, one would need some public (IP address reachable on the internet) redirection/proxy - service. Perhaps such a thing exists. [952]http://sc.uvnc.com provides + service. Perhaps such a thing exists. [953]http://sc.uvnc.com provides this service for their UltraVNC Single Click users. @@ -7976,7 +7999,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc As of Apr/2007 x11vnc supports reverse connections in SSL and so we can do this. On the Helpdesk side (Viewer) you will need STUNNEL or - better use the [953]Enhanced TightVNC Viewer (SSVNC) package we + better use the [954]Enhanced TightVNC Viewer (SSVNC) package we provide that automates all of the SSL for you. To do this create a file named "vncs" in the website "hd" directory @@ -8006,11 +8029,11 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc with the hostnames or IP addresses customized to your case. - The only change from the "vnc" above is the addition of the [954]-ssl + The only change from the "vnc" above is the addition of the [955]-ssl option to x11vnc. This will create a temporary SSL cert: openssl(1) will need to be installed on the user's end. A fixed SSL cert file could be used to avoid this (and provide some authentication; more - info [955]here.) + info [956]here.) The naive user will be doing this: wget -qO - http://www.mysite.com/hd/vncs | sh - @@ -8019,7 +8042,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc But before that, the helpdesk operator needs to have "vncviewer -listen" running as before, however he needs an SSL tunnel at his end. - The easiest way to do this is use [956]Enhanced TightVNC Viewer + The easiest way to do this is use [957]Enhanced TightVNC Viewer (SSVNC). Start it, and select Options -> 'Reverse VNC Connection (-listen)'. Then UN-select 'Verify All Certs' (this can be enabled later if you want; you'll need the x11vnc SSL certificate), and click @@ -8049,7 +8072,7 @@ connect = localhost:5501 answer the prompts with whatever you want; you can take the default for all of them if you like. The openssl(1) package must be installed. - See [957]this link and [958]this one too for more info on SSL certs. + See [958]this link and [959]this one too for more info on SSL certs. This creates $HOME/.vnc/certs/server-self:mystunnel.pem, then you would change the "stunnel.cfg" to look something like: foreground = yes @@ -8070,7 +8093,7 @@ connect = localhost:5501 then all bets are off!. More SSL variations and info about certificates can be found - [959]here. + [960]here. OpenSSL libssl.so.0.9.7 problems: @@ -8080,7 +8103,7 @@ connect = localhost:5501 distros are currently a bit of a mess regarding which version of libssl is installed. - You will find the [960]details here. + You will find the [961]details here. Q-120: Can I (temporarily) mount my local (viewer-side) Windows/Samba @@ -8089,7 +8112,7 @@ connect = localhost:5501 You will have to use an external network redirection for this. Filesystem mounting is not part of the VNC protocol. - We show a simple [961]Samba example here. + We show a simple [962]Samba example here. First you will need a tunnel to redirect the SMB requests from the remote machine to the one you sitting at. We use an ssh tunnel: @@ -8129,7 +8152,7 @@ d,ip=127.0.0.1,port=1139 far-away> smbumount /home/fred/smb-haystack-pub At some point we hope to fold some automation for SMB ssh redir setup - into the [962]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [963]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing). @@ -8139,7 +8162,7 @@ d,ip=127.0.0.1,port=1139 You will have to use an external network redirection for this. Printing is not part of the VNC protocol. - We show a simple Unix to Unix [963]CUPS example here. Non-CUPS port + We show a simple Unix to Unix [964]CUPS example here. Non-CUPS port redirections (e.g. LPD) should also be possible, but may be a bit more tricky. If you are viewing on Windows SMB and don't have a local cups server it may be trickier still (see below). @@ -8173,34 +8196,44 @@ d,ip=127.0.0.1,port=1139 for Host and 6631 for Port). The main setting you want to convey is the host is localhost and the port is non-standard (e.g. 6631). Some configuration utilities will take an Internet Printing Protocol (IPP) - URI, e.g. http://localhost:6631/ipp/, - http://localhost:6631/ipp/printer-name, - ipp://localhost:6631/ipp/printer-name, etc. - - If you do not have root privileges, but are running a recent (version - 1.2 or greater) of the Cups client software, then an easy way to - temporarily switch Cups servers is to create: $HOME/.cupsrc on the - remote side with a line like: + URI, e.g. http://localhost:6631/printers/, + ipp://localhost:6631/printers/printer-name, + ipp://localhost:6631/ipp/printer-name, etc. Check your CUPS + documentation and admin interfaces to find what the syntax is and what + the "printer name" is. + + If you do not have root or print admin privileges, but are running a + recent (version 1.2 or greater) of the Cups client software, then an + easy way to temporarily switch Cups servers is to create the directory + and file: $HOME/.cups/client.conf on the remote side with a line like: ServerName localhost:6631 When not using x11vnc for remote access you can comment the above line - out with a '#' (or rename the cupsrc file), to have normal cups + out with a '#' (or rename the client.conf file), to have normal cups operation. - Sadly, Cups client software that is older (1.1) does not support - appending the port number, and for newer ones there is a bug - preventing it from always working (fixed in 1.2.3). Kludges like these - at the command line will work: + Unfortunately, running applications may need to be restarted to notice + the new printers (libcups does not track changes in client.conf). + Depending on circumstances, a running application may actually notice + the new printers without restarting (e.g. no print dialog has taken + place yet, or there are no CUPS printers configured on the remote + side.) + + Cups client software that is older (1.1) does not support appending + the port number, and for newer ones there is a bug preventing it from + always working (fixed in 1.2.3). Kludges like these at the command + line will work: far-away> env CUPS_SERVER=localhost IPP_PORT=6631 lpstat -p -d far-away> env CUPS_SERVER=localhost IPP_PORT=6631 lpr -P myprinter file.ps far-away> env CUPS_SERVER=localhost IPP_PORT=6631 firefox but are somewhat awkward since you have to retroactively set the env. var IPP_PORT. Its value cannot be broadcast to already running apps - (like the $HOME/.cupsrc trick does). A common workaround for an - already running app is to somehow get it to "Print To File", e.g. - file.ps and then use something like the lpr example above. Also, the - option "-h host:port" works with CUPS lp(1) and lpr(1). + (like the $HOME/.cups/client.conf trick sometimes does). A common + workaround for an already running app is to somehow get it to "Print + To File", e.g. file.ps and then use something like the lpr example + above. Also, the option "-h host:port" works with CUPS lp(1) and + lpr(1). You can also print to Windows shares printers in principle. You may do this with the smbspool(8) command, or configure the remote CUPS via @@ -8211,7 +8244,7 @@ d,ip=127.0.0.1,port=1139 "localhost". At some point we hope to fold some automation for CUPS ssh redir setup - into the [964]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [965]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing). @@ -8312,7 +8345,7 @@ or: the applications will fail to run because LD_PRELOAD will point to libraries of the wrong wordsize. * At some point we hope to fold some automation for esd or artsd ssh - redir setup into the [965]Enhanced TightVNC Viewer (SSVNC) package + redir setup into the [966]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep/2006 it is there for testing). @@ -8324,14 +8357,14 @@ or: in Solaris, see Xserver(1) for how to turn it on via +kb), and so you won't hear them if the extension is not present. - If you don't want to hear the beeps use the [966]-nobell option. If + If you don't want to hear the beeps use the [967]-nobell option. If you want to hear the audio from the remote applications, consider - trying a [967]redirector such as esd. + trying a [968]redirector such as esd. Q-124: Does x11vnc work with IPv6? - Currently the only way to do this is via [968]inetd. You configure + Currently the only way to do this is via [969]inetd. You configure x11vnc to be run from inetd or xinetd and instruct it to listen on an IPv6 address. For xinetd the setting "flags = IPv6" will be needed. @@ -8340,7 +8373,7 @@ or: connection). Some sort of ipv4-to-ipv6 redirector tool (perhaps even a perl script) could be useful to avoid this. - Also note that not all VNC Viewers are [969]IPv6 enabled, so a + Also note that not all VNC Viewers are [970]IPv6 enabled, so a redirector could even be needed on the client side. @@ -8355,7 +8388,7 @@ or: anything) and thank you for your support! Click on the PayPal button below for more info. - [PayPal] + [x-click-but04.gif]-Submit References @@ -8448,9 +8481,9 @@ References 87. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int 88. http://www.karlrunge.com/x11vnc/ssvnc.html 89. http://sourceforge.net/projects/libvncserver/ - 90. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=635593 - 91. http://sourceforge.net/project/shownotes.php?release_id=635593&group_id=32584 - 92. http://www.karlrunge.com/x11vnc/x11vnc-0.9.6.tar.gz + 90. http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=646288 + 91. http://sourceforge.net/project/shownotes.php?release_id=646288&group_id=32584 + 92. http://www.karlrunge.com/x11vnc/x11vnc-0.9.7.tar.gz 93. http://www.karlrunge.com/x11vnc/index.html#faq-binaries 94. http://www.tightvnc.com/download.html 95. http://www.realvnc.com/download-free.html @@ -8471,7 +8504,7 @@ References 110. http://www.karlrunge.com/x11vnc/index.html#faq-solaris251build 111. http://www.karlrunge.com/x11vnc/index.html#faq-macosx 112. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int - 113. http://www.karlrunge.com/x11vnc/x11vnc-0.9.6.tar.gz + 113. http://www.karlrunge.com/x11vnc/x11vnc-0.9.7.tar.gz 114. http://www.karlrunge.com/x11vnc/bins 115. mailto:xvml@karlrunge.com 116. http://www.karlrunge.com/x11vnc/index.html#faq-ssl-tunnel-int @@ -9290,44 +9323,45 @@ References 929. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect 930. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager 931. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 932. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 933. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary - 934. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir - 935. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input - 936. http://www.unixuser.org/~euske/vnc2swf/ - 937. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ - 938. http://www.karlrunge.com/x11vnc/ssvnc.html - 939. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer - 940. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 941. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer - 942. http://www.karlrunge.com/x11vnc/ssvnc.html - 943. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext - 944. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms - 945. http://www.uvnc.com/addons/repeater.html - 946. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 947. http://www.uvnc.com/addons/singleclick.html - 948. http://www.karlrunge.com/x11vnc/index.html#faq-macosx - 949. http://www.karlrunge.com/x11vnc/single-click.html + 932. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 933. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 934. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary + 935. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir + 936. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 937. http://www.unixuser.org/~euske/vnc2swf/ + 938. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ + 939. http://www.karlrunge.com/x11vnc/ssvnc.html + 940. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer + 941. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 942. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer + 943. http://www.karlrunge.com/x11vnc/ssvnc.html + 944. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext + 945. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms + 946. http://www.uvnc.com/addons/repeater.html + 947. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 948. http://www.uvnc.com/addons/singleclick.html + 949. http://www.karlrunge.com/x11vnc/index.html#faq-macosx 950. http://www.karlrunge.com/x11vnc/single-click.html - 951. http://www.karlrunge.com/x11vnc/index.html#firewalls - 952. http://sc.uvnc.com/ - 953. http://www.karlrunge.com/x11vnc/ssvnc.html - 954. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 955. http://www.karlrunge.com/x11vnc/single-click.html - 956. http://www.karlrunge.com/x11vnc/ssvnc.html - 957. http://www.karlrunge.com/x11vnc/single-click.html - 958. http://www.karlrunge.com/x11vnc/ssl.html - 959. http://www.karlrunge.com/x11vnc/single-click.html - 960. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems - 961. http://www.samba.org/ - 962. http://www.karlrunge.com/x11vnc/ssvnc.html - 963. http://www.cups.org/ - 964. http://www.karlrunge.com/x11vnc/ssvnc.html + 951. http://www.karlrunge.com/x11vnc/single-click.html + 952. http://www.karlrunge.com/x11vnc/index.html#firewalls + 953. http://sc.uvnc.com/ + 954. http://www.karlrunge.com/x11vnc/ssvnc.html + 955. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl + 956. http://www.karlrunge.com/x11vnc/single-click.html + 957. http://www.karlrunge.com/x11vnc/ssvnc.html + 958. http://www.karlrunge.com/x11vnc/single-click.html + 959. http://www.karlrunge.com/x11vnc/ssl.html + 960. http://www.karlrunge.com/x11vnc/single-click.html + 961. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems + 962. http://www.samba.org/ + 963. http://www.karlrunge.com/x11vnc/ssvnc.html + 964. http://www.cups.org/ 965. http://www.karlrunge.com/x11vnc/ssvnc.html - 966. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell - 967. http://www.karlrunge.com/x11vnc/index.html#faq-sound - 968. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 969. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html + 966. http://www.karlrunge.com/x11vnc/ssvnc.html + 967. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell + 968. http://www.karlrunge.com/x11vnc/index.html#faq-sound + 969. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 970. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html ======================================================================= http://www.karlrunge.com/x11vnc/chainingssh.html: @@ -11267,7 +11301,7 @@ Enhanced TightVNC Viewer (SSVNC: SSL/SSH VNC viewer) connecting. * Support for native MacOS X usage with bundled Chicken of the VNC viewer (the Unix X11 viewer is also provided for MacOS X, and is - better IMHO). + better IMHO. It is now the default on MacOS X.) * [15]Dynamic VNC Server Port determination and redirection (using ssh's builtin SOCKS proxy, ssh -D) for servers like x11vnc that print out PORT= at startup. @@ -11741,12 +11775,27 @@ Enhanced TightVNC viewer (SSVNC) options: 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. - - Note that scaling is done in software and can be slow - and requires more memory. "str" can also be set by + 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. @@ -12217,7 +12266,7 @@ x11vnc: a VNC server for real X displays Here are all of x11vnc command line options: % x11vnc -opts (see below for -help long descriptions) -x11vnc: allow VNC connections to real X11 displays. 0.9.6 lastmod: 2008-12-08 +x11vnc: allow VNC connections to real X11 displays. 0.9.7 lastmod: 2009-01-03 x11vnc options: -display disp -auth file -N @@ -12257,57 +12306,57 @@ x11vnc options: -blackout string -xinerama -noxinerama -xtrap -xrandr [mode] -rotate string -padgeom WxH -o logfile -flag file - -rc filename -norc -env VAR=VALUE - -prog /path/to/x11vnc -h, -help -?, -opts - -V, -version -license -dbg - -q, -quiet -v, -verbose -bg - -modtweak -nomodtweak -xkb - -noxkb -capslock -skip_lockkeys - -skip_keycodes string -sloppy_keys -skip_dups - -noskip_dups -add_keysyms -noadd_keysyms - -clear_mods -clear_keys -clear_all - -remap string -norepeat -repeat - -nofb -nobell -nosel - -noprimary -nosetprimary -noclipboard - -nosetclipboard -seldir string -cursor [mode] - -nocursor -cursor_drag -arrow n - -noxfixes -alphacut n -alphafrac fraction - -alpharemove -noalphablend -nocursorshape - -cursorpos -nocursorpos -xwarppointer - -noxwarppointer -buttonmap string -nodragging - -ncache n -ncache_cr -ncache_no_moveraise - -ncache_no_dtchange -ncache_no_rootpixmap -ncache_keep_anims - -ncache_old_wm -ncache_pad n -debug_ncache - -wireframe [str] -nowireframe -nowireframelocal - -wirecopyrect mode -nowirecopyrect -debug_wireframe - -scrollcopyrect mode -noscrollcopyrect -scr_area n - -scr_skip list -scr_inc list -scr_keys list - -scr_term list -scr_keyrepeat lo-hi -scr_parms string - -fixscreen string -debug_scroll -noxrecord - -grab_buster -nograb_buster -debug_grabs - -debug_sel -pointer_mode n -input_skip n - -allinput -speeds rd,bw,lat -wmdt string - -debug_pointer -debug_keyboard -defer time - -wait time -wait_ui factor -setdefer n - -nowait_bog -slow_fb time -xrefresh time - -nap -nonap -sb time - -readtimeout n -ping n -nofbpm - -fbpm -nodpms -dpms - -forcedpms -clientdpms -noserverdpms - -noultraext -chatwindow -noxdamage - -xd_area A -xd_mem f -sigpipe string - -threads -nothreads -fs f - -gaps n -grow n -fuzz n - -debug_tiles -snapfb -rawfb string - -freqtab file -pipeinput cmd -macnodim - -macnosleep -macnosaver -macnowait - -macwheel n -macnoswap -macnoresize - -maciconanim n -macmenu -macuskbd - -gui [gui-opts] -remote command -query variable - -QD variable -sync -noremote - -yesremote -unsafe -safer - -privremote -nocmds -allowedcmds list - -deny_all + -rmflag file -rc filename -norc + -env VAR=VALUE -prog /path/to/x11vnc -h, -help + -?, -opts -V, -version -license + -dbg -q, -quiet -v, -verbose + -bg -modtweak -nomodtweak + -xkb -noxkb -capslock + -skip_lockkeys -skip_keycodes string -sloppy_keys + -skip_dups -noskip_dups -add_keysyms + -noadd_keysyms -clear_mods -clear_keys + -clear_all -remap string -norepeat + -repeat -nofb -nobell + -nosel -noprimary -nosetprimary + -noclipboard -nosetclipboard -seldir string + -cursor [mode] -nocursor -cursor_drag + -arrow n -noxfixes -alphacut n + -alphafrac fraction -alpharemove -noalphablend + -nocursorshape -cursorpos -nocursorpos + -xwarppointer -noxwarppointer -buttonmap string + -nodragging -ncache n -ncache_cr + -ncache_no_moveraise -ncache_no_dtchange -ncache_no_rootpixmap + -ncache_keep_anims -ncache_old_wm -ncache_pad n + -debug_ncache -wireframe [str] -nowireframe + -nowireframelocal -wirecopyrect mode -nowirecopyrect + -debug_wireframe -scrollcopyrect mode -noscrollcopyrect + -scr_area n -scr_skip list -scr_inc list + -scr_keys list -scr_term list -scr_keyrepeat lo-hi + -scr_parms string -fixscreen string -debug_scroll + -noxrecord -grab_buster -nograb_buster + -debug_grabs -debug_sel -pointer_mode n + -input_skip n -allinput -speeds rd,bw,lat + -wmdt string -debug_pointer -debug_keyboard + -defer time -wait time -wait_ui factor + -setdefer n -nowait_bog -slow_fb time + -xrefresh time -nap -nonap + -sb time -readtimeout n -ping n + -nofbpm -fbpm -nodpms + -dpms -forcedpms -clientdpms + -noserverdpms -noultraext -chatwindow + -noxdamage -xd_area A -xd_mem f + -sigpipe string -threads -nothreads + -fs f -gaps n -grow n + -fuzz n -debug_tiles -snapfb + -rawfb string -freqtab file -pipeinput cmd + -macnodim -macnosleep -macnosaver + -macnowait -macwheel n -macnoswap + -macnoresize -maciconanim n -macmenu + -macuskbd -gui [gui-opts] -remote command + -query variable -QD variable -sync + -noremote -yesremote -unsafe + -safer -privremote -nocmds + -allowedcmds list -deny_all libvncserver options: -rfbport port TCP port for RFB protocol @@ -12341,7 +12390,7 @@ libvncserver-tight-extension options: % x11vnc -help -x11vnc: allow VNC connections to real X11 displays. 0.9.6 lastmod: 2008-12-08 +x11vnc: allow VNC connections to real X11 displays. 0.9.7 lastmod: 2009-01-03 (type "x11vnc -opts" to just list the options.) @@ -14786,6 +14835,13 @@ t "file" in addition to stdout. This option could be useful by wrapper script to detect when x11vnc is ready. +-rmflag file Remove "file" at exit to signal when x11vnc is done. + The file is created at startup if it does not already + exist or if "file" is prefixed with "create:". + If the file is created, the x11vnc PID is placed in + the file. Otherwise the files contents is not changed. + Use prefix "nocreate:" to prevent creation. + -rc filename Use "filename" instead of $HOME/.x11vncrc for rc file. -norc Do not process any .x11vncrc file for options. @@ -15914,16 +15970,18 @@ t -rawfb string Instead of polling X, poll the memory object specified in "string". - For file polling to memory map mmap(2) a file use: + For file polling, to memory map mmap(2) a file use: "map:/path/to/a/file@WxHxB", with framebuffer Width, Height, and Bits per pixel. "mmap:..." is the same. - If there is trouble with mmap, use "file:/..." - for slower lseek(2) based reading. Use "snap:..." - to imply -snapfb mode and the "file:" access (this - is for unseekable devices that only provide the fb all - at once, e.g. a video camera provides the whole frame). + If there is trouble with mmap, use "file:/..." + for slower lseek(2) based reading. + + Use "snap:..." to imply -snapfb mode and the "file:" + access (this is for unseekable devices that only provide + the fb all at once, e.g. a video camera provides the + whole frame). For shared memory segments string is of the form: "shm:N@WxHxB" which specifies a shmid N and with @@ -15943,25 +16001,29 @@ t discussion below where the device may be queried for (and possibly set) the framebuffer parameters. - If the string begins with "console", "/dev/fb", or - "fb", see the LINUX CONSOLE discussion below where - the framebuffer device is opened and keystrokes (and - possibly mouse events) are inserted into the console. + If the string begins with "console", "/dev/fb", + "fb", or "vt", see the LINUX CONSOLE discussion + below where the framebuffer device is opened and + keystrokes (and possibly mouse events) are inserted + into the console. If the string begins with "vnc", see the VNC HOST discussion below where the framebuffer is taken as that of another remote VNC server. Optional suffixes are ":R/G/B" and "+O" to specify - red, green, and blue masks and an offset into the - memory object. If the masks are not provided x11vnc - guesses them based on the bpp. + red, green, and blue masks (in hex) and an offset into + the memory object. If the masks are not provided x11vnc + guesses them based on the bpp (if the colors look wrong, + you need to provide the masks.) Another optional suffix is the Bytes Per Line which in - some cases is not WxB/4. Specify it as WxHxB-BPL + some cases is not WxB/8. Specify it as WxHxB-BPL e.g. 800x600x16-2048. This could be a normal width 1024 at 16bpp fb, but only width 800 shows up. + So the full format is: mode:file@WxHxB:R/G/B+O-BPL + Examples: -rawfb shm:210337933@800x600x32:ff/ff00/ff0000 -rawfb map:/dev/fb0@1024x768x32 @@ -15972,6 +16034,7 @@ t -rawfb video0 -rawfb video -pipeinput VID -rawfb console + -rawfb vt2 -rawfb vnc:somehost:0 (see ipcs(1) and fbset(1) for the first two examples) @@ -15995,7 +16058,7 @@ t If the device is not "seekable" (e.g. webcam) try reading it all at once in full snaps via the "snap:" mode (note: this is a resource hog). If you are using - file: or map: and the device needs to be reopened for + file: or map: AND the device needs to be reopened for *every* snapfb snapshot, set the environment variable: SNAPFB_RAWFB_RESET=1 as well. @@ -16006,6 +16069,25 @@ t 24bpp packed RGB. This is the default under "video" mode if the bpp is 24. + Normally the bits per pixel, B, is 8, 16, or 32 (or + rarely 24), however there is also some support for + B < 8 (e.g. old graphics displays 4 bpp or 1 bpp). + In this case you certainly must supply the masks as + well: WxHxB:R/G/B. The pixels will be padded out to + 8 bpp using depth 8 truecolor. The scheme currently + does not work with snap fb (ask if interested.) B=1 + monochrome example: file:/dev/urandom@128x128x1:1/1/1 + Some other like this are 128x128x2:3/3/3 128x128x4:7/7/7 + + For B < 8 framebuffers you can also set the env. var + RAWFB_CGA=1 to try a CGA mapping for B=4 (e.g. linux + vga16fb driver.) Note with low bpp and/or resolution + VGA and VGA16 modes on the Linux console one's attempt + to export them via x11vnc can often be thwarted due to + special color palettes, pixel packings, and even video + painting buffering. OTOH, often experimenting with the + RGB masks can yield something recognizable. + VIDEO4LINUX: on Linux some attempt is made to handle video devices (webcams or TV tuners) automatically. The idea is the WxHxB will be extracted from the @@ -16092,37 +16174,76 @@ t is not queried for the current values. Otherwise the device will be queried. - LINUX CONSOLE: If the libvncserver LinuxVNC program - is on your system you may want to use that instead of - the following method because it will be faster and more - accurate for Linux text console. + LINUX CONSOLE: The following describes some ways to + view and possibly interact with the Linux text/graphics + console (i.e. not X11 XFree86/Xorg) + + Note: If the libvncserver LinuxVNC program is on your + system you may want to use that instead of the following + method because it will be faster and more accurate + for the Linux text console and includes mouse support. + There is, however, the basic LinuxVNC functionality in + x11vnc if you replace "console" with "vt" in the + examples below. If the rawfb string begins with "console" the - framebuffer device /dev/fb0 is opened (this requires - the appropriate kernel modules to be installed) and so - is /dev/tty0. The latter is used to inject keystrokes + framebuffer device /dev/fb0 is opened and /dev/tty0 is + opened too. The latter is used to inject keystrokes (not all are supported, but the basic ones are). - You will need to be root to inject keystrokes. - /dev/tty0 refers to the active VT, to indicate one - explicitly, use "console2", etc. using the VT number. - - If the Linux version seems to be 2.6 or later and the - "uinput" module appears to be present, then the uinput - method will be used instead of /dev/ttyN. uinput allows - insertion of BOTH keystrokes and mouse input and so it - preferred when accessing graphical (e.g. QT-embedded) - linux console apps. See -pipeinput UINPUT below for - more information on this mode; you will have to use - -pipeinput if you want to tweak any UINPUT parameters. - You may also want to also use the -nodragging and - -cursor none options. Use "console0", etc or - -pipeinput CONSOLE to force the /dev/ttyN method. - - Note you can change VT remotely using the chvt(1) - command. Sometimes switching out and back corrects - the framebuffer state. - - To skip input injecting entirely use "consolex". + You will need to be root to inject keystrokes, but + not necessarily to open /dev/fb0. /dev/tty0 refers to + the active VT, to indicate one explicitly, use, e.g., + "console2" for /dev/tty2, etc. by indicating the + specific VT number. + + For the Linux framebuffer device, /dev/fb0, (fb1, + etc) to be enabled the appropriate kernel drivers must + be loaded. E.g. vesafb or vga16fb and also by setting + the boot parameter vga=0x301 (or 0x314, 0x317, etc.) + (The vga=... method is the preferred way; set your + machines up that way.) Otherwise there will be a + 'No such device' error. You can also load a Linux + framebuffer driver specific to your make of video card + for more functionality. Once the machine is booted one + can often 'modprobe' the fb driver as root to obtain + a framebuffer device. + + If you cannot get /dev/fb0 working on Linux, try + using the LinuxVNC emulation mode by "-rawfb vtN" + where N = 1, ... 6 is the Linux Virtual Terminal (aka + virtual console) you wish to view, e.g. "-rawfb vt2". + Unlike /dev/fb mode, it need not be the active Virtual + Terminal. Note that this mode can only show text and + not graphics. x11vnc polls the text in /dev/vcsaN + + Set the env. var. RAWFB_VCSA_BW=1 to disable colors in + the "vtN" mode (i.e. black and white only.) If you + do not prefer the default 16bpp set RAWFB_VCSA_BPP to + 8 or 32. If you need to tweak the rawfb parameters by + using the 'console_guess' string printed at startup, + be sure to indicate the snap: method. + + uinput: If the Linux version appears to be 2.6 or + later and the "uinput" module appears to be present + (modprobe uinput), then the uinput method will be used + instead of /dev/ttyN. uinput allows insertion of BOTH + keystrokes and mouse input and so it preferred when + accessing graphical (e.g. QT-embedded) linux console + apps. See -pipeinput UINPUT below for more information + on this mode; you will have to use -pipeinput if you + want to tweak any UINPUT parameters. You may also want + to also use the -nodragging and -cursor none options. + Use "console0", etc or -pipeinput CONSOLE to force + the /dev/ttyN method. + + Note you can change the Linux VT remotely using the + chvt(1) command to make the one you want be the active + one (e.g. 'chvt 3'). Sometimes switching out and back + corrects the framebuffer's graphics state. For the + "-rawfb vtN" mode there is no need to switch the VT's. + + To skip input injecting entirely use "consolex" + or "vtx". The string "/dev/fb0" (1, etc.) can be used instead of "console". This can be used to specify a different @@ -16132,8 +16253,8 @@ t If you do not want x11vnc to guess the framebuffer's WxHxB and masks automatically (sometimes the kernel - gives inaccurate information), specify them with a - @WxHxB at the end of the string. + gives incorrect information), specify them with a @WxHxB + (and optional :R/G/B masks) at the end of the string. Examples: -rawfb console @@ -16142,6 +16263,7 @@ t -rawfb consolex (no keystrokes or mouse) -rawfb console:/dev/nonstd -rawfb console -pipeinput UINPUT:accel=4.0 + -rawfb vt3 (/dev/tty3 w/o /dev/fb0) VNC HOST: if the -rawfb string is of the form "vnc:host:N" then the VNC display "N" on the remote |