Vulnerability reported in Symantec Anti-virus

Hi Debra,

On Wednesday 31 May 2006 09:52, Debra Bartling wrote:

> At 12:50 PM 5/30/2006, you wrote:
> >In my testing, I had some problems with going from
394 to 400 on one
> > Dell system (it seemed to hang near the end of the
patching
> > process)....
>
> FYI -- Using the 310.exe and the two patches posted on
the
> software.berkeley.edu site, I had problems yesterday on
5 of 6
> computers, both Windows 2000 and XP. In each case, the
install would
> hang at some point, either trying to run LiveUpdate at
the end of the
> 310.exe install or while installing the first patch.

Thanks for the report. Another option is the following:

=======
In response to the recent SAV vulnerability I've created a
new slipstreamed 
SCS 3.1 + MP1 installer available for testing here:

  http://wssg.berkeley.edu/public/test/scs3-fortesting/

This was made using the Symantec KB article:

http://service1.symantec.com/SUPPO
RT/ent-security.nsf/ppfdocs/2006051811363248

The idea is to reduce the number of steps required to patch
SCS 3.1 for 
folks not already running that version. Patching for the
SYM06-010 advisory 
is still required but with the slipstreamed installer one
can get both MP1 
and PP1 in two rather than three steps.

This is most appropriate for unmanaged desktops, but if you
or others who
receive this note could give it a trial and let me know if
it works OK or 
not, we can sooner make it available via the Software page
as another 
option for folks.
=======

> What finally worked was:
>
> 1. Uninstall Symantec Client Security, reboot
> 2. Install 310.exe off the network (not running
LiveUpdate), reboot
> 3. Install the first patch (not running LiveUpdate),
reboot
> 4. Install the second patch (not running LiveUpdate),
reboot
> 5. Run LiveUpdate
>
> But now I see that these machines are missing the UCB
custom
> configuration (host exceptions).

That indicates that the installation was incomplete, at
least as far as 
migrating the original settings that came with 3.1 itself.
If everything 
else looks good, you could try using the "Start/All
Programs/Symantec 
Client Security/Restore CB firewall settings"
menu to put the default CB 
Secure settings in place.

--Karl

------------------------------------------------------------
------------
The following was automatically added to this message by the
list server:

For information about Micronet, including subscribing to
or unsubscribing from its mailing list and finding out
about upcoming meetings, please visit the Micronet Web site:
<http://micronet.be
rkeley.edu/>.