麦粉丝中文网率先发布，转载请注明本文出处.
McAfee VirusScan Enterprise 8.0 的Patch16补丁已经出来了，如果你是McAfee的大客户，可以优先获得厂家发放的该补丁，对于普通用户，需要晚些时候才有机会获得，目前我已经作了一些测试，改善不是很多，但有关键的几点是不错的，下面给大家看看readme.txt中的原文，另外将其中修正的几个问题在下面翻译成中文给大家。
Release Notes for McAfee VirusScan Enterprise 8.0i Patch 16
Environment
McAfee VirusScan Enterprise 8.0i
Summary
Patch 16 is currently undergoing a Managed Release program, where select customers have agreed to be early adopters of the Patch. This program will conclude December 18, at which time the Patch will become generally available.
The Managed Release program has a limited number of openings for customer participation. To participate in the Managed Release program for this release or future VirusScan Patch releases, please consult with your Technical Account Manager.
================================================== ========
Release Notes for McAfee(R) VirusScan(R) Enterprise
Version 8.0i
Patch 16
Copyright (C) 2007 McAfee, Inc.
All Rights Reserved
================================================== ========
Patch Release: 26 November 2007
This release was developed and tested with:
- VirusScan Enterprise:8.0i
- DAT Version: 5162, November 13 2007
- Engine Version: 5.2.00
Make sure you have installed these versions before
using this release.
================================================== ========
Thank you for using VirusScan(R) Enterprise
software. This file contains important information
regarding this release. We strongly recommend that
you read the entire document.
The attached files are provided as is, and with no
warranty either expressed or implied as to their
suitability for any particular use or purpose.
McAfee, Inc. assumes no liability for damages
incurred either directly or indirectly as a result
of the use of these files, including but not limited
to the loss or damage of data or systems, loss of
business or revenue, or incidental damages arising
from their use. Patch files should be applied only
on the advice of McAfee Technical Support, and only
when you are actually experiencing the issue being
addressed by the Patch. Patch files should not be
proactively applied in order to prevent potential
product issues. You are responsible for reading and
following all instructions for preparation,
configuration, and installation of Patch files.
Patch files are not a substitute or replacement for
product Service Packs which may be released by
McAfee, Inc. It is a violation of your software
license agreement to distribute or share these files
with any other person or entity without written
permission from McAfee, Inc. Further, posting of
McAfee Patch files to publicly available Internet
sites is prohibited. McAfee, Inc. reserves the right
to refuse distribution of Patch files to any company
or person guilty of unlawful distribution of McAfee
software products. Questions or issues with McAfee
Patch files should be directed to McAfee Technical
Support.
__________________________________________________ ________
WHAT'S IN THIS FILE
- About This Release
- Purpose
- Resolved Issues
- Previously Resolved Issues
- Known Issues
- Files Included With This Release
- Installation
- Installation Requirements
- Installation Steps
- Installation Steps via ePolicy orchestrator
- Additional Steps for Anti-Spyware
Enterprise Module
- Installation Steps via McAfee Installation
Designer
- Verifying Installation
- Contact Information
- Copyright & Trademark Attributions
- License Information
__________________________________________________ ________
ABOUT THIS RELEASE
PURPOSE
This release combines previous Patches and updated
binaries into a single Microsoft Patch installer to
address all items listed in "Resolved Issues" and
"Previously Resolved Issues" below.
For the most update-to-date copy of this Readme
information, refer to McAfee Support KnowledgeBase
article 614252.
RESOLVED ISSUES
1. ISSUE:
Certain applications exhibited a much heavier
CPU load with VirusScan Enterprise’s Buffer
Overflow protection enabled.
RESOLUTION:
The buffer overflow engine was restructured to
bypass expensive evaluations when inexpensive
tests had already given conclusive information.
2. ISSUE:
If a request to open a file is blocked by an
Access protection rule, and the filter driver is
not prepared to accept the status code
indicating that the file contents require
flushing, the system may halt with a STOP 0x50.
RESOLUTION:
The AV filter driver has been revised to ensure
files are properly closed if access to the file
was blocked by the Access Protection feature.
3. ISSUE:
Some potentially unwanted programs could be
detected even though they were added to the
exclusion list.
RESOLUTION:
The common shell binary has been updated to
better handle specific return codes from the
scanner engine.
4. ISSUE:
When upgrading from VirusScan Enterprise 8.0i to
8.5i the Lotus Notes Scanner may fail to upgrade
properly if the Lotus Notes Client was open.
RESOLUTION:
The VirusScan Enterprise 8.0i Lotus Notes
Scanner now becomes dormant during the
installation of VirusScan Enterprise 8.5i and
the new scanner is enabled upon reboot.
NOTE:
This fix has the ability to install to Lotus
Notes version 7.x. However, it does not add any
additional support for the scanner on Lotus
Notes 7.x.
5. ISSUE:
The Access Protection, port blocking white list
is limited to 1024 characters.
RESOLUTION:
The buffer sizes for the white list have now
been increased from 1024 characters to 2500
characters. Also, the VirusScan NAP will now
accept up to 2500 characters for the white
list.
6. ISSUE:
The VirusScan Enterprise management plug-in
writes all settings to the registry on every
policy enforcement. This increased the risk for
registry corruption.
RESOLUTION:
The VirusScan Enterprise management plug-in now
writes to the registry only when there is a
difference between the current policy and the
contents of the registry.
7. ISSUE:
The VirusScan Enterprise On-Demand Scanner would
end scanning of cookies (requires McAfee
AntiSpyware Module) after detecting the first
cookie.
RESOLUTION:
The Common Shell component has been corrected to
solve an issue where the scan was being
terminated prematurely.
8. ISSUE:
"User Defined Detection" settings are in effect
even when the "Detect Unwanted Programs"
setting, for the scanner, is disabled.
RESOLUTION:
Changes have been made so that when the "Detect
Unwanted Programs" setting is disabled, "User
Defined Detections" settings are included with
the setting.
__________________
1.在启用VirusScan Enterprise的缓冲区溢出保护后可能会因为某些应用软件的使用导致发生CPU超负荷的情况。
2.当打开一个被访问保护规则阻挡的文件时，可能因为驱动过滤的问题导致出现0x50的系统终止错误。
3.VirusScan Enterprise可能会检测某些潜在的恶意程序即便它已被添加到排除列表中，并对这些恶意程序执行处理。
4.当将VirusScan Enterprise8.0升级到8.5的时候恰巧Lotus Notes客户端没有启用，那么Lotus Notes 扫描程序很有可能会无法正常升级。
5.访问保护中端口阻挡的白名单列表字符限制由原来的1024个字符扩充到2500个字符。
6.由于VirusScan Enterprise默认可以强制将所有规则（包含原始规则）写入注册表进行保存，这样的做法相应地增加了不少风险。因此安装Patch16后，VirusScan Enterprise只将不同于默认设置的策略写入注册表进行保存。
7.VirusScan Enterprise的按需扫描可能会在检测第一个cookie文件后出现错误终止。（在安装反间谍模块后）
8.即便“检测有害程序”设置没有启用，但对于按访问扫描来说，“用户定义的检测项”的设置同样是有效的。
以上翻译由柯文舜完成，细水校正，由麦粉丝中文网发布，转载请注明本文出处. |
发表于 2007-11-30 19:21:49
