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.

(cherry picked from commit f029745f63)

This makes our builds directly compatible with most distributions
without packagers/users having to specify extra flags.

Commit 4e61f8dbc5 fixed the GUI but forgot
to change the other places in the code.

There was even some confusion in the RFB protocol regarding this, but
the zlib implementation confirms that accepted values for compression
level is 0-9.

The GUI incorrectly noted the max level to be 6 while it in fact is 9.

Even if this note is true it just adds confusion.

The number of colors used isn't something the end-users should have to
concern themselves with. I intentionally left the information in the
man-pages.

because it is not only platform independent
but also allows to override the build date
This helps to make tigervnc builds reproducible

See https://reproducible-builds.org/ for why this is good

Also adds UTC flag, to be independent of timezone.
Also changes JAVA_DATE format to ISO-8601 date format.

Requires cmake-2.8.11+ from 2013

Our main web site now supports https, so update all references.

Applets don't work anymore so remove everything that has to do
with serving them.

Ensure queueMutex is always correctly released by using finally blocks. This is the closest approximation of AutoMutex style automatic release you can get in Java.

The user can specify a tigervnc configuration file as an argument to the
viewer. Previously the viewer assumed this to be a server, but now we
will first check if there is any file matching the given argument. If
so, try to load the content of that file, like we normally do.

Fixes issue #38.

Fixes issue #616

Menukey was broken by recent refactoring of OptionsDialog

Various errors exposed when connecting to RealVNC servers
on alternative platforms (ARM, SPARC).  SSLEngineManager
was also cleaned up but most of the changes are cosmetic.

See issue #534

Changes to keyboard handling require methods from the KeyEvent
class that were not introduced until Java 7.

Java L&F has pre-defined hook that transfers the focus to the
menu of the RootPane.  Since the viewer doesn't have a menu
this just causes a loss of focus and subsequent unexpected
behavior of keyboard and mouse.

See issue #505

Need to be careful with escapes though.