summaryrefslogtreecommitdiffstats
path: root/libvncserver
Commit message (Collapse)AuthorAgeFilesLines
...
* RFB 3.8 clients are well informedsteven_carr2006-06-052-9/+30
|
* Better support for RFB >= 3.8 protocolssteven_carr2006-06-051-22/+43
|
* All security types for RFB >= 3.7 *have* to respond with a Security Result ↵steven_carr2006-06-051-1/+9
| | | | (Even rfbSecTypeNone)
* move all types into handler loop.runge2006-06-031-10/+9
|
* Security Type memory leak plugged. Leaks when rfb >= 3.7 clients connects.steven_carr2006-05-291-5/+9
| | | | The security list would grow 1 entry when clients connect.
* Plugged some memory leakagesteven_carr2006-05-287-3/+85
|
* Permit auth.c to test major versionsteven_carr2006-05-161-0/+1
|
* Specifically test for Major Version 3 addedsteven_carr2006-05-161-1/+2
|
* Statistics now fit into 80-column outputsteven_carr2006-05-161-4/+4
|
* Statistics output now fits in 80-column outputsteven_carr2006-05-161-67/+85
|
* Corrected Cursor Statistics reporting as messagessteven_carr2006-05-161-2/+2
|
* remove unneeded filedscho2006-05-151-15/+0
|
* Support sending TextChat messages back to the clientsteven_carr2006-05-151-0/+41
|
* Default to RFB 3.8, add command line option to specify the RFB version.steven_carr2006-05-153-5/+30
|
* The great UltraVNC Compatibility Commitsteven_carr2006-05-1515-229/+1426
|
* fix some build issues WRT ultravnc code.runge2006-05-135-3494/+3499
|
* Server Capability Encodingssteven_carr2006-05-041-3/+277
| | | | | | | rfbEncodingSupportedEncodings - What encodings are supported? rfbEncodingSupportedMessages - What message types are supported? rfbEncodingServerIdentity - What is the servers version string? ie: "x11vnc: 0.8.1 lastmod: 2006-04-25 (LibVNCServer 0.9pre)"
* Client Independent Server Side Scaling is now supportedsteven_carr2006-05-0314-64/+580
| | | | Both PalmVNC and UltraVNC SetScale messages are supported
* Ultra Encoding added. Tested against UltraVNC V1.01steven_carr2006-05-026-6/+3745
|
* Make VPATH building work with -I $(top_srcdir) for rfb/rfb.hrunge2006-04-262-2/+2
|
* add KeyboardLedState extensiondscho2006-03-282-2/+68
|
* SSL patch for Java viewer. https support for x11vnc.runge2006-03-281-1/+5
|
* ignore maxRectsPerUpdate when encoding is Zlib (thanks scarr)dscho2006-03-271-0/+2
|
* do not timeout on idle client input (with pthreads)dscho2006-03-011-0/+16
|
* rfbCheckFds now returns the number of processed eventsdscho2006-02-281-10/+13
|
* add handleEventsEagerly flag (Thanks, Donald)dscho2006-02-282-82/+88
|
* Added method to get extension specific client datarohit_991292006-02-241-1/+1
|
* Added method to get extension specific client datarohit_991292006-02-242-34/+37
|
* add functions to unregister extensions/security typesdscho2006-02-223-9/+127
|
* fix some non-gcc compiler warnings and signals in x11vncrunge2006-02-205-1/+11
|
* logMutex needs to be initialized too; in rfbDefaultLog.runge2006-01-111-2/+12
|
* rfbProcessEvents() has to iterate also over clients with sock < 0 to close themdscho2006-01-102-3/+19
|
* fix client non-jpeg/libz buildsrunge2006-01-081-1/+1
|
* rfbRegisterProtocolExtension extMutex was never initialized.runge2006-01-061-0/+6
|
* make compile again with pthreads; fix off-by-one errordscho2005-12-221-2/+4
|
* introduce -deferptrupdate (thanks Dave)dscho2005-12-193-4/+43
|
* assorted fixes for MinGW32dscho2005-12-193-15/+20
|
* work around write() returning ENOENT on Solaris 2.7dscho2005-12-091-0/+3
|
* fix deadlock from rfbReleaseExtensionIterator(), fix no libz/libjpeg ↵runge2005-11-259-16/+30
| | | | builds, disable tightvnc-filetransfer if no libpthread, add --without-pthread option, rm // comments, set NAME_MAX if not defined, x11vnc: throttle load if fb update requests not taking place.
* The PseudoEncoding extension code was getting silly:dscho2005-10-071-4/+2
| | | | | | | | | | | | | | | | | | | | If the client asked for an encoding, and no enabled extension handled it, LibVNCServer would walk through all extensions, and if they promised to handle the encoding, execute the extension's newClient() if it was not NULL. However, if newClient is not NULL, it will be called when a client connects, and if it returns TRUE, the extension will be enabled. Since all the state of the extension should be in the client data, there is no good reason why newClient should return FALSE the first time (thus not enabling the extension), but TRUE when called just before calling enablePseudoEncoding(). So in effect, the extension got enabled all the time, even if that was not necessary. The resolution is to pass a void** to enablePseudoEncoding. This has the further advantage that enablePseudoEncoding can remalloc() or free() the data without problems. Though keep in mind that if enablePseudoEncoding() is called on a not-yet-enabled extension, the passed data points to NULL.
* kill BackChannel and CustomClientMessage: the new extension technique makes ↵dscho2005-10-064-52/+1
| | | | these hooks obsolete
* provide a list of the pseudo encodings understood by the extensiondscho2005-10-062-4/+38
|
* do it right: it is not DEFINES, but AM_CFLAGSdscho2005-10-061-1/+1
|
* add enablePseudoEncoding() to rfbProtocolExtensiondscho2005-10-032-8/+25
|
* This monster commit contains support for TightVNC's file transfer protocol.dscho2005-09-2817-19/+2974
| | | | Thank you very much, Rohit!
* Introduce generic protocol extension method. Deprecatedscho2005-09-274-10/+103
| | | | the processCustomClientMessage() method.
* Security is global. This was a misguided attempt to evade a global list.dscho2005-09-272-7/+8
| | | | I eventually saw the light and went with Rohit´s original approach.
* support VNC protocol version 3.7dscho2005-09-263-21/+212
|
* x11vnc: -gui tray mode, httpd.c: check httpListenSock >= 0.runge2005-07-021-0/+3
|
* main.c: fix screen->deferUpdateTime default.runge2005-06-271-3/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-14 22:17:42 +0000