Symantec Endpoint Security throws out error bugs

[Иван 290]

http://www.theregister.co.uk/2008/02/20/sy...rity_error_bug/

Symantec is working on a patch for a bug that generates errors in corporate security protection updates. Workarounds designed to quell the message storm are available but a more comprehensive fix is still in testing.

The glitch in the Symantec's LiveUpdate package has left sysadmins managing Symantec Endpoint Protection coping with "broken" clients, according to Reg reader Richard who manages the network of a UK college. Updates to the Decomposer function of Symantec Endpoint Protection last week, a software component that decompresses or unpacks files, meant that clients spew our errors every time they attempt to download further updates.

Symantec has published an advisory detailed workarounds. Posts on Symantec forums indicate that the problem first reared its head on 11 February. Richard's experiences seem fairly typical.

"On the 11 I noticed that the log files on the server were filling up with LiveUpdate errors, I contacted Symantec support who ran through a few things with me and he went away stumped, promising to get back to me soon," he told El Reg.

"So I turned to the Symantec forums, the replies came flooding in, looks like every Symantec customer worldwide has been affected by the issue, it turns out they posted corrupt Decompositer definitions and it's broken the client on people's machines."

The incident has sparked a lively debate on Symantec's forums between some disgruntled customers and staffers over the general quality of its security software and, more particularly, the security giant's quality assurance and testing regimes.

Symantec acknowledged the error-generating bug, but says the product remains functional. "This issue would have led users to see "Error 58/55" in their SEP log files. The issue shouldn’t have done anything but generate errors — there should have been no issue with the product itself," a spokesman said.

Richard said the problem didn't cause problems in downloading anti-virus definitions even without applying workarounds (contrary to earlier versions of this story). Nonetheless the issue is still causing all sorts of grief. "Anti-virus updates appear to come down fine. It’s just a decomposer issue, but does that mean that anti-virus can’t scan inside archives until the problem is fixed? Symantec aren't saying," he said.

"However many many people are still having problems with things like the errors filling up logs and grinding servers to a halt. I personally figured something was wrong when none of my users could log on, there were temp files from live update littering the boot drive of the server and it had no free space," Richard reports. ®

https://forums.symantec.com/syment/board/me...ding&page=1

К сожалению ссылка на решение проблемы, приведенная в статье не работает

[A. 875]

День сегодня такой.

Микрософт тоже отжог...

Information about programs that are known to experience a loss of functionality

when they run on a Windows Vista Service Pack 1-based computer.

1. Programs that are blocked from starting after you install Windows Vista SP1

The programs in the following table have known compatibility problems

with Windows Vista SP1. For reliability reasons, Microsoft blocks

these programs from starting after you install Windows Vista SP1:

- Bitdefender AV and Internet Security v.10

- Fujitsu Shock Sensor v 2.1.0.0

- Jiangmin KV Antivirus v. 10 and 2008

- Trend Micro Internet Security 2008

- Rising Personal Firewall 2007

- Zone Alarm Security Suite 7.1.105

http://support.microsoft.com/kb/935796/en-us

[Кирилл Керценбаум 671]

Symantec is working on a patch for a bug that generates errors in corporate security protection updates. Workarounds designed to quell the message storm are available but a more comprehensive fix is still in testing.

Проблема была связана с ошибкой в выпуске Сертификата для обновления компонент антивирусного движка. Она не приводила к отказу ни Антивирусной защиты, ни системы в целом, временное решения было представлено в течение 6 часов. На перевыпуск обновления понадобилось больше времени, так была необходимость проведения всех циклов тестирования заново

К сожалению ссылка на решение проблемы, приведенная в статье не работает

Она просто немного переехала - http://service1.symantec.com/support/ent-s...0c?OpenDocument

Микрософт тоже отжог...

К сожалению это тенденция нашего времени, ошибок в ПО становится все больше, радует лишь что критичность этих ошибок снижается