We don't know the size of the output buffer here and giving the input
string size is just confusing and upsets the compiler in some cases.

This is what display managers do, so it is expected by many
environments.

We terminated the child instead of the parent after fork().

Reported by Jan Grulich from Red Hat.

This was already handled for most exit conditions, but not the early
ones.

Mainly fixes for Japanese and Korean keyboard layouts.

Not sure how this has changed, but ImageMagick is now using the first
-size to also determine how to scale the SVGs, which is not what we
want.

Anything else is excessive.

Each character is more than one byte, so adjust the clearing of the
buffer to reflect that.

Some code points are reserved for the UTF-16 coding itself and must not
appear as input data to the algorithm.

Signed bug prevented anything not ASCII from being coded correctly.

Everything outside of BMP was handled incorrectly and was coded as
completely different code points.

This would mess up most conversions from UTF-8 as the caller wouldn't
know how far to step to get to the next valid character, resulting in
markers for invalid data to be injected here and there.

Also add some unit tests to avoid this reoccurring.

It is now dynamically generated, so it will be in the build directory
and not in the source directory.

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.

Refer @CMAKE_INSTALL_FULL_SYSCONF@ instead.

Like the native viewer, the Java viewer didn't store certificate
exceptions properly. Whilst not as bad as the native viewer, it still
failed to check that a stored certificate wouldn't be maliciously used
for another server. In practice this can in most cases be used to
impersonate another server.

Handle this like the native viewer by storing exceptions for a specific
hostname/certificate combination.

Not sure why this got in there, but it is incorrect as it results in
creating files with too liberal permissions.

Update Surface_X11.cxx

Runtime sellection of ARGB  XImage byte order

For some reason it got generated at an incorrect 20x20 size last time.

It should be using the safe wrappers for everything so make sure it
cannot bypass those and call the SConnection methods directly.

We incorrectly called the underlying functions instead of the safe
wrappers for the new clipboard functions. This had the effect of a)
crashing the entire server if one of these functions failed, and b) not
respecting the settings disabling the clipboard.

With this commit, TigerVNC will compile for Windows using MSYS2, MinGW-w64 and Inno Setup 6.  The resulting binaries have some dll dependencies (even with BUILD_STATIC).  The required dll dependencies are not included in the installer.

Unfortunately, the latest version of MSYS2 and MinGW-w64 do not produce a working executable for Windows 7.

This line affects every command run by the user, unlike everything else
in our policy which is just for vncserver/vncsession. It's easy to miss
this so add a comment pointing it out.

We handled this in the failure scenario, but not in the vastly more
common successful case.

If InnoSetup is run on a case sensitive system then the configuration
files must match what the file is actually called.

Allow vnc session labeled with SELinux vnc_session_t domain to create
directory in user homedir ~/.vnc labeled with SELinux label xdm_home_t.

Because also process vncpasswd creates ~/.vnc directory, file transition that
userdomain attribute SELinux domain (label for the process) can create the
directory with the same label needs to be added.

userdomain attribute contains following SELinux types:
    auditadm_t
    dbadm_t
    guest_t
    logadm_t
    secadm_t
    staff_t
    staff_wine_t
    sysadm_t
    unconfined_t
    user_t
    user_wine_t
    webadm_t
    xguest_t

Signed-off-by: Lukas Vrabec <lvrabec@redhat.com>

EL 7 tigervnc.spec updates