Pulse Secure Desktop Client Release Notes Pulse Secure Desktop Client Release Notes Pulse Secure Desktop

  • View
    4

  • Download
    0

Embed Size (px)

Text of Pulse Secure Desktop Client Release Notes Pulse Secure Desktop Client Release Notes Pulse Secure...

  • Pulse Secure Desktop Client Release Notes Pulse Secure Desktop Client v5.0R16 Build 61523 For more information on this product, go to www.pulsesecure.net/products.

    Build

    Published

    Document Version

    10.0

    http://www.pulsesecure.net/products

  • Pulse Secure, LLC

    2700 Zanker Road, Suite 200 San Jose, CA 95134 http://www.pulsesecure.net

    © 2016 by Pulse Secure, LLC. All rights reserved

    Pulse Secure and the Pulse Secure logo are trademarks of Pulse Secure, LLC in the United States. All other trademarks,

    service marks, registered trademarks, or registered service marks are the property of their respective owners.

    Pulse Secure, LLC assumes no responsibility for any inaccuracies in this document. Pulse Secure, LLC reserves the right to

    change, modify, transfer, or otherwise revise this publication without notice.

    The information in this document is current as of the date on the title page.

    END USER LICENSE AGREEMENT

    The Pulse Secure product that is the subject of this technical documentation consists of (or is intended for use with) Pulse

    Secure software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”)

    posted at http://www.pulsesecure.net/support/eula. By downloading, installing or using such software, you agree to the

    terms and conditions of that EULA.

    http://www.pulsesecure.net/ http://www.pulsesecure.net/support/eula

  • Pulse Secure Desktop Client Release Notes

    © 2016 by Pulse Secure, LLC. All rights reserved 3

    Contents

    Introduction 6

    General Notes 6

    Interoperability and Supported Platforms 6

    New Features 6

    Caveats, Important Changes, and Deprecated Features 6

    Problems Resolved in 5.0R16 6

    Table 1 Problem Resolved in Pulse 5.0R16 6

    Problems Resolved in 5.0R15.1 7

    Problem Resolved in Pulse 5.0R15 7

    Table 2 Problem Resolved in Pulse 5.0R15 7

    Problem Resolved in Pulse 5.0R14 7

    Table 3 Problem Resolved in Pulse 5.0R14 8

    Problem Resolved in Pulse 5.0R13.1 8

    Table 4 Problem Resolved in Pulse 5.0R13.1 8

    Problem Resolved in Pulse 5.0R13 8

    Table 5 Resolved in This Release 8

    Pulse Secure Desktop New Features in Pulse 5.0R12 9

    Pulse Secure Rebranding ...................................................................................................................................... 9

    Problem Resolved in Pulse 5.0R12 9

    Table 6 Resolved in This Release 9

    Security Issues Resolved in Pulse 5.0R12 ............................................................................................................. 10

    Table 7 Security Issues Resolved in This Release 10

    Problem Resolved in Pulse 5.0R11 11

    Table 8 Resolved in This Release 11

    Security Issues Resolved in Pulse 5.0R11 11

    Table 9 Security Issues Resolved in This Release 11

    Problem Resolved in Pulse 5.0R10 12

    Table 10 Resolved in This Release 12

  • Pulse Secure Desktop Client Release Notes

    © 2016 by Pulse Secure, LLC. All rights reserved 4

    Problem Resolved in Pulse 5.0R9 12

    Table 10 Resolved in This Release 12

    Noteworthy Changes in Pulse 5.0R8 13

    Problem Resolved in Pulse 5.0R8 13

    Table 11 Resolved in This Release 13

    Noteworthy Changes in Pulse 5.0R7 14

    Problem Resolved in Pulse 5.0R7 14

    Table 12 Resolved in This Release 14

    Noteworthy Changes in Pulse 5.0R6 14

    Removal of AppAccel (WX) from this and subsequent releases on Pulse Secure client ............................... 14

    Problem Resolved in Pulse 5.0R6 Release 15

    Table 13 Resolved in This Release 15

    Problem Resolved in Pulse 5.0R5 15

    Table 14 Resolved in This Release 15

    Problem Resolved in Pulse 5.0R4 16

    Table 15 Resolved in This Release 16

    Problem Resolved in Pulse 5.0R3.1 16

    Table 16 Resolved in This Release 16

    Problem Resolved in Pulse 5.0R3 17

    Table 17 Resolved in This Release 17

    Known Issues in Pulse 5.0R3 17

    Table 18 Known Issues 17

    Problem Resolved in Pulse 5.0R2 19

    Table 19 Resolved in This Release 19

    Known Issues in Pulse 5.0R2 19

    Documentation Feedback 19

    Technical Support 20

  • Pulse Secure Desktop Client Release Notes

    © 2016 by Pulse Secure, LLC. All rights reserved 5

    Revision History 20

  • Pulse Secure Desktop Client Release Notes

    © 2016 by Pulse Secure, LLC. All rights reserved 6

    Introduction

    This release-notes document for the Pulse Secure desktop client version 5.0. This document provides a cumulative list of all

    enhancements, fixes and known issues for the 5.0 client. If the information in the release notes differs from the

    information found in the documentation set, follow the release notes.

    The Pulse Secure desktop client provides a secure and authenticated connection from an endpoint device (either Windows

    or Mac OS X) to a Pulse Secure gateway (either Pulse Connect Secure or Pulse Policy Secure). For a complete description of

    the capabilities of this desktop client, please see the online help within the desktop client itself, or the Pulse Desktop Client

    Administration Guide (which can be found at Pulse Secure’s Technical Publications site).

    General Notes Security-related issues are not normally covered in Pulse Secure release notes. To find more information security advisories

    affecting Pulse Secure products, please the Pulse Secure security advisory page.

    Interoperability and Supported Platforms

    Please refer to the Pulse Secure Supported Platforms Guide for supported versions of browsers and

    operating systems in this release.

    New Features No new features were introduced in the Pulse Secure Desktop Client version 5.0r16

    Caveats, Important Changes, and Deprecated Features The Pulse Secure Desktop Client version 5.0R16 addresses issues described in security advisory SA40241.

    Important note: In order to run the Pulse Secure desktop client version 5.0R15 or later on a Windows 7 machine, the

    machine must contain a March 10, 2015 Windows 7 Update in order to be able to accept and verify SHA-2-signed binaries

    properly. This Windows 7 update is described here and here. If this update is not installed (in other words if a Windows 7

    machine has not received an OS update since March 10, 2015), then Pulse 5.0R15 and later will have reduced functionality

    (see PRS-337311, below). (As a general rule, Pulse Secure, LLC recommends that client machines be kept current with the

    latest OS updates to maximize security and stability.)

    Problems Resolved in 5.0R16 Table 1 Problem Resolved in Pulse 5.0R16

    Problem Report

    Number

    Description

    https://www.pulsesecure.net/techpubs/ https://kb.pulsesecure.net/?atype=sa https://www.pulsesecure.net/techpubs/pulse-policy-secure/pps/5.2rx https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA40241/ https://support.microsoft.com/en-us/kb/3033929 https://technet.microsoft.com/en-us/library/security/3033929

  • Pulse Secure Desktop Client Release Notes

    © 2016 by Pulse Secure, LLC. All rights reserved 7

    PRS-342195

    Pulse SAM fails to launch on Windows 10 Redstone due to Windows digital signature verification error

    Problems Resolved in 5.0R15.1 The Pulse Secure Desktop Client version 5.0r15.1 addresses issues described in security advisory SA40241.

    Problem Resolved in Pulse 5.0R15

    Table describes issues that are resolved.

    Table 2 Problem Resolved in Pulse 5.0R15

    Problem

    Report

    Number

    Description

    PRS-337311 As described in the “Caveats” section of this document, the Pulse Secure desktop client version 5.0R15 and later are code-signed with SHA-2 certificates in order to meet new restrictions enforced by enforced by Microsoft operating systems in 2016. This new code-signing feature causes certain issues with older versions of Windows 7. Specifically, versions of Windows 7 that have not been patched since March 10, 2015 will not be able to load certain drivers and executables signed with SHA-2. These unpatched versions of Windows 7 will experience the error “An unexpec