Fix binary incompatibility between openssl versions

OpenSSL changed the layout of X509_STORE_CTX between 0.9 and 1.0
So we have to consider this struct as private implementation, and use
the access functions instead.

This bug would cause certificate verification problems if a different
version of openssl is loaded at runtime to the headers Qt was compiled
against.

Task-number: QTBUG-28343
Change-Id: I47fc24336f7d9c80f08f9c8ba6debc51a5591258
Reviewed-by: Richard J. Moore <rich@kde.org>
(cherry picked from commit eb2688c4c4f257d0a4d978ba4bf57d6347b15252)

Gbp-Pq: Name Fix_binary_incompatibility_between_openssl_versions.patch

SSL certificates: blacklist mis-issued Turktrust certificates

Those certificates have erroneously set the CA attribute to true,
meaning everybody in possesion of their keys can issue certificates on
their own.

backport of bf5e7fb2652669599a508e049b46ebd5cd3206e5 from qtbase

Task-number: QTBUG-28937
Change-Id: Iee57c6f983fee61c13c3b66ed874300ef8e80c23
Reviewed-by: Richard J. Moore <rich@kde.org>
Gbp-Pq: Name SSL-certificates-blacklist-mis-issued-Turktrust-cert.patch

Make the rules for redirects a bit stricter.

Change-Id: I7a3cec664aa028202de3d3bda9f499e4deb2998d

Gbp-Pq: Name make_rules_for_redirect_stricter.patch

Fix mmap usage.

Add missing MAP_NORESERVE and fix error checking.

Special thanks to Olivier JG for debugging the issue.

Task-number: QTBUG-27322
Change-Id: Ia9f4aa80415f0127318714912b524131a5b0f18a

Gbp-Pq: Name add_missing_map_noreserve.patch

Fix JIT crash on x86-64 (avoid 32-bit branch offset overflow)

Cherry-picked from webkit commit
a5b3261a8c4386b4e14ce40a34c7fc933a5f7001

Task-number: QTBUG-23871
Change-Id: Ia028fe072b349e3a7883ae0f6f7298941cc1bc9e
Reviewed-by: Simon Hausmann <simon.hausmann@nokia.com>
(cherry picked from commit 79ebd39d0d4846cb911ae122d2059e5add568d7e in qtscript)

Gbp-Pq: Name fix_jit_crash_on_x86_64.patch

disable-SSL-compression-by-default

Gbp-Pq: Name disable-SSL-compression-by-default.patch

Fix-cursor-truncate-to-include-line-position

Origin: commit ca89c49fa2c5cbb3945897046f33eed9f7da846c
Author: Jiang Jiang <jiang.jiang@nokia.com>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@nokia.com>
Applied-Upstream: yes
Forwarded: not-needed

Gbp-Pq: Name Fix-cursor-truncate-to-include-line-position.patch

QElfParser: fix type of sh_size

The type of the sh_size field of a section header is either Elf32_Word or Elf64_Xword,
so the type used cannot be qelfword_t (always 32 bits) but qelfoff_t.

Change-Id: Ia380b6823913fee7a96b39f742630ae3a9ca0cb8
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reviewed-by: Arvid Picciani <arvid.picciani@nokia.com>
(backport of 77b179689ba37dc909778fdd00df2701f83a2868 from qtbase)

Gbp-Pq: Name QElfParser-fix-type-of-sh_size.patch

Fix logic for figuring out what ConfigureNotify positions can be trusted

When reading ahead in the queue for ConfigureNotify events, it's necessary
to look for intermediate ReparentNotify events as well, since they will
determine whether the position in the event can be trusted or not.

Bug: https://bugreports.qt.nokia.com/browse/QTBUG-21900

Gbp-Pq: Name QTBUG-21900_Buttons_in_Qt_applications_not_clickable_when_run_under_gnome-shell.patch

QTBUG-14724_close_orphaned_file_descriptors_after_printing

 What happened: In QPdfBaseEnginePrivate::openPrintDevice() noone
 remembers the file descriptor opened by tempFile() which is a call to
 the cups library to cupsTempFile()

 Later in closePrintDevice the check for fd<0 fails, so no one closes
 the file descriptor. If you later remove the file, the descriptor is
 still open and cannot removed until you close the application.

 If you print 20 times and more during your application is running and
 you print out large files (complicate forms with a lot of elements
 produces files with 3-4 MByte) your temporary file can be full, but
 you don't see (with ls) files in it.

Bug: https://bugreports.qt.nokia.com/browse/QTBUG-14724
Author: Georg Scherzer

Gbp-Pq: Name QTBUG-14724_close_orphaned_file_descriptors_after_printing.patch

Add_support_for_QT_USE_DRAG_DISTANCE_env_var

from QT_USE_DRAG_DISTANCE environment variable.
See also http://bugreports.qt.nokia.com/browse/QTBUG-12594
Author: Joonas Tanskanen <joonas.tanskanen@sasken.com>

Gbp-Pq: Name Add_support_for_QT_USE_DRAG_DISTANCE_env_var.patch

qt4-x11 (4:4.8.2+dfsg-11) unstable; urgency=medium

  * Take upstream patch change_all_shmget_calls_to_use_user-only_memory.patch.
    It changes the shmget calls to get user-only memory, CVE-2013-0254.
    - Set urgency to medium.
    - Drop changes from tests/auto/qtipc/qsharedmemory/tst_qsharedmemory.cpp,
    it doesn't exists in the Debian tarball.

[dgit import unpatched qt4-x11 4:4.8.2+dfsg-11]

Import qt4-x11_4.8.2+dfsg-11.debian.tar.gz

[dgit import tarball qt4-x11 4:4.8.2+dfsg-11 qt4-x11_4.8.2+dfsg-11.debian.tar.gz]

Import qt4-x11_4.8.2+dfsg.orig.tar.xz

[dgit import orig qt4-x11_4.8.2+dfsg.orig.tar.xz]