tigervnc.git - High performance, multi-platform VNC client and server: https://github.com/TigerVNC/tigervnc

	Commit message (Collapse)	Author	Age	Files	Lines
*	Make Xvnc and x0vncserver pass the display name to PAM modules.	Carlos Santos	2025-06-13	1	-0/+2
\| \| \| \| \| \|	Fixes: https://issues.redhat.com/browse/RHEL-34880 Signed-off-by: Carlos Santos <casantos@redhat.com>
*	Remove Xvnc manual bool param check	Pierre Ossman	2025-06-11	1	-1/+0
\| \| \| \| \|	This was supposed to be removed in e97e225 when we moved this to the core library.
*	Consolidate argument parsing in single function	Pierre Ossman	2025-01-10	1	-1/+2
\| \| \| \| \|	Avoid duplicating this complexity everywhere and make sure all commands get the same handling and fixes.
*	Clean up string encoding handling	Pierre Ossman	2023-06-30	1	-0/+2
\| \| \| \| \| \|	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 functions	Pierre Ossman	2023-02-04	1	-2/+0
\| \| \| \|	It's just confusing that we have our own variety that isn't compatible.
*	Use __attribute__:s directly	Pierre Ossman	2023-01-05	1	-10/+8
\| \| \| \| \| \|	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.
*	Tolerate specifying -BoolParam 0 and similar	Pierre Ossman	2020-09-18	1	-0/+1
\| \| \| \| \| \|	This is needed by vncserver which doesn't know which parameters are boolean, and it cannot use the -Param=Value form as that isn't tolerated by the Xorg code.
*	Add UTF-8 to/from ISO 8859-1 conversion routines	Pierre Ossman	2019-07-01	1	-0/+4
\| \| \| \| \|	We convert between UTF-8 and ISO 8859-1 (latin 1) in several places so create some common routines for this.
*	Make sure clipboard uses \n line endings	Pierre Ossman	2019-07-01	1	-1/+4
\| \| \| \| \| \|	This is required by the protocol so we should make sure it is enforced. We are tolerant of clients that violate this though and convert incoming clipboard data.
*	Restructure Xvnc/libvnc.so code to avoid C++ header hacks	Pierre Ossman	2015-01-26	1	-0/+56
	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.