Subject: X2Go issue (in src:x2goclient) has been marked as closed

From: Mike DePaulo <[email-masked]>
Date: Sat, 11 Mar 2017 21:30:23 +0100 (CET)

close #1152
thanks

Hello,

we are very hopeful that X2Go issue #1152 reported by you
has been resolved in the new release (4.1.0.0) of the
X2Go source project »src:x2goclient«.

You can view the complete changelog entry of src:x2goclient (4.1.0.0)
below, and you can use the following link to view all the code changes
between this and the last release of src:x2goclient.

    http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=45a6a96b2f53a9947ce75b5ce5e142c3fa196213;hp=add03ee78f3dcbee3317bf17a08dcb2cbeb12ee7

If you feel that the issue has not been resolved satisfyingly, feel
free to reopen this bug report or submit a follow-up report with
further observations described based on the new released version
of src:x2goclient.

Thanks a lot for contributing to X2Go!!!

light+love
X2Go Git Admin (on behalf of the sender of this mail)

---
X2Go Component: src:x2goclient
Version: 4.1.0.0--2017.03.11
Status: RELEASE
Date: Sat, 11 Mar 2017 13:24:19 -0500
Fixes: 1152
Changes:
 x2goclient (4.1.0.0--2017.03.11) RELEASED; urgency=medium
 .
   [ Mike DePaulo ]
   * New upstream version (4.1.0.0-2017.03.11):
     - Windows: Upgrade PulseAudio from 6.0 to 7.1
       Fixes: #1152 Issues with audio when playing HTML5 videos
     - Windows: Remove uninstaller from start menu.
       It is still available in "Programs and Features".
     - Windows: Upgrade Win32 OpenSSL from 1.0.1t to 1.0.2k
       Fixes numerous CVEs
     - Windows: Upgrade libssh from 0.7.0 to 0.7.4 (while maintaining
       Pageant support).
       The possibly relevant changes are:
         + CVE-2016-0739 was fixed
         + improved id_ed25519 support
         + numerous bug fixes
     - Windows: Update PuTTY from 0.67 to 0.68
       The possibly relevant changes are:
         + CVE-2016-6167 was fixed (did not affect X2Go Client by
           default because the installation dir is not writeable by
           users)
         + CVE-2017-6542 was fixed