We now filter incoming data, which means we can start assuming the
clipboard data is always null terminated. This allows us to clean
up a lot of the internal handling.

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.

We will log the exception, so avoid direct writes to stderr by
simply removing these log lines.

Some input sources are still using input methods even though they
claim to be "ASCII" input. This causes our input handling to fail
since we need to query the layout to handle dead keys.

Fortunately there is another API to get the raw, underlying input
source that the input method uses. So let's use that and be sure
that we're always getting something we can use.

There is some bug in gcc's new -Werror=format-overflow that makes it
think majorVersion could end up being very large. Increase the target
buffer for now to keep gcc happy.

The parameter files are used to make sure changes in the UI are
persistent. Storing anything else results in behaviours that the
user has no easy way of changing.

It is already hidden in the UI, so make sure it also is gone as a
command line parameter. This follows the behaviour of the similar
sendPrimary parameter.

This provides some basic rate limiting that will make it difficult
for an attacker to brute force passwords. Only relevant when the
blacklist is disabled as otherwise the attacker only gets a very
limited number of attempts.

We need to make sure it is null terminated on truncation. We also
need to avoid giving a too large size argument or modern gcc will
complain.

It is not enough to create an exception object, you need to throw
it as well.

It's not common knowledge these days how X geometry is specified, and
even the man page X(7) is missing on many systems now.

FLTK has some options (that we've also documented in the man page)
that should be mentioned in the --help output.

We can use a dummy value here as we set up the buffer and stride
further down in the constructor.

There might be multiple clients using a single IP (e.g. NAT), which
can make the blacklist do more harm than good. So add a setting to
disable it if needed.

No need to expose these, so keep them internal to the implementation,
like most settings are.

We always sync when we get focus, so this code path is really only
for when the server announces LED state support after we already
have focus.

Make sure we only handle this specific scenario as otherwise we
could end up syncing twice, which just toggles things back and forth
and ends up syncing incorrectly.

This is where to install headers to, not where to find headers to
build against. Toolchains should know where to locate their system
headers while non-system headers should be found using
pkg-config. Users with bizarre setups where the toolchain really
cannot find the system headers should set CPPFLAGS.

Travis wants "cpp", not "c++". It just happened to work anyway
because the base image includes the same tools.

It has a current GnuTLS and FLTK which simplifies the build.

Make the builds faster as we now run them often via Travis.

Remove the unused Java self sign variable, and make sure we don't
hard code a version as it needs to be adjusted before a build.

libXft is needed to build FLTK for the RHEL 6 RPM.

The supporting scripts weren't really up to date, so remove them
and just require the packager to include FLTK in the source
tarball.

It is needed by x0vncserver.

It is needed to build Xvnc.

They include a new enough version, so stop doing our own build.

Patch originally by @KenMilmore on GitHub.

Packages for RHEL 5 and Ubuntu 12.04 are no longer maintained, so
remove those files.

These are for ancient versions of FLTK and are not needed in the
versions required by us.

The contributed script uses bash features extensively and does not work with ksh.

Two minor issues:

This script is written in python two which is depreciated, and should be rewritten in python three, but I have so far been successful in not learning python. :-) to simplify debugging I have clarified that it needs a python two interpreter.

This script downloads an old version of mesa (an update may be appropriate),  unfortunately the release candidate previously specified is no longer available, so an update to the next released version was made.

Modern fontconfig needs it, so make sure it is included.

Add basic templates for users to follow so that we get the information
we need directly in the initial report.