Cisco Cisco Content Security Management Appliance M380 Notas de publicación
11
Release Notes for Cisco IronPort AsyncOS 8.0 for Security Management
Known Issues
Known Issues
Some issues may also have been present in previous releases. These issues are described in previous
release notes.
release notes.
Known issues in AsyncOS for Email and AsyncOS for Web that affect the Cisco Content Security
Management appliance may be documented under those product names in the Bug Search Tool or in the
release notes for those products.
Management appliance may be documented under those product names in the Bug Search Tool or in the
release notes for those products.
Known Issues in Release 8.0.0-407
Dynamic information about known issues in this release is available via the Bug Search Tool. See
.
Known Issues in Release 8.0.0-404
Note
Known issues in AsyncOS for Email Security and AsyncOS for Web are documented in the release notes
for those products.
for those products.
86109
CSCzv49704
Fixed: SSH 1 is an obsolete and nonsecure protocol and support for it should be removed
SSH1 protocol is no longer an option for SCP push on the Log Subscriptions page or in the CLI
logconfig
command. SSH2 is the default protocol.
84778
CSCzv34188
Fixed: Issue Priority options on “Open a Technical Support Case” page are not translated
Previously: On the “Open a Technical Support Case” page under the Help and Support menu,
the options for Issue Priority did not appear in the language currently selected in Preferences.
the options for Issue Priority did not appear in the language currently selected in Preferences.
Table 2
Resolved Issues (continued)
Previous
Bug ID
Bug ID
Bug ID
Description
Table 3
Known Issues
Bug ID
Description
CSCuf56294
An application fault may occur when configuring SOCKS policies in Identities.
This can occur when both of the following conditions exist:
•
On the SOCKS Policy Edit Page, you select Authorized Groups or Users.
•
SOCKS Policy membership is based on an Identity with custom or predefined URL Categories.
CSCuf57558
For MIB files downloaded from the SMA, MIB browsers cannot load the MIB file correctly
Workaround: Download the revised MIB file for your SMA version:
CSCzv88664
Loading a configuration file saved from the appliance after upgrade may fail
For information and a solution to this issue, see
.