Release Notes for Cisco AnyConnect Secure Mobility Client, Release 3.1
End-of-Life Date Announced for AnyConnect 3.x
Downloading the Latest Version of AnyConnect
Important Security Considerations
Enable Strict Certificate Trust in the AnyConnect Local Policy
AnyConnect Certificate Requirements
Increased Security in the AnyConnect Pre-deploy Package
Important AnyConnect, Host Scan, and CSD Interoperability Information
Important AnyConnect 3.1 and ASA 9.0 Interoperability Considerations
Upgrading 3.1 MR12 AnyConnect Clients/Incompatibility Issues
Upgrading 3.1 MR11 AnyConnect Clients/Incompatibility Issues
Upgrading 3.1 MR10 AnyConnect Clients/Incompatibility Update
Upgrading 3.0 AnyConnect Clients and Optional Modules
Upgrading 2.5 and older AnyConnect Clients and Optional Modules
Web-based installation May Fail on 64-bit Windows
AnyConnect Compatibility with Microsoft Windows 10
AnyConnect Support for Windows 8.x
Changes in AnyConnect 3.1.14018
Changes in AnyConnect 3.1.13015
Changes in AnyConnect 3.1.12020
Changes in AnyConnect 3.1.11004
Changes in AnyConnect 3.1.10010
AnyConnect Compatibility with Microsoft Windows 10.X
AnyConnect 3.x Unsupported with Mac OS X El Capitan
June 2015 and July 2015 OpenSSL Vulnerabilities
Changes in AnyConnect 3.1.09013
Changes in AnyConnect 3.1.08009
Changes in AnyConnect 3.1.07021
Microsoft Permanent Fix for Windows 8.1 AnyConnect Incompatibility
Changes in AnyConnect 3.1.06079
Changes in AnyConnect 3.1.06078
Changes in AnyConnect 3.1.06073
Changes in AnyConnect 3.1.05187
Changes in AnyConnect 3.1.05182
Adaptive Security Appliance Requirements
IOS Support by AnyConnect 3.1.x
AnyConnect UI Fails Due to Missing Dependency libpangox
OS X 10.9 Safari Can Disable Weblaunch
Internet Explorer, Java 7, and AnyConnect 3.1.1 Interoperability
Implicit DHCP filter applied when Tunnel All Networks Configured
AnyConnect VPN over Tethered Devices
AnyConnect Virtual Testing Environment
UTF-8 Character Support for AnyConnect Passwords
Disabling Auto Update May Prevent Connectivity Due to a Version Conflict
Interoperability between Network Access Manager and other Connection Managers
Network Interface Card Drivers Incompatible with Network Access Manager
Avoiding SHA 2 Certificate Validation Failure (CSCtn59317)
Configuring Antivirus Applications for Host Scan
Microsoft Internet Explorer Proxy Not Supported by IKEv2
MTU Adjustment on Group Policy May Be Required for IKEv2
MTU Automatically Adjusted When Using DTLS
Network Access Manager and Group Policy
Full Authentication Required if Roaming between Access Points
User Guideline for Cisco Cloud Web Security Behavior with IPv6 Web Traffic
Preventing Other Devices in a LAN from Displaying Hostnames
Messages in the Localization File Can Span More than One Line
AnyConnect for Mac OS X Performance when Behind Certain Routers
Preventing Windows Users from Circumventing Always-on
AnyConnect Requires That the ASA Be Configured to Accept TLSv1 Traffic
Trend Micro Conflicts with Install
ActiveX Controls May Fail During Web-Deployment and Upgrade
Using the Manual Install Option on Mac OS X if the Java Installer Fails
No Pro-Active Key Caching (PKC) or CCKM Support
Application Programming Interface for the AnyConnect Secure Mobility Client
Caveats Resolved by AnyConnect 3.1.14018
Open Caveats in AnyConnect 3.1.14018
Caveats Resolved by AnyConnect 3.1.13015
Caveats Resolved by AnyConnect 3.1.12020
Caveats Resolved by AnyConnect 3.1.11004
Caveats Resolved by AnyConnect 3.1.10010
Caveats Resolved by AnyConnect 3.1.09013
Caveats Resolved by AnyConnect 3.1.08009
Caveats Resolved by AnyConnect 3.1.07021
Caveats Resolved by AnyConnect 3.1.06079
Caveats Resolved by AnyConnect 3.1.06078
Caveats Resolved by AnyConnect 3.1.06073
Caveats Resolved by AnyConnect 3.1.05187
Caveats Resolved by AnyConnect 3.1.05182
This document includes the following sections:
The AnyConnect 3.1.14018 release is the last maintenance release for 3.1.x. Refer to the End-of-Sale and End-of-Life Announcement for the Cisco AnyConnect Secure Mobility Client Version 3.x for information about the end-of-sale and end-of-life date set for Cisco AnyConnect Secure Mobility Client, Version 3.x. You are encouraged to migrate to AnyConnect 4.x and Apex or Plus licenses, which grant access to AnyConnect 4.x software.
To download the latest version of AnyConnect, you must be a registered user of Cisco.com.
Other files, which help you add additional features to AnyConnect, can also be downloaded.
To obtain the AnyConnect software, follow these steps:
1.
Follow this link to the Cisco AnyConnect Secure Mobility Client Introduction page:
http://www.cisco.com/en/US/products/ps10884/tsd_products_support_series_home.html
4.
Expand the Latest Releases folder and click the latest release, if it is not already selected.
5.
Download AnyConnect Packages using one of these methods:
–
To download a single package, find the package you want to download and click Download.
–
To download multiple packages, click Add to cart in the package row and then click Download Cart at the top of the Download Software page.
6.
Read and accept the Cisco license agreement when prompted.
7.
Select a local directory in which to save the downloads and click Save.
8.
See “Configuring the ASA to Download AnyConnect” in Chapter 2, Deploying the AnyConnect Secure Mobility Client in the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 3.1 to install the packages onto an ASA or to deploy AnyConnect using your enterprise software management system.
“Code Signing Certificates: Windows will no longer trust files with the Mark of the Web attribute that are signed with a SHA-1 code signing certificate and are timestamped after 1/1/2016.” Refer to the Microsoft documentation for more details: http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx
Files signed before January 1st, 2016 will be valid until January 1st, 2017.
Note
: Due to the code signing changes, the current AnyConnect users must upgrade to AnyConnect release 3.1.13015, the future version of AnyConnect 4.2 MR, or AnyConnect 4.3+ releases in order to keep their AnyConnect functional on Windows platforms after January 1, 2017.
We strongly recommend you enable Strict Certificate Trust for the AnyConnect client for the following reasons:
To configure Strict Certificate Trust see Chapter 9 “Enabling FIPS and Additional Security in the Local Policy” of the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 3.1.
The following behavioral changes have been made to server certificate verification:
–
If a Subject Alternative Name extension is present with relevant attributes, name verification is performed solely against the Subject Alternative Name. Relevant attributes include DNS Name attributes for all certificates, and additionally include IP address attributes if the connection is being performed to an IP address.
–
If a Subject Alternative Name extension is not present, or is present but contains no relevant attributes, name verification is performed against any Common Name attributes found in the Subject of the certificate.
–
If a certificate uses a wildcard for the purposes of name verification, the wildcard must be in the first (left-most) subdomain only, and additionally must be the last (right-most) character in the subdomain. Any wildcard entry not in compliance is ignored for the purposes of name verification.
The AnyConnect pre-deploy VPN package previously installed the VPN WebLaunch ActiveX control by default. Starting in AnyConnect 3.1, installation of the VPN ActiveX control is turned off by default. This change was made to favor the most secure configuration as the default behavior.
When pre-deploying the AnyConnect Client and Optional Modules, if you require the VPN ActiveX control to be installed with AnyConnect, you must use the NOINSTALLACTIVEX=0 option with msiexec or a transform. For example, on one line enter:
msiexec /package anyconnect-win-ver-pre-deploy-k9.msi /norestart /passive NOINSTALLACTIVEX=0 /lvx*
We always recommend that you upgrade to the latest Host Scan engine version.
Note
: AnyConnect will not establish a VPN connection when used with an incompatible version of Host Scan or CSD. Ensure that you are running the version of HostScan that is the same version as AnyConnect.
Note
: If you cannot upgrade AnyConnect and Host Scan or AnyConnect and CSD at the same time, upgrade Host Scan or CSD first, then upgrade AnyConnect.
Cisco dropped support for the Secure Desktop (Vault), Cache Cleaner, Keystroke Logger Detection (KSL), and Host Emulation Detection features of CSD in Nov 2012. For more information, see the deprecation field notice “ Secure Desktop (Vault), Cache Cleaner, Keystroke Logger Detection, and Host Emulation Detection Features Are Deprecated.”
CSD was deprecated in April 2014: Cisco Secure Desktop Deprecation.
Note
: Pre-login assessment and returning certificate information is not available. HostScan is not an authentication method; it simply checks to verify what exists on the device attempting to connect.
The following AnyConnect features require ASA 9.0 or later, or ASDM 7.0 or later, to be installed on your ASA for them to be effective:
AnyConnect integrates the following modules into the AnyConnect client package:
If you are using the ASA to deploy AnyConnect, the ASA can deploy all the optional modules. If pre-deploying using your SMS, you can deploy all modules, but you must pay special attention to the module installation sequence and other details.
AnyConnect shares its Host Scan component with Cisco Secure Desktop (CSD). The stand-alone Host Scan package for AnyConnect provides the same features as the Host Scan package that is part of CSD. The AnyConnect client can co-exist with Cisco Secure Desktop Vault, but it cannot be run or deployed from inside the Vault.
Every release of AnyConnect includes a localization MST file that administrators can upload to the ASA whenever they upload AnyConnect packages with new software. If you are using our localization MST files, make sure to update them with the latest release from CCO whenever you upload a new AnyConnect package.
For more information about deploying the AnyConnect modules, see the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 3.1.
Once AnyConnect 3.1.12020 has been automatically deployed to an endpoint, you cannot connect to a secure gateway configured with AnyConnect versions 4.0, 4.1, 4.1MR2, or 4.1MR4, which are incompatible. If you try to upgrade from the AnyConnect 3.1 MR12 version to any version other than AnyConnect 4.1MR8, 4.2, or 3.1 versions later than 3.1.12020, you will receive a notification that the upgrade is not allowed.
Once AnyConnect 3.1.11004 has been automatically deployed to an endpoint, you cannot connect to a secure gateway configured with AnyConnect versions 4.0, 4.1, 4.1MR2, or 4.1MR4, which are incompatible. If you try to upgrade from the AnyConnect 3.1 MR11 version to any version other than AnyConnect 4.1MR6 (or later) or 3.1 versions later than 3.1.11004, you will receive a notification that the upgrade is not allowed.
Once AnyConnect 3.1.10010 has been automatically deployed to an endpoint, you cannot connect to a secure gateway configured with AnyConnect versions 4.0, 4.1, and 4.1MR2, which are incompatible. If you try to upgrade from the AnyConnect 3.1 MR10 version to any version other than AnyConnect 4.1MR4 (or later) or 3.1 versions later than 3.1.10010, you will receive a notification that the upgrade is not allowed.
When you upgrade from AnyConnect Secure Mobility Client Release 3.0 to AnyConnect Secure Mobility Client Release 3.1, AnyConnect 3.1 performs the following operations:
When you upgrade from any 2.5.x version of AnyConnect, the AnyConnect Secure Mobility Client Release 3.1 performs the following:
Note
: If you are upgrading from the legacy Cisco VPN client, the MTU value on the physical adapters may have been lowered to 1300. You should restore the MTU back to the default (typically 1500) for each adapter so as to achieve optimal performance when using AnyConnect.
This issue applies to Internet Explorer versions 10 and 11, on Windows versions 7 and 8.
When the Windows registry entry HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\TabProcGrowth is set to 0, Active X has problems during AnyConnect web deployment.
See http://support.microsoft.com/kb/2716529 for more information.
Note
: On Windows 8, starting Internet Explorer from the Windows start screen runs the 64-bit version. Starting from the desktop runs the 32-bit version.
Java 7 can cause problems with AnyConnect Secure Mobility Client, Hostscan, CSD and Clientless SSL VPN (WebVPN). A description of the issues and workarounds is provided in the Troubleshooting Technote Java 7 Issues with AnyConnect, CSD/Hostscan, and WebVPN - Troubleshooting Guide, which is in Cisco documentation under Security > Cisco Hostscan.
AnyConnect 3.1MR10 (3.1.10010) and later are compatible with Windows 10 official release. Technical Assistance Center (TAC) support will be available beginning on 7/29/2015.
For best results, we recommend a clean install of AnyConnect on Windows 10 system and not an upgrade from Windows 7/8/8.1. If you are planning to perform an upgrade from Windows 7/8/8/1 with AnyConnect pre-installed, make sure that you first upgrade AnyConnect prior to upgrading the Operating System. The Network Access Manager module must be uninstalled prior to upgrading to Windows 10. After the first upgrade is complete, it can be re-installed on the system. You may also choose to fully uninstall AnyConnect and re-install one of the supported versions after upgrading to Windows 10.
Limitations to AnyConnect Support for Windows 8.x
–
WinPcap service “Remote Packet Capture Protocol v.0 (experimental)” distributed with Wireshark does not support Windows 8.
To work around this problem, uninstall Wireshark or disable the WinPcap service, reboot your Windows 8 computer, and attempt the AnyConnect connection again.
–
Outdated wireless cards or wireless card drivers that do not support Windows 8 prevent AnyConnect from establishing a VPN connection.
To work around this problem, make sure you have the latest wireless network cards or drivers that support Windows 8 installed on your Windows 8 computer.
Note
Machine authentication allows a client desktop to be authenticated to the server before the user logs in. During this time server can perform scheduled administrative tasks for this client machine. Machine authentication is also required for the EAP Chaining feature where a server can authenticate both User and Machine for a particular client. This will result in identifying company assets and applying appropriate access policy. For example, if this is a personal asset (PC/laptop/tablet), and a company login is used, server will fail Machine authentication, but succeed User authentication and will apply proper access restrictions to this client desktop.
AnyConnect 3.1.14018 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.14018.
AnyConnect 3.1.13015 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.13015.
AnyConnect 3.1.12020 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.12020.
AnyConnect 3.1.11004 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.11004.
AnyConnect 3.1.10010 is a maintenance release that includes Windows 10 support and OpenSSL fixes and resolves the defects described in Caveats Resolved by AnyConnect 3.1.11004.
AnyConnect 3.1MR10 (3.1.10010) and later are compatible with Windows 10 official release. See AnyConnect Compatibility with Microsoft 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 ( http://support.microsoft.com/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.
New operating support for AnyConnect 3.x ended in July 2015. El Capitan is not a supported operating system for the Cisco AnyConnect Secure Mobility Client, Release 3.x. However, Cisco AnyConnect Secure Mobility Client, Release 4.1 is compatible with Mac OS X El Capitan. See the AnyConnect Ordering Guide for information on AnyConnect Plus and Apex licenses, which grant access to AnyConnect 4.x software.
AnyConnect 3.1.09013 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.09013.
AnyConnect 3.1.08009 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.08009.
AnyConnect 3.1.07021 is a maintenance release that resolves the 2015 OpenSSL Vulnerabilities in CSCus42746 and other the defects described in Caveats Resolved by AnyConnect 3.1.07021. Also, read the section below for issues with Microsoft’s February 10, 2015 patch.
Microsoft’s Patch update on February 10, 2015 introduced an OS regression which impacts Windows 8.1 users running AnyConnect. This issue will also impact some Windows 7 users if they have IE11 installed.
To resolve this issue, install the Windows 8.1 March cumulative security update for Internet Explorer (MS15-018) or the Vulnerability in SChannel could allow security feature bypass: March 10, 2015 (MS15-031) update. This update is being distributed by Windows update. After the update is installed, the “fixit” or other workarounds are no longer needed. Go here for more details.
The Cisco Tracking ID is CSCus89729. Further details are available here: https://tools.cisco.com/bugsearch/bug/CSCus89729.
AnyConnect 3.1.06079 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.06079.
AnyConnect 3.1.06078 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.06078.
AnyConnect 3.1.06073 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.06073, and contains Host Scan Engine 3.1.06073. The versions of Antivirus, Antispyware, and Firewall products supported by Hostscan are listed on http://www.cisco.com/c/en/us/support/security/anyconnect-secure-mobility-client/products-device-support-tables-list.html.
AnyConnect 3.1.05187 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.05187, and contains Host Scan Engine 3.1.05183.
AnyConnect 3.1.05187 also adds support for Mac OS X 10.10. Support for Mac OS X 10.7 has been dropped.
AnyConnect 3.1.05182 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.05182, and contains Host Scan Engine 3.1.05182.
This section identifies the management and endpoint requirements for this release. For endpoint OS support and license requirements for each feature, see AnyConnect Secure Mobility Client Features, Licenses, and OSs.
AnyConnect 3.1 installations can coexist with other VPN clients, including IPsec clients, on all supported endpoints; however, we do not support running AnyConnect while other VPN clients are running.
The following sections identify the minimum management and endpoint requirements:
–
Cisco Next Generation Encryption “Suite-B” security
–
AnyConnect client deferred upgrades
–
Use the ASDM to edit non-VPN client profiles (such as Network Access Manager, Web Security, or Telemetry).
–
Use the services supported by a Cisco IronPort Web Security Appliance license. These services let you enforce acceptable use policies and protect endpoints from websites found to be unsafe, by granting or denying all HTTP and HTTPS requests.
–
Deploy firewall rules. If you deploy always-on VPN, you might want to enable split tunneling and configure firewall rules to restrict network access to local printing and tethered mobile devices.
–
Configure dynamic access policies or group policies to exempt qualified VPN users from an always-on VPN deployment.
–
Configure dynamic access policies to display a message on the AnyConnect GUI when an AnyConnect session is in quarantine.
Note
: The minimum flash memory recommended for all ASA 5500 models using AnyConnect 3.1 is 512MB. This will allow hosting of multiple endpoint operating systems, and logging and debugging to be enabled on the ASA.
Due to flash size limitations on the ASA 5505 (maximum of 128 MB), not all permutations of the AnyConnect package will be able to be loaded onto this model. To successfully load AnyConnect, you will need to reduce the size of your packages (i.e. fewer OSs, no host Scan, etc,) until they fit on the available flash.
Check for the available space before proceeding with the AnyConnect install or upgrade. You can use one of the following methods to do so:
If your ASA has only the default internal flash memory size or the default DRAM size (for cache memory), you could have problems storing and loading multiple AnyConnect client packages on the ASA. Even if you have enough space on the flash to hold the package files, the ASA could run out of cache memory when it unzips and loads the client images. For internal memory requirements for each ASA model, see Memory Requirements for the Cisco ASA Adaptive Security Appliances Software Version 8.3 and Later. For additional information about the ASA memory requirements and upgrading ASA memory, see the latest release notes for the Cisco ASA 5500 series.
Cisco supports AnyConnect VPN access to IOS Release 15.1(2)T functioning as the secure gateway; however, IOS Release 15.1(2)T does not currently support the following AnyConnect features:
For additional limitations of IOS support for AnyConnect VPN, please see Features Not Supported on the Cisco IOS SSL VPN.
Refer to http://www.cisco.com/go/fn for additional IOS feature support information.
Make sure you enter the whitespace between “start=” and “disabled”.
Note
: Internet Explorer 6.0 is no longer supported.
The AnyConnect GUI is not supported on all Linux distributions. When the GUI is supported, it's appearance is the same as the AnyConnect version 2.5 GUI.
AnyConnect requires 50MB of hard disk space.
To operate correctly with Mac OS X, AnyConnect requires a minimum display resolution of 1024 by 640 pixels.
Mac OS X 10.8 introduces a new feature called Gatekeeper that restricts which applications are allowed to run on the system. You can choose to permit applications downloaded from:
The default setting is Mac App Store and identified developers (signed applications). AnyConnect release 3.1 is a signed application, but it is not signed using an Apple certificate. This means that you must either select the Anywhere setting or use Control-click to bypass the selected setting to install and run AnyConnect from a pre-deploy installation. Users who web deploy or who already have AnyConnect installed are not impacted. For further information see: http://www.apple.com/macosx/mountain-lion/security.html.
Note
: Web launch or OS upgrades (for example 10.9 to 10.10) install as expected. Only the pre-deploy installation requires additional configuration as a result of Gatekeeper.
Note
: See Important AnyConnect, Host Scan, and CSD Interoperability Information, for important AnyConnect and Host Scan compatibility information.
Tip
You should always upgrade to the latest Host Scan engine that matches the same version as the AnyConnect version.
The Host Scan engine, which is among the components delivered by AnyConnect Secure Mobility Client, identifies endpoint posture attributes of the host.
The List of Antivirus, Antispyware, and Firewall Applications Supported by Host Scan is available on cisco.com. The support chart opens most easily using a Firefox browser. If you are using Internet Explorer, download the file to your computer and change the file extension from.zip to.xlsm. You can open the file in Microsoft Excel, Microsoft Excel viewer, or Open Office.
This Host Scan package can be installed on ASA version 8.4 or later. See Important AnyConnect, Host Scan, and CSD Interoperability Information for interoperability information.
For brief descriptions and example product numbers (SKUs) of the AnyConnect user license options, see Cisco Secure Remote Access: VPN Licensing Overview.
For our open source licensing acknowledgments, see Open Source Used In AnyConnect Secure Mobility Client 3.1.
For the latest end-user license agreement, see Cisco End User License Agreement, AnyConnect Secure Mobility Client, Release 3.1.
We support all non-beta AnyConnect software versions available on the Cisco AnyConnect VPN Software Download site; however, we provide fixes and enhancements only in maintenance or feature releases based on the most recently released version.
For information about when releases are no longer supported, see http://www.cisco.com/c/en/us/products/eos-eol-policy.html
The following guidelines and limitations for this and previous releases are in effect:
On many newer Linux distributions, the AnyConnect UI may fail to start with the error:
The missing library is obsolete and is no longer available. This impacts other applications, not just AnyConnect.
Pango has released the source code of a compatible library that has been built by others and is available online. To resolve this problem, find and install either the package pangox-compat-0.0.2-2.el7.x86_64.rpm or pangox-compat-0.0.2-3.fc20.x86_64.rpm.
The default security settings in the version of Safari that comes with OS X 10.9 (Mavericks) prevents AnyConnect Weblaunch from working. To configure Safari to allow Weblaunch, edit the URL of the ASA to Unsafe Mode, as described below.
Open Safari > Preferences > Security > Manage Website Settings. Click on the ASA and select run in Unsafe Mode.
Supported versions of Internet Explorer stop working when the user attempts to connect to the ASA, when Java 7 is installed on the endpoint, when Host Scan is installed and enabled on the ASA, and when AnyConnect 3.1.1 is installed and enabled on the ASA.
This does not happen when Active X or earlier versions of Java 7 are installed. To avoid this, use a supported version of Java on the endpoint that is earlier than Java 7.
To allow local DHCP traffic to flow in the clear when Tunnel All Networks is configured, AnyConnect adds a specific route to the local DHCP server when the AnyConnect client connects. To prevent data leakage on this route, AnyConnect also applies an implicit filter on the LAN adapter of the host machine, blocking all traffic for that route except DHCP traffic.
Cisco has qualified the AnyConnect VPN client over a bluetooth or USB tethered Apple iPhone only. Network connectivity provided by other tethered devices should be verified with the AnyConnect VPN client before deployment.
AnyConnect supports Smartcard provided credentials in the following environments:
Note
: AnyConnect does not support Smart cards on Linux or PKCS #11 devices.
Cisco performs a portion of AnyConnect client testing using these virtual machine environments:
We do not support running AnyConnect in virtual environments; however, we expect AnyConnect to function properly in the VMWare environments we test in.
If you encounter any issues with AnyConnect in your virtual environment, report them. We will make our best effort to resolve them.
AnyConnect 3.0 or later used with ASA 8.4(1) or later supports UTF-8 characters in passwords sent using RADIUS/MSCHAP and LDAP protocols.
When Auto Update is disabled for a client running AnyConnect release 2.5.x or 3.0.2, the ASA must have the same version (2.5.x or 3.0.2) or earlier installed or the client will fail to connect to the VPN.
To avoid this problem, configure the same version or earlier AnyConnect package on the ASA, or upgrade the client to the new version by enabling Auto Update.
AnyConnect 3.0.1047 is signed with the new certificate VeriSign Class 3 Public Primary Certification Authority - G5. Upon installation, Windows XP, Windows Vista, Mac OS X, and Linux users might see a downloader error message, such as the following:
This event can occur if one or all of the following are true:
AnyConnect installations and upgrades might require endpoint users to install the root CA before upgrading or installing AnyConnect. To do so, enable Update Root Certificates and verify that the Internet is reachable before the AnyConnect installation. By default, Update Root Certificates is enabled. Users can also update the root CA manually, as instructed on the VeriSign website.
When the Network Access Manager operates, it takes exclusive control over the network adapters and blocks attempts by other software connection managers (including the Windows native connection manager) to establish connections. Therefore, if you want AnyConnect users to use other connection managers on their endpoint computers (such as iPassConnect Mobility Manager), they must disable Network Access Manager either through the Disable Client option in the Network Access Manager GUI, or by stopping the Network Access Manager service.
The Intel wireless network interface card driver, version 12.4.4.5, is incompatible with Network Access Manager. If this driver is installed on the same endpoint as the Network Access Manager, it can cause inconsistent network connectivity and an abrupt shutdown of the Windows operating system.
The AnyConnect client relies on the Windows Cryptographic Service Provider (CSP) of the certificate for hashing and signing of data required during the IKEv2 authentication phase of the IPsec/IKEv2 VPN connection. If the CSP does not support SHA 2 algorithms, and the ASA is configured for the pseudo-random function (PRF) SHA256, SHA384, or SHA512, and the connection profile (tunnel-group) is configured for certificate or certificate and AAA authentication, certificate authentication fails. The user receives the message Certificate Validation Failure.
This failure occurs for Windows only, for certificates that belong to CSPs that do not support SHA 2-type algorithms. Other supported OSs do not experience this problem.
To avoid this problem you can configure the PRF in the IKEv2 policy on the ASA to md5 or sha (SHA 1).
Alternatively, you can modify the certificate CSP value for native CSPs that work:
Note
: Do not apply this workaround to SmartCards certificates. You cannot change the CSP names. Instead, contact the SmartCard provider for an updated CSP that supports SHA 2 algorithms.
Note
: Performing the following workaround actions could corrupt the user certificate if you perform them incorrectly. Use extra caution when specifying changes to the certificate.
You can use the Microsoft Certutil.exe utility to modify the certificate CSP values. Certutil is a command-line utility for managing a Windows CA, and is available in the Microsoft Windows Server 2003 Administration Tools Pack. You can download the Tools Pack at this URL:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c16ae515-c8f4-47ef-a1e4-a8dcbacff8e3&displaylang=en
Follow this procedure to run Certutil.exe and change the Certificate CSP values:
1.
Open a command window on the endpoint computer.
2.
View the certificates in the user store along with their current CSP value using the following command:
The following example shows the certificate contents displayed by this command:
1.
Identify the <CN> attribute in the certificate. In the example, the CN is Carol Smith. You need this information for the next step.
2.
Modify the certificate CSP using the following command. The example below uses the subject <CN> value to select the certificate to modify. You can also use other attributes.
On Windows Vista and Windows 7 or later, use this command:
On Windows XP, use this command:
3.
Repeat step 2 and verify the new CSP value appears for the certificate.
Antivirus applications can misinterpret the behavior of some of the applications included in the posture module and the Host Scan package as malicious. Before installing the posture module or Host Scan package, configure your antivirus software to “white-list” or make security exceptions for these Host Scan applications:
This release of AnyConnect does not support Apple iOS. However, you can use the same ASAs to support Apple iOS devices running AnyConnect 3.0 VPN connections. For ASA setup instructions, see the Release Notes for Cisco AnyConnect Secure Mobility Client Release 3.0.x for Apple iOS.
IKEv2 does not support the Microsoft Internet Explorer proxy. If you need support for that feature, use SSL.
AnyConnect sometimes receives and drops packet fragments with some routers, resulting in a failure of some web traffic to pass.
To avoid this, lower the value of the MTU. We recommend 1200. The following example shows how to do this using CLI:
To set the MTU using ASDM, go to Configuration > Network (Client) Access > Group Policies > Add or Edit > Advanced > SSL VPN Client.
If Dead Peer Detection (DPD) is enabled for DTLS, the client automatically determines the path MTU. If you previously reduced the MTU using the ASA, you should restore the setting to the default (1406). During tunnel establishment, the client auto-tunes the MTU using special DPD packets. If you still have a problem, use the MTU configuration on the ASA to restrict the MTU as before.
Windows Active Directory Wireless Group Policies manage the wireless settings and any wireless networks that are deployed to PCs in a specific Active Directory Domain. When installing the Network Access Manager, administrators must be aware that certain wireless GPOs can affect the behavior of the Network Access Manager. Administrators should test the GPO policy settings with the Network Access Manager before doing full GPO deployment. The following GPO conditions may prevent the Network Access Manager from operating as expected (CSCtk57290):
A mobile endpoint running Windows 7 or later must do a full EAP authentication instead of leveraging the quicker PMKID reassociation when the client roams between access points on the same network. Consequently, in some cases, AnyConnect prompts the user to enter credentials for every full authentication if the active profile requires it.
Unless an exception for an IPv6 address, domain name, address range, or wild card is specified, IPv6 web traffic is sent to the scanning proxy where it performs a DNS lookup to see if there is an IPv4 address for the URL the user is trying to reach. If the scanning proxy finds an IPv4 address, it uses that for the connection. If it does not find an IPv4 address, the connection is dropped.
If you want all IPv6 traffic to bypass the scanning proxies, you can add this static exception for all IPv6 traffic: /0. Doing this makes all IPv6 traffic bypass all scanning proxies. This means that IPv6 traffic is not protected by Cisco Cloud Web Security.
After one uses AnyConnect to establish a VPN session with Windows 7 or later on a remote LAN, the network browsers on the other devices in the user’s LAN display the names of hosts on the protected remote network. However, the other devices cannot access these hosts.
To ensure the AnyConnect host prevents the hostname leak between subnets, including the name of the AnyConnect endpoint host, configure that endpoint to never become the master or backup browser.
1.
Enter regedit in the Search Programs and Files text box.
2.
Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Browser\Parameters\
An AnyConnect certificate revocation warning popup window opens after authentication if AnyConnect attempts to verify a server certificate that specifies the distribution point of an LDAP certificate revocation list (CRL) if the distribution point is only internally accessible.
If you want to avoid the display of this popup window, do one of the following:
Note
: Disabling server certificate revocation checking in Internet Explorer can have severe security ramifications for other uses of the OS.
If you try to search for messages in the localization file, they can span more than one line, as shown in the example below:
When the AnyConnect client for Mac OS X attempts to create an SSL connection to a gateway running IOS, or when the AnyConnect client attempts to create an IPsec connection to an ASA from behind certain types of routers (such as the Cisco Virtual Office (CVO) router), some web traffic may pass through the connection while other traffic drops. AnyConnect may calculate the MTU incorrectly.
To work around this problem, manually set the MTU for the AnyConnect adaptor to a lower value using the following command from the Mac OS X command line:
On Windows computers, users with limited or standard privileges may sometimes have write access to their program data folders. This could allow them to delete the AnyConnect profile file and thereby circumvent the always-on feature. To prevent this, configure the computer to restrict access to the following folders (or at least the Cisco sub-folder):
Using the Windows 7 or later Wireless Hosted Network feature can make AnyConnect unstable. When using AnyConnect, we do not recommend enabling this feature or running front-end applications that enable it (such as Connectify or Virtual Router).
AnyConnect requires the ASA to accept TLSv1 traffic, but not SSLv3 traffic. The SSLv3 key derivation algorithm uses MD5 and SHA-1 in a way that can weaken the key derivation. TLSv1, the successor to SSLv3, resolves this and other security issues present in SSLv3.
Thus, the AnyConnect client cannot establish a connection with the following ASA settings for “ssl server-version”:
If you have Trend Micro on your device, the Network Access Manager will not install because of a driver conflict. You can uninstall the Trend Micro or uncheck trend micro common firewall driver to bypass the issue. Trend Micro also conflicts with Web Security.
None of the supported antivirus, antispyware, and firewall products report the last scan time information. Host scan reports the following:
–
File system protection status (active scan)
Installation of an ActiveX control requires administrative privileges.
AnyConnect web-deployment must install an ActiveX control. If the user can't install that control, then web-deployment fails.
The AnyConnect ActiveX control will change periodically, due to a security fix or the addition of new functionality. Upgrading the ActiveX control will fail during Weblaunch for users with Standard privileges.
To avoid these problems, Administrators can deploy using the AnyConnect pre-installer, SMS, GPO or other administrative deployment methodology.
If users use WebLaunch to start AnyConnect on a Mac and the Java installer fails, a dialog box presents a Manual Install link. Users should follow this procedure when this happens:
1.
Click Manual Install. A dialog box presents the option to save a.dmg file that contains an OS X installer.
2.
Mount the disk image (.dmg) file by opening it and browsing to the mounted volume using Finder.
3.
Open a Terminal window and use the CD command to navigate to the directory containing the file saved. Open the.dmg file and run the installer.
4.
Following the installation, choose Applications > Cisco > Cisco AnyConnect Secure Mobility Client to initiate an AnyConnect session, or use Launchpad.
Network Access Manager does not support PKC or CCKM caching. On Windows 7, fast roaming with a non-Cisco wireless card is unavailable.
The AnyConnect Secure Mobility Client includes an Application Programming Interface (API) for customers who want to write their own client programs.
The API package contains documentation, source files, and library files to support a C++ interface for the Cisco AnyConnect VPN Client. You can use the libraries and example programs for building on Windows, Linux and MAC platforms. The Makefiles (or project files) for the Windows platform are also included. For other platforms, it includes platform specific scripts showing how to compile the example code. Network administrators can link their application (GUI, CLI, or embedded application) with these files and libraries.
You can download the APIs from Cisco.com.
For support issues regarding the AnyConnect API, send e-mail to the following address: anyconnect-api-support@cisco.com.
Caveats describe unexpected behavior or defects in Cisco software releases.
The Release Notes for the AnyConnect Secure Mobility Client, Release 3.1 is a living document that we update as we continue to produce maintenance releases and major releases of AnyConnect. As the development of AnyConnect continues, should we find caveats that impact AnyConnect 3.1, or resolve caveats that improve AnyConnect 3.1, we will update these tables and republish this document.
Caveats are fixed for an AnyConnect release until that release reaches end of life. To see Cisco’s end of life policy, and which versions are no longer supported, see http://www.cisco.com/c/en/us/products/eos-eol-policy.html.
For more information, see the following documents: