3d00472a9c
x11vnc: improve ultravnc filexfer rate by calling rfbCheckFD more often
18 years ago
be2b77f2f2
x11vnc: clear DISPLAY for -unixpw su_verify, user supplied sig ignore.
18 years ago
a60ee2ee9f
RFB 3.8 clients are well informed
19 years ago
6bd995ec77
Better support for RFB >= 3.8 protocols
19 years ago
a75a576e13
All security types for RFB >= 3.7 *have* to respond with a Security Result (Even rfbSecTypeNone)
19 years ago
8417618289
move all types into handler loop.
19 years ago
aa54531107
Security Type memory leak plugged. Leaks when rfb >= 3.7 clients connects.
...
The security list would grow 1 entry when clients connect.
19 years ago
1955526d45
Plugged some memory leakage
19 years ago
2fa31ba4ea
Permit auth.c to test major version
19 years ago
52fb63d51b
Specifically test for Major Version 3 added
19 years ago
b5ab72d65f
Statistics now fit into 80-column output
19 years ago
7039f24f61
Statistics output now fits in 80-column output
19 years ago
0a21bf330c
Corrected Cursor Statistics reporting as messages
19 years ago
bd12b13c91
remove unneeded file
19 years ago
7218843ac0
Support sending TextChat messages back to the client
19 years ago
1c3af68549
Default to RFB 3.8, add command line option to specify the RFB version.
19 years ago
ccdbe8f325
The great UltraVNC Compatibility Commit
19 years ago
347c4a9847
fix some build issues WRT ultravnc code.
19 years ago
0d734ad896
Server Capability Encodings
...
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)"
19 years ago
2670641432
Client Independent Server Side Scaling is now supported
...
Both PalmVNC and UltraVNC SetScale messages are supported
19 years ago
afa9fae024
Ultra Encoding added. Tested against UltraVNC V1.01
19 years ago
3c80351a1c
Make VPATH building work with -I $(top_srcdir) for rfb/rfb.h
19 years ago
1602b345f3
add KeyboardLedState extension
19 years ago
5920dc18d7
SSL patch for Java viewer. https support for x11vnc.
19 years ago
10c61b53c2
ignore maxRectsPerUpdate when encoding is Zlib (thanks scarr)
19 years ago
4130598960
do not timeout on idle client input (with pthreads)
19 years ago
0d40904d9f
rfbCheckFds now returns the number of processed events
19 years ago
f52cfa651b
add handleEventsEagerly flag (Thanks, Donald)
19 years ago
b7773ea6e6
Added method to get extension specific client data
19 years ago
eb08d83d62
Added method to get extension specific client data
19 years ago
d3599be1b8
add functions to unregister extensions/security types
19 years ago
603b5667b6
fix some non-gcc compiler warnings and signals in x11vnc
19 years ago
9b3163c00b
logMutex needs to be initialized too; in rfbDefaultLog.
19 years ago
0b7a0030ac
rfbProcessEvents() has to iterate also over clients with sock < 0 to close them
19 years ago
def3012663
fix client non-jpeg/libz builds
19 years ago
e781eea698
rfbRegisterProtocolExtension extMutex was never initialized.
19 years ago
e673a125df
make compile again with pthreads; fix off-by-one error
19 years ago
1c26789eff
introduce -deferptrupdate (thanks Dave)
19 years ago
1b81e342cb
assorted fixes for MinGW32
19 years ago
3a8d4bdbe6
work around write() returning ENOENT on Solaris 2.7
19 years ago
8eb18f6cd8
fix deadlock from rfbReleaseExtensionIterator(), fix no libz/libjpeg 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.
19 years ago
951ec26b7c
The PseudoEncoding extension code was getting silly:
...
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.
19 years ago
d15e35586b
kill BackChannel and CustomClientMessage: the new extension technique makes these hooks obsolete
19 years ago
60f1770e10
provide a list of the pseudo encodings understood by the extension
19 years ago
808b6a0b23
do it right: it is not DEFINES, but AM_CFLAGS
19 years ago
8490de3ff0
add enablePseudoEncoding() to rfbProtocolExtension
19 years ago
0a909fde7a
This monster commit contains support for TightVNC's file transfer protocol.
...
Thank you very much, Rohit!
19 years ago
93be927b1c
Introduce generic protocol extension method. Deprecate
...
the processCustomClientMessage() method.
19 years ago
94fcd86cc2
Security is global. This was a misguided attempt to evade a global list.
...
I eventually saw the light and went with Rohit´s original approach.
19 years ago
da7b3e714f
support VNC protocol version 3.7
19 years ago
runge
steven_carr
dscho
rohit_99129