| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The previous FIXME was incorrect. The old code did in fact continue
looking over the entire area. This commit restores that old behaviour.
|
| |
| |
| |
| | |
It knows more details so it can track things better.
|
| |
| |
| |
| |
| | |
It had regressed in performance compared to 1.3. This brings it back
up to the same speed.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The only class that cares if connections are reversed or not is
VNCSConnectionST so let it keep track of this fact.
|
| | |
|
| |
| |
| |
| | |
Needed for some tests.
|
| | |
|
|/
|
|
|
| |
On some platforms va_list might be defined as something that causes
ambiguity and results in the wrong function being called.
|
| |
|
|
|
|
|
| |
It just adds noise and you can't really tell which timer it is
anyway without more logging in other places.
|
|
|
|
|
|
|
|
| |
The internal Xorg headers are very incompatible with C++ and we've had
to resort to all kinds of hacks in order to include them in our C++
code. This approach isn't really viable long term so restructure things
so that we have a glue layer written in C that bridges the Xorg core
with the RFB classes.
|
| |
|
|
|
|
|
|
| |
Both SSecurityVeNCrypt and SSecurityStack are wrappers around other
security objects, so they need to delegate the properties of those
sub-objects properly.
|
|
|
|
|
|
| |
A read-only client should not be allowed to kick out other clients.
It will be forced into shared mode, or refused the connection, depending
on the neverShared parameter.
|
|\
| |
| |
| | |
into viewonly
|
| | |
|
| |
| |
| |
| | |
So clients with limited access rights can not affect it.
|
| |
| |
| |
| |
| | |
Try to read second password (for read only access) from rfbauth file. If client
sent second password instead of first one, allow him read only access.
|
| |
| |
| |
| |
| |
| |
| | |
SConnection has AccessRights property that specifies what connected client can
do. Set this property to value given by SSecurity after successful
authentication. This way individual SSecurity subclasses can accept clients but
restrict their access.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 39d7dc043afcf6f94b9c16942765fdb9a6a3202e.
We should be secure by default, even if it might cause a performance
hit. Those who wish to make that trade off are more likely to notice
the lack of performance than others noticing the lack of security.
|
|/
|
|
|
| |
It's often useful to see if encryption was used, and how the user
authenticated (if at all).
|
| |
|
|
|
|
|
| |
We don't even log this much for RFB protocol stuff, and it makes
it very annoying to run with full debugging on.
|
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
This was just plain wrong, so redo it properly.
|
| |
|
| |
|
|
|
|
|
|
| |
Having it in ConnParams made the linker pull all the encoder objects
into vncviewer, making it larger than necessary and giving it extra
parameters in its help output that weren't relevant.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This allows us to apply a lot more server logic
independently of which encoder is in use.
Most of this class are things moved over from the
Tight encoder.
|
|
|
|
| |
There is nothing using these classes anymore, so remove the clutter.
|
|
|
|
|
|
|
| |
This avoid a lot of unnecessary middle men. This also pushes the
responsibility for pixel format conversion into the encoders and
decoders. The new bufferFromBuffer() is used for direct conversion,
rather than PixelTransformer/TransImageGetter.
|
|
|
|
|
|
| |
Like we do for everything else. This also gets rid
of the callback, which is a bit out of place
compared to everything else.
|
| |
|
|
|
|
|
|
| |
Add a magical cursor framebuffer class for handling when you
want to render the cursor on the server side. Keeps the cursor
specific magic in one contained place.
|
| |
|
|
|
|
|
| |
Allows you to modify the buffer with data in a
different pixel format.
|
|
|
|
|
|
|
|
|
| |
Handles the common cases when the target or source are in
the preferred 888 format.
If one of the buffers is not 888, then it must also be properly
aligned (which is commonly the case). Performance is now in many
cases on par with PixelTransformer.
|
|
|
|
|
| |
This is a lot easier and cheaper than having to set up a complete
PixelTransformer object.
|
|
|
|
|
|
| |
You have to loop many times when converting e.g. 2 bits to 8,
so have a couple of lookup tables to speed things up. We still
use bit replication to get from 8 bits to 16 bits though.
|
|
|
|
|
| |
Allows pixel buffers that do damage tracking to get
proper information.
|
|
|
|
|
| |
Clearly separates the read API from the write API
and also from actual implementation.
|