Cisco Cisco Web Security Appliance S380 Release Notes
Resolved Issues
26
Release Notes for Cisco IronPort AsyncOS 7.1.3 for Web
Resolved Issues in Version 7.1.2
lists the issues that were resolved in version 7.1.2 of AsyncOS for Web.
Table 4
Resolved Issues in AsyncOS 7.1.2 for Web
Defect ID
Description
50248
Fixed: Web Proxy generates a core file when it encounters memory management
issues
issues
Previously, the Web Proxy generated a core file when it encountered internal memory
management issues. This no longer occurs.
management issues. This no longer occurs.
71187
Fixed: Invalid HTTPS certificate handling
Previously, when the HTTPS Proxy encountered a destination server using a
certificate with multiple errors (such as unrecognized root authority), the HTTPS
Proxy performed the configured action for unrecognized root authority before all
other types of certificate errors. This no longer occurs. Now, the HTTPS Proxy
performs the action specified for the error that has a higher ranking using the
following ranking:
certificate with multiple errors (such as unrecognized root authority), the HTTPS
Proxy performed the configured action for unrecognized root authority before all
other types of certificate errors. This no longer occurs. Now, the HTTPS Proxy
performs the action specified for the error that has a higher ranking using the
following ranking:
•
Expired certificates
•
Unrecognized root authority
•
All other errors
•
Mismatched hostname
71202
Fixed: FTP Proxy generates a core file when the FTP client closes a connection
very early
very early
Previously, the FTP Proxy generated a core file when the FTP client closed a
connection before the Web Proxy could accept it. This no longer occurs.
connection before the Web Proxy could accept it. This no longer occurs.
72382
Fixed: Web Security appliance locks up and then automatically reboots when a
large number of SSH connections are made to the management interface
large number of SSH connections are made to the management interface
Previously, the Web Security appliance locked up and then automatically rebooted
when a large number of SSH connections were made to the management interface,
such as from automated scripts. This no longer occurs. Now, only 100 concurrent SSH
sessions are allowed.
when a large number of SSH connections were made to the management interface,
such as from automated scripts. This no longer occurs. Now, only 100 concurrent SSH
sessions are allowed.