Cisco Cisco AnyConnect Secure Mobility Client v3.x Release Notes

Page of 34
 
Release Notes for Cisco AnyConnect Secure Mobility Client, Release 3.1
Changes in AnyConnect 3.1.10010
9
Changes in AnyConnect 3.1.10010
AnyConnect 3.1.10010 is a maintenance release that includes Windows 10 support and OpenSSL fixes and 
resolves the defects described in 
.
AnyConnect Compatibility with Microsoft Windows 10.X
AnyConnect 3.1MR10 (3.1.10010) and later are compatible with Windows 10 official release. See 
.
Restriction with Windows 10
For Network Access Manager, machine authentication using machine password will not work on Windows 10 / 
Server 2012 unless a registry fix described in Microsoft KB 2743127 (
is applied to the client desktop. This fix includes adding a DWORD value LsaAllowReturningUnencryptedSecrets 
to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa registry key and setting this value to 1. 
This change permits Local Security Authority (LSA) to provide clients like Cisco Network Access Manager with the 
Machine password. It is related to the increased default security settings in Windows 10/ Server 2012. Machine 
authentication using Machine certificate does not require this change and will work the same as it worked with 
pre-Windows 8 operating systems.
AnyConnect 3.x Unsupported with Mac OS X El Capitan 
AnyConnect Ordering Guide 
for information on 
AnyConnect Plus and Apex licenses, which grant access to AnyConnect 4.x software.
June 2015 and July 2015 OpenSSL Vulnerabilities
Cisco AnyConnect 3.1.10010 resolves CSCuu83398 and CSCuv26246 OpenSSL vulnerabilities.
Changes in AnyConnect 3.1.09013
AnyConnect 3.1.09013 is a maintenance release that resolves the defects described in 
Changes in AnyConnect 3.1.08009
AnyConnect 3.1.08009 is a maintenance release that resolves the defects described in 
Changes in AnyConnect 3.1.07021
AnyConnect 3.1.07021 is a maintenance release that resolves the 2015 OpenSSL Vulnerabilities in CSCus42746 
and other the defects described in 
. Also, read the section 
below for issues with Microsoft’s February 10, 2015 patch.