aboutsummaryrefslogtreecommitdiffstats
path: root/unix/xserver/hw/vnc
Commit message (Collapse)AuthorAgeFilesLines
...
* | Improve log message when mapping keysymsPierre Ossman2023-08-231-1/+1
| | | | | | | | | | | | | | | | | | | | It was a poor choice of words to call these keysyms "unknown" as they are likely perfectly normal keysyms, they just cannot be found in the currently loaded keyboard layout. This log message has confused users, so let's get rid of the "unknown" part. We already use the verb "add" heavily in the other log messages, so let's keep that rather than switch to some for of "map".
* | Update copyright year to 2023Samuel Mannehed2023-07-201-1/+1
|/
* Clean up string encoding handlingPierre Ossman2023-06-303-0/+16
| | | | | | We should handle this in the low-level protocol code as much as possible to avoid mistakes. This way the rest of the code can assume that strings are always UTF-8 with \n line endings.
* Use standard C string functionsPierre Ossman2023-02-043-14/+7
| | | | It's just confusing that we have our own variety that isn't compatible.
* Use std::string instead of CharArrayPierre Ossman2023-02-043-6/+7
| | | | | Let's use a more common type instead of something homegrown. Should be more familiar to new developers.
* Return std::string instead of dynamic allocationsPierre Ossman2023-02-042-18/+7
| | | | | | We mostly use classical C strings, but the memory management around them can get confusing and error prone. Let's use std::string for the cases where we need to return a newly allocated string.
* Return static char buffer from some methodsPierre Ossman2023-02-041-1/+1
| | | | | | | | | This mimics how some system functions (like inet_ntop()) work, and avoids complexity around ownership of the returned string buffer. The downside is that the string must be consumed directly as it will be overwritten on the next call, but that is not an issue with the current usage.
* Use StringParameters directlyPierre Ossman2023-02-041-3/+1
| | | | | We don't need to make extra copies of the string in most cases, so let's simplify the code and access the string directly when we can.
* Use stdint typesPierre Ossman2023-02-012-10/+10
| | | | | Avoid having our own custom stuff and instead use the modern, standard types, for familiarity.
* Use __attribute__:s directlyPierre Ossman2023-01-052-19/+11
| | | | | | These are supported by gcc and clang, and I don't think MSVC works well with our code anyway, so let's keep things simple and use these directly.
* Change development version to 1.13.80Pierre Ossman2022-12-151-1/+1
|
* Don't enable RSA-AES by default in serversPierre Ossman2022-10-141-1/+1
| | | | | | These require a key to have been set up on the server beforehand, so they do not give a good default experience as clients will be unable to connect.
* Fix SecurityTypes default value in man pagesPierre Ossman2022-09-011-1/+1
| | | | | The order is important in the servers, so make sure the man pages follow the code properly.
* Add support for RSA-AES security typespdlan2022-09-011-2/+12
|
* Fix typo in previous commitPierre Ossman2022-07-051-1/+1
|
* Fix Xvnc dependency list (again)Pierre Ossman2022-07-051-3/+8
| | | | | | | | | The previous commit was incorrect in that it overrides automake's dependency list, rather than adding to it. So we need to make sure things are duplicated between Xvnc_DEPENDENCIES and Xvnc_LDADD as appropriate. Use the same approach as the Xorg binary to keep things familiar.
* Add missing dependencies for XvncPierre Ossman2022-07-041-0/+1
| | | | | | These aren't crucial for a clean build, but must be set for Xvnc to be properly rebuilt if anything in the Xorg tree changes. automake doesn't properly deduce these automatically from Xvnc_LDADD, unfortunately.
* Improve logging around screen resizingPierre Ossman2022-01-251-6/+0
| | | | | | Avoid duplication, and add logging for some more error conditions so it's possible to see in the logs why a resize has failed or produced unexpected results.
* Update copyright year to 2022Pierre Ossman2022-01-051-1/+1
|
* Be consistent in including config.hPierre Ossman2021-12-303-0/+12
| | | | | | The generally recommended way is to include it from source files, not headers. We had a mix of both. Let's try to be consistent and follow the recommended way.
* xvnc: adapt for 1.21Joakim Tjernlund2021-11-241-4/+2
| | | | | VENDOR_STRING is gone as is DEFAULT_LOG_VERBOSITY site.h has been removed and is not needed.
* xorg-version.h: Increase supported Xorg version to 1.21Joakim Tjernlund2021-11-241-2/+2
|
* Fix formatting of -rfbport in man pagesPierre Ossman2021-11-091-2/+2
|
* Change development version to 1.12.80Pierre Ossman2021-09-081-1/+1
|
*---. Merge branches 'host-name-max', 'fix-build-viewer-off' and ↵Pierre Ossman2021-07-237-22/+17
|\ \ \ | | | | | | | | | | | | 'fix-case-insensitive-fs' of https://github.com/arichardson/tigervnc
| | | * Rename Input.h to vncInput.h to fix building on case-insensitive FSAlex Richardson2021-07-156-9/+8
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I am cross-compiling from macOS for a FreeBSD-derived system so my host file system is case insensitive but the target isn't. Without this change I get the following warnings which show that the vnc "Input.h" is being included from mi/mi.h instead of the xserver "input.h": ``` In file included from /Users/alex/cheri/xvnc-server/hw/vnc/Input.c:33: /Users/alex/cheri/xvnc-server/mi/mi.h:55:10: warning: non-portable path to file '"Input.h"'; specified path differs in case from file name on disk [-Wnonportable-include-path] #include "input.h" ^~~~~~~~~ "Input.h" ```
| * / Fix build on systems without HOST_NAME_MAXAlex Richardson2021-07-151-13/+9
| |/ | | | | | | | | | | Some operating systems such as FreeBSD don't define a HOST_NAME_MAX macro. The portable approach to determine the real host name limit is calling sysconf(_SC_HOST_NAME_MAX) so do that instead.
* / Keep ownership of second selection when first is lostPierre Ossman2021-07-201-9/+61
|/ | | | | | | | | | | | | | This fixes regression introduced by the extended clipboard extension. Previously it was possible for the server to hold on to the CLIPBOARD selection even if another application took ownership of PRIMARY. This is important to handle the common use case of selecting something in order to paste over it. The new request based model doesn't readily support this as we assume the client has lost its data once we push the new PRIMARY selection to it. So to handle this we have the maintain a cache of the client's data, and make sure to fill that cache before we do anything that might cause the client to lose the data.
* Merge branch 'utilize-system-wide-crypto' of https://github.com/grulja/tigervncPierre Ossman2021-07-141-1/+3
|\
| * Utilize system-wide crypto policiesJan Grulich2021-07-141-1/+3
| |
* | Remove vfb references from symbol namesPierre Ossman2021-07-134-69/+69
| | | | | | | | | | | | Xvnc was originally based on Xvfb, but it's just confusing to keep the names. So change all prefix to "vnc" instead to clearly mark things as part of TigerVNC.
* | Remove zaphod mode from XvncPierre Ossman2021-07-131-164/+64
| | | | | | | | | | It isn't really useful as it behaves just like starting multiple servers, so remove it in favour of keeping things simple.
* | Remove undocumented -linebias argumentPierre Ossman2021-07-131-26/+0
| | | | | | | | | | This is a development flag with no real use, so remove it to clean up the code.
* | Clean up Xvnc screen structPierre Ossman2021-07-131-18/+6
| | | | | | | | | | Remove stuff we don't use, and get it more in sync with Xvfb for easier comparison.
* | Remove unused headersPierre Ossman2021-07-131-8/+1
| |
* | Remove obsolete AIX hackPierre Ossman2021-07-131-5/+0
| |
* | Remove obsolete comment about backing storePierre Ossman2021-07-131-5/+0
| | | | | | | | This was removed years ago.
* | Remove CloseScreen() wrapperPierre Ossman2021-07-131-22/+0
| | | | | | | | The memory leak this worked around was fixed in X.org 1.16.
* | Do all RandR init in vncRandRInit()Pierre Ossman2021-07-131-20/+15
| | | | | | | | | | | | | | Keep everything in one place to make it easier to read. This also removes the call to RRInit() as that is done implicitly anyway.
* | Use central SetRootClip()Pierre Ossman2021-07-131-90/+4
| | | | | | | | | | There's been a common one since X.org 1.11, so use that instead of our own copy.
* | Remove Darwin code from XvncPierre Ossman2021-07-131-22/+0
| | | | | | | | | | We don't build for that platform anyway, so this is just a remnant from Xvfb.
* | Handle X.org patch level featuresPierre Ossman2021-07-136-40/+41
| | | | | | | | | | | | With the 1.20.x releases there has been features and API changes even on patch level versions, so we need to update our macros to handle these as well.
* | Remove shared memory framebuffer optionPierre Ossman2021-07-131-77/+3
| | | | | | | | | | This is a pointless remnant of Xvfb. We never print the id of the shared memory, so no other application can access this memory anyway.
* | Remove more color map code from XvncPierre Ossman2021-07-131-151/+0
| | | | | | | | | | This hasn't been supported or used in many years, so clean out the final remnants.
* | Remove DDXTIME codePierre Ossman2021-07-131-11/+0
| | | | | | | | This hasn't been used since xorg-server 1.1 so get rid of it.
* | Call FatalError() on bad Xvnc argumentsPierre Ossman2021-07-131-6/+12
| | | | | | | | This is consistent with other ddx behaviour.
* | Use CHECK_FOR_REQUIRED_ARGUMENTS() for arg checkPierre Ossman2021-07-131-15/+15
| | | | | | | | | | This is what all the other ddx variants use, so do the same in Xvnc to be consistent.
* | Apply Xorg coding style to xvnc.cPierre Ossman2021-07-131-560/+567
| | | | | | | | | | Makes it easier to compare with upstream files as the formatting will be the same.
* | Remove #ifdef RENDERPierre Ossman2021-07-132-22/+0
| | | | | | | | | | RENDER has been mandatory since xorg-server 1.9, so remove these checks.
* | Move ddxInputThreadInit() to xvnc.cPierre Ossman2021-07-132-9/+9
| | | | | | | | | | This should only be in the ddx parts of an X server, and Input.c is used by libvnc.so as well and can cause conflicts there.
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-09 20:07:40 +0000