Table of Contents
- Downloading the Latest Version of AnyConnect
- Important Security Considerations
- Important AnyConnect, Host Scan, and CSD Interoperability Information
- Deprecation of Features: Secure Desktop (Vault), Cache Cleaner, Keystroke Logger Detection, and Host Emulation Detection
- Important AnyConnect 3.1 and ASA 9.0 Interoperability Considerations
- Installation Overview
- AnyConnect Support for Windows 8.x
- Web-based installation May Fail on 64-bit Windows
- 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
- System Requirements
- Host Scan Engine
- AnyConnect Support Policy
- Guidelines and Limitations
- Application Programming Interface for the AnyConnect Secure Mobility Client
- AnyConnect Caveats
- Related Documentation
- 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.
Step 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.
- We have removed all AnyConnect software packages prior to AnyConnect 3.1.05182 from Cisco.com because of a security risk found in the OpenSSL software integrated in those releases: http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20140605-openssl. We recommend that customers running AnyConnect 3.0.X or AnyConnect 3.1.0178 or earlier upgrade to the latest version of AnyConnect 3.1.06073 or AnyConnect 4.0.
- We do not recommend using a self-signed certificate because of the possibility that a user could inadvertently configure a browser to trust a certificate on a rogue server and because of the inconvenience to users of having to respond to a security warning when connecting to your secure gateway.
- With the increase in targeted exploits, enabling Strict Certificate Trust in the local policy helps prevent “man in the middle” attacks when users are connecting from untrusted networks such as those in coffee shops and airports.
- Even if you use fully verifiable and trusted certificates, the AnyConnect client, by default, allows end users to accept unverifiable certificates. If your end users were subjected to a man-in-the-middle attack, they may be prompted to accept a malicious certificate. To remove this decision from your end users, enable Strict Certificate Trust.
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.
- SSL connections being performed via FQDN no longer make a secondary server certificate verification with the FQDN's resolved IP address for name verification if the initial verification using the FQDN fails.
- IPsec and SSL connections require that if a server certificate contains Key Usage, the attributes must contain DigitalSignature AND (KeyAgreement OR KeyEncipherment). If the server certificate contains an EKU: for SSL the attributes must contain serverAuth, and for IPsec the attributes must contain serverAuth OR ikeIntermediate. Note that server certificates are not required to have a KU or an EKU to be accepted.
- IPSec connections perform name verification on server certificates. The following rules are applied for the purposes of IPSec name 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:
Caution AnyConnect will not establish a VPN connection when used with an incompatible version of Host Scan or CSD.
Caution 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.
Deprecation of Features: Secure Desktop (Vault), Cache Cleaner, Keystroke Logger Detection, and Host Emulation Detection
These features will continue to provide the functionality for which they were built, but will eventually be incompatible with future releases of the ASA, ASDM, AnyConnect, or the operating system on which the endpoint runs.
For more information, see the deprecation field notice “ Secure Desktop (Vault), Cache Cleaner, Keystroke Logger Detection, and Host Emulation Detection Features Are Deprecated.”
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.
- Upgrades all previous versions of the core client and retains all VPN configurations.
- If you install Network Access Manager, AnyConnect retains all CSSC 5.x configuration for use with Network Access Manager, then removes CSSC 5.x.
- Upgrades any Host Scan files used by AnyConnect.
- Does not upgrade the Cisco IPsec VPN client (or remove it). However, the AnyConnect 3.1 client can coexist on the computer with the IPsec VPN client.
- Does not upgrade and cannot coexist with Cisco’s ScanSafe AnyWhere+. You must uninstall AnyWhere+ before installing the AnyConnect Secure Mobility Client.
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.
See http://support.microsoft.com/kb/2716529 for more information.
- Run a 32-bit version of Internet Explorer.
- Edit the registry entry to a non-zero value, or remove that value from the registry.
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 provide in the Troubleshooting Technote Java 7 Issues with AnyConnect, CSD/Hostscan, and WebVPN - Troubleshooting Guide, which is in Cisco documentation under Security > Cisco Hostscan.
- Upgrading to Windows 8.1 requires you to uninstall AnyConnect, and reinstall it after your Windows upgrade is complete.
- AnyConnect is not supported on Windows RT. There are no APIs provided in the operating system to provide this functionality. Cisco has an open request with Microsoft on this topic. Customers who want this functionality should contact Microsoft to express their interest.
- Other third-party product’s incompatibility with Windows 8 prevent AnyConnect from establishing a VPN connection over wireless networks. Here are two examples of this problem:
– WinPcap service “Remote Packet Capture Protocol v.0 (experimental)” distributed with Wireshark does not support Windows 8.
- AnyConnect is not integrated with the new UI framework, known as the Metro design language, that is deployed on Windows 8; however, AnyConnect does run on Windows 8 in desktop mode.
- Verify that the driver on the client system is supported by Windows 8. Drivers that are not supported by Window 8 may have intermittent connection problems.
- For Network Access Manager, machine authentication using machine password will not work on Windows 8 / 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 8 / 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.
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.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.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.
- Adaptive Security Appliance Requirements
- IOS Support by AnyConnect 3.1.x
- Microsoft Windows
- Mac OS X
– 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.
Caution 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.
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.
- Post Log-in Always-on VPN
- Connect Failure Policy
- Client Firewall providing Local Printer and Tethered Device access
- Optimal Gateway Selection
- AnyConnect Profile Editor
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.
- After April 8, 2014, Microsoft will no longer provide new security updates, non-security hotfixes, free or paid assisted support options, or online technical content updates for Windows XP ( http://www.microsoft.com/en-us/windows/endofsupport.aspx). On the same date, Cisco will stop providing customer support for AnyConnect releases running on Windows XP, and we will not offer Windows XP as a supported operation system for future AnyConnect releases.
- When Windows XP is configured with a secondary IP address, starting an AnyConnect connection starts the IpFilterDriver, which blocks traffic over the secondary IP. To prevent this, disable the ipFilterDriver with the following command:
- Upgrading from Windows XP to Windows Vista or Windows 7 or later requires a clean install since the Cisco AnyConnect Virtual Adapter is not preserved during the upgrade. Manually uninstall AnyConnect, upgrade Windows, then reinstall AnyConnect manually or via WebLaunch.
- Windows 2003 Server (32 bit) is supported for Network Access Manager only.
- Windows 2008 is not supported; however, we do not prevent the installation of AnyConnect 3.1 on this OS.
- To start AnyConnect with WebLaunch, you must use the 32-bit version of Firefox 3.0+ and enable ActiveX or install Sun JRE 1.4+.
- AnyConnect VPN is compatible with 3G data cards which interface with Windows 7 or later via a WWAN adapter.
- On Windows XP, schannel.dll supports only 3DES and not AES encryption; therefore, an ASA on which XP clients terminate must have 3DES enabled with the ssl encryption aes128-sha1 aes256-sha1 3des-sha1 command.
- x86 instruction set.
- 32-bit or 64-bit processor.
- 32 MB RAM.
- 20 MB hard disk space.
- Superuser privileges are required for installation.
- libstdc++ users must have libstdc++.so.6(GLIBCXX_3.4) or higher, but below version 4.
- Java 5 (1.5) or later. The only version that works for web installation is Sun Java. You must install Sun Java and configure your browser to use that instead of the default package.
- zlib - to support SSL deflate compression
- xterm - only required if you're doing initial deployment of AnyConnect via Weblaunch from ASA clientless portal.
- gtk 2.0.0.
- gdk 2.0.0
- libpango 1.0 or a compatible build such as package pangox-compat-0.0.2-2.el7.x86_64.rpm or pangox-compat-0.0.2-3.fc20.x86_64.rpm
- iptables 1.2.7a or later.
- tun module supplied with kernel 2.4.21 or 2.6.
- Mac OS X 10.5 is no longer supported. AnyConnect 3.1 will not install on this platform.
- Mac OS X 10.6, and 10.7 are no longer supported.
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.
Caution See Important AnyConnect, Host Scan, and CSD Interoperability Information, for important AnyConnect and Host Scan compatibility information.
The Host Scan engine, which is among the components delivered by AnyConnect Secure Mobility Client, identifies endpoint posture attributes of the host. Host Scan package, hostscan_3.1.06073-k9.pkg, is available for use with AnyConnect 3.1.006073 and higher.
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
- 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 Smart Card Support
- 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
- iPhone Not Supported
- 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
- Revocation Message
- 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
- Avoid Wireless-Hosted-Network
- AnyConnect Requires That the ASA Be Configured to Accept TLSv1 Traffic
- Trend Micro Conflicts with Install
- What Host Scan Reports
- ActiveX Controls May Fail During Web-Deployment and Upgrade
- No Pro-Active Key Caching (PKC) or CCKM Supporterror while loading shared libraries: libpangox-1.0.so.0: cannot open shared object file: No such file or directory
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.
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.
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.
- Microsoft CAPI 1.0 and CAPI 2.0 on Windows 7 and Windows 8.
- Keychain via Tokend on Mac OS X, 10.4 and higher
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.
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:
- Root certificates were intentionally pruned.
- Update Root Certificates is disabled.
- The internet is not reachable when an upgrade occurs (for example, you have your ASA in a private network without Internet access).
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 18.104.22.168, 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.
Caution 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.
Caution 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:
certutil -csp "Microsoft Enhanced RSA and AES Cryptographic Provider" -f -repairstore -user My <CN> carol smithcertutil -csp "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" -f -repairstore -user My <CN> carol smith
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.
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.
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.
- Obtain a certificate without any private CRL requirements.
- Disable server certificate revocation checking in Internet Explorer.
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.
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.
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.
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.
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.
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.
- Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 3.1
- Open Source Software Used In AnyConnect Secure Mobility Client, Release 3.1
- Release notes for Cisco ASA 5500
- Release notes for Cisco Adaptive Security Device Manager
- Supported VPN Platforms, Cisco ASA 5500 Series
- Release notes for Cisco Secure Desktop
- AnyConnect and HostScan Antivirus, Antispyware, and Firewall Support Charts
- Navigating the Cisco ASA 5500 Series Documentation
- Cisco AnyConnect Secure Mobility Solution Guide
- IronPort AsyncOS for Web User Guide
- IronPort AsyncOS 7.0 for Web Release Notes
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.