runge
|
11a5ea9ff9
|
fix typo.
|
18 years ago |
steven_carr
|
a60ee2ee9f
|
RFB 3.8 clients are well informed
|
19 years ago |
|
steven_carr
|
6bd995ec77
|
Better support for RFB >= 3.8 protocols
|
19 years ago |
|
steven_carr
|
a75a576e13
|
All security types for RFB >= 3.7 *have* to respond with a Security Result (Even rfbSecTypeNone)
|
19 years ago |
|
runge
|
8417618289
|
move all types into handler loop.
|
19 years ago |
|
steven_carr
|
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 |
|
steven_carr
|
52fb63d51b
|
Specifically test for Major Version 3 added
|
19 years ago |
|
steven_carr
|
ccdbe8f325
|
The great UltraVNC Compatibility Commit
|
19 years ago |
dscho
|
d3599be1b8
|
add functions to unregister extensions/security types
|
19 years ago |
|
runge
|
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 |
|
dscho
|
0a909fde7a
|
This monster commit contains support for TightVNC's file transfer protocol.
Thank you very much, Rohit!
|
19 years ago |
|
dscho
|
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 |
|
dscho
|
da7b3e714f
|
support VNC protocol version 3.7
|
19 years ago |
|
dscho
|
8bee4eb990
|
ANSIfy, fix some warnings from Linus' sparse
|
20 years ago |
|
dscho
|
97299606da
|
global structures/functions should have "rfb", "sra" or "zrle" as prefix,
while structure members should not
|
20 years ago |
|
dscho
|
876868553d
|
move the library into libvncserver/, x11vnc into x11vnc/
|
21 years ago |
