COPYING: Replace content with GPL-2 license text, because that is the overall (i.e., strictest) license we have to deal with in nx-libs.

debian/roll-tarball.sh: Rename README.md to README.NX-Development before moving it into doc/ folder.

* bin/{nxagent,nxauth,x2goagent}
* etc/
* doc/nx-X11_vs_XOrg69_patches
* README.keystrokes"
* nx-libs.spec

debian/roll-tarball.sh: Allow patch files names having a dash next to the four digits (i.e., 1234-<patchname>.<suffix>).

 Due to C arithmetic conversion rules we must use an unsigned constant (or a
 cast) to perform the multiplication using unsigned arithmetic.

 Fixes ArcticaProject/nx-libs#55.

 Author: Emanuele Giaquinta <emanuele.giaquinta@gmail.com>
Reviewed-by: Jeremy Huddleston <jeremyhu@apple.com>
 Rebased against NX: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Attributes GH PR #43: https://github.com/ArcticaProject/nx-libs/pull/43

Attributes GH PR #42: https://github.com/ArcticaProject/nx-libs/pull/42

Attributes GH PR #41: https://github.com/ArcticaProject/nx-libs/pull/41

Library clean-up: Drop libxkbui, has been built previously but none of its symbols have been used in NX.

Attributes GH PR #40: https://github.com/ArcticaProject/nx-libs/pull/40

imake clean-up: Enforce build of Mesa GLX extension. Drop all other GLX build methods (built-in DRI drivers, etc.).

* MS Windows (non-tested)
* Mac OS X (not provided)
* SGISI / opengl (not provided)
* DRI support (nxagent uses Mesa software emulation only)

 The client-side library libNX_GL.{a,so} is not built when building nx-libs.

 However, nx-X11/lib/GL/** ships several imake include files
 (Imakefile.inc) that are also used in nx-X11/programs/Xserver/GL/**.
 These files have been moved from the nx-X11/lib/GL/ code subtree to the
 nx-X11/programs/Xserver/GL/.

 Furthermore, we don't provide module builds of the GL extension anymore,
 as that feature is neither used in nx-libs.

Fix negotiation in stage 10 error.

Attributes GH PR #39: https://github.com/ArcticaProject/nx-libs/pull/39

* Unix file socket support -> 3.6.x
* Embedding / re-parenting -> 3.6.x

Xext CVE fixes in XVideo extension.

DIX CVE fixes in nx-X11/programs/Xserver/hw/nxagent/ rather than nx-X11/programs/Xserver/dix/.

v2: backport to nx-libs 3.6.x (Mike DePaulo)
v3: port to NXxvdisp.c rather than xvdisp.c (Mike DePaulo)
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>

Conflicts:
	Xext/xvdisp.c

 The length checking code validates PutImage height and byte width by
 making sure that byte-width >= INT32_MAX / height. If height is zero,
 this generates a divide by zero exception. Allow zero height requests
 explicitly, bypassing the INT32_MAX check.

 Fix for regression introduced by fix for CVE-2014-8092.

 v2: backports to nx-libs 3.6.x (Mike Gabriel)
 v3: port to NXdispatch.c rather than dispatch.c (Mike DePaulo)
Signed-off-by: Keith Packard <keithp@keithp.com>

ProcPutImage() calculates a length field from a width, left pad and depth
specified by the client (if the specified format is XYPixmap).

The calculations for the total amount of memory the server needs for the
pixmap can overflow a 32-bit number, causing out-of-bounds memory writes
on 32-bit systems (since the length is stored in a long int variable).

v2: backport to nx-libs 3.6.x (Mike DePaulo)
v3: port to NXdispatch.c rather than dispatch.c (Mike DePaulo)
Reported-by: Ilja Van Sprundel <ivansprundel@ioactive.com>
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>

Conflicts:
	dix/dispatch.c

Avoid use-after-free in dix/dixfonts.c: doImageText() [CVE-2013-4396] from xorg/Xserver http://lists.x.org/archives/xorg-announce/2013-October/002332.html

Save a pointer to the passed in closure structure before copying it
and overwriting the *c pointer to point to our copy instead of the
original.  If we hit an error, once we free(c), reset c to point to
the original structure before jumping to the cleanup code that
references *c.

Since one of the errors being checked for is whether the server was
able to malloc(c->nChars * itemSize), the client can potentially pass
a number of characters chosen to cause the malloc to fail and the
error path to be taken, resulting in the read from freed memory.

Since the memory is accessed almost immediately afterwards, and the
X server is mostly single threaded, the odds of the free memory having
invalid contents are low with most malloc implementations when not using
memory debugging features, but some allocators will definitely overwrite
the memory there, leading to a likely crash.

v2: Apply to NXdixfonts.c rather than dixfonts.c (Mike DePaulo)