| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
for integration with TQt event loop.
Use tq... includes instead of ntq....
Signed-off-by: Slávek Banko <slavek.banko@axis.cz>
|
|\
| |
| |
| | |
Signed-off-by: Slávek Banko <slavek.banko@axis.cz>
|
| |
| |
| |
| | |
... explaining cedae6e6f97b14f5df3ea7c5f7efd59f2bc9ad82.
|
| | |
|
| |
| |
| |
| | |
clientOutput thread
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
CMakeLists.txt
libvncserver/main.c
|
| |
| |
| |
| |
| |
| |
| |
| | |
Discovered by madscientist159 on 11 Jan 2015:
"noted in testing with the threaded server build, whereby
if newClientHook() returned RFB_CLIENT_ON_HOLD there was no
way to release the hold when the server became ready"
|
| |
| |
| |
| | |
Signed-off-by: Stefan Weil <sw@weilnetz.de>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- When processing input, check if there is any extra data
pending in the internal websocket frame and SSL buffers.
- Prevents input events lagging behind because they get
stuck in one of the buffers.
Data pending in our own buffers cannot be detected with
select() so was not processed until more input arrives
from the network.
- Closes # 55
Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
|
| | |
|
|/
|
|
| |
embedded with krfb
|
|
|
|
| |
compilation
|
|
|
|
|
| |
Krfb crashes on quit, if any client is connected
due to a rfbClientConnectionGone call missing
|
|
|
|
|
|
| |
too.
As done with the RFB sockets, this uses a separate-socket approach as well.
|
|
|
|
|
| |
Without this, we would have gotten a stale IPv4 socket in a race
condition.
|
|
|
|
|
|
|
|
|
| |
This uses a separate-socket approach since there are systems that do not
support dual binding sockets under *any* circumstances, for instance
OpenBSD. Using separate sockets for IPv4 and IPv6 is thus more portable
than having a v6 socket handle v4 connections as well.
Signed-off-by: Christian Beier <dontmind@freeshell.org>
|
| |
|
|
|
|
|
|
|
| |
This is required to be able to do proper event loop integration with Qt.
Idea was taken from vino's libvncserver fork.
Signed-off-by: Christian Beier <dontmind@freeshell.org>
|
|
|
|
|
|
|
| |
This adds generic before/after encoding buffers to the rfbClient
struct, so there is no need for thread local storage.
Signed-off-by: Christian Beier <dontmind@freeshell.org>
|
|
|
|
| |
Signed-off-by: Christian Beier <dontmind@freeshell.org>
|
|
|
|
|
|
|
| |
This implements the xvp VNC extension, which is described in the
community version of the RFB protocol:
http://tigervnc.sourceforge.net/cgi-bin/rfbproto
It is also mentioned in the official RFB protocol.
|
|
|
|
|
|
|
|
|
|
| |
When not calling rfbRegisterProtocolExtension() the extension mutex
is uninitialized but used upon calling rfbGetExtensionIterator() and
rfbReleaseExtensionIterator() in rfbNewTCPOrUDPClient(). This causes
libvncserver to crash on Win32 when building with thread support.
Signed-off-by: Tobias Doerffel <tobias.doerffel@gmail.com>
Signed-off-by: Christian Beier <dontmind@freeshell.org>
|
|
|
|
|
|
|
| |
The header file and most of the functions referred to
do not exist in libvncserver.
Signed-off-by: Christian Beier <dontmind@freeshell.org>
|
|
|
|
|
|
|
| |
If set, this hook gets called just before
rfbSendFrameBufferUpdate() returns.
Signed-off-by: Christian Beier <dontmind@freeshell.org>
|
| |
|
|
|
|
| |
Proposed tight security type fix for debian bug 517422.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There seems to be a locking problem in libvncserver, with respect to how
condition variables are used.
On certain machines in our lab, when using a vncviewer to view a display
that has a very high rate of updates, we will occasionally see the VNC
server process crash. In one stack trace that was obtained, an assertion
had tripped in glibc's pthread_cond_wait, which was called from
clientOutput.
Inspection of clientOutput suggests that WAIT is being called incorrectly.
The mutex that protects a condition variable should always be locked when
calling wait, and on return from the wait will still be locked. The
attached patch fixes the locking around this condition variable, and one
other that I found by grepping the source for similar occurrences.
Signed-off-by: Charles Coffing <ccoffing@novell.com>
|
| |
|
| |
|
| |
|
|
|
|
| |
Both PalmVNC and UltraVNC SetScale messages are supported
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|