Cisco Cisco ASA 5512-X Adaptive Security Appliance Release Notes

Page of 66
 
13
Release Notes for the Cisco ASA 5500 Series, Version 8.2(x)
 
  New Features
New Features in Version 8.2(4.1)
Released: January 18, 2011
 lists the new features for ASA Version 8.2(4.1).
Note
We recommend that you upgrade to a Cisco.com-posted interim release only if you have a specific 
problem that it resolves. If you decide to run an interim release in a production environment, keep in 
mind that only targeted testing is performed on interim releases. Interim releases are fully supported by 
Cisco TAC and will remain on the download site only until the next maintenance release is available. If 
you choose to run an interim release, we strongly encourage you to upgrade to a fully-tested maintenance 
or feature release when it becomes available. We will document interim release features at the time of 
the next maintenance or feature release. For a list of resolved caveats for each interim release, see the 
Cisco ASA Interim Release Notes available on the Cisco.com software download site.
New Features in Version 8.2(4)
Released: December 15, 2010
Remote Access Features
Clientless SSL VPN 
support for Outlook Web 
Access 2010
By default, Clientless SSL VPN now provides content transformation (rewriting) support for 
Outlook Web Access (OWA) 2010 traffic.
We did not modify any commands.
Table 7
New Features for ASA Version 8.2(4.4) (continued)
Feature
Description
Table 8
New Features for ASA Version 8.2(4.1)
Feature
Description
Remote Access Features
SSL SHA-2 digital 
signature
This release supports the use of SHA-2 compliant signature algorithms to authenticate SSL VPN 
connections that use digital certificates. Our support for SHA-2 includes all three hash sizes: 
SHA-256, SHA-384, and SHA-512. SHA-2 requires AnyConnect 2.5.1 or later (2.5.2 or later 
recommended). This release does not support SHA-2 for other uses or products. This feature does 
not involve configuration changes. Caution: To support failover of SHA-2 connections, the standby 
ASA must be running the same image. To support this feature, we added the Signature Algorithm 
field to the show crypto ca certificate command to identify the digest algorithm used when 
generating the signature.