Re: Custom UCB Symantec Anti-virus? - the meaning of 'custom'?

I might be biased, since I work just down the hall, but I have never
observed any member of SNS behaving in anything other than a
professional manner.

I, in fact, note a decided lack of fascism in the air (and I lose sleep
nightly over that issue in general).

Having worked with them on several occasions, their objective is to keep
campus functional for everybody on campus, that's plenty to keep them
busy. And sensitivity to the campus need for academic freedom and open
communication has always been there, as far as I can see.

I've always found them to be extremely receptive to collaboration, which
I highly recommend to any unit on campus.

My, well, call it $0.04

-Jay

Bruce C. Beattie wrote:
> I would think that it would be less stressful worrying about whether SNS
> was trying to act as Big Brother, then to worry about finding the time
> to rebuild all the systems that were compromised due to a lack of
> warning from SNS.
> Just my 2¢
> Bruce
>
> Michael Green wrote:
>
>> John D. MacDonald wrote:
>>
>>> I may be alone in this, and I'm sorry if it sounds picky, but it seems
>>> like it would be extremely useful to have the non-"custom" SAV download
>>> available separately from the full 500MB SCS Admin Disc. I know that
>>> for me, having to download the full 500MB disc to extract the XP SAV
>>> client with each version update is tedious. And when configuring
>>> laptops, or other machines that aren't getting a pre-rolled ghost image,
>>> you always want to install and update SAV before connecting it to the
>>> network, so it means a 500MB download via AirBears unless I happen to
>>> have the current SAV on a USB stick with me.
>>>
>>> Of course, if I'm the only one who gets stuck like that, then nevermind.
>>>
>>> John
>>>
>>>
>>>
>> John,
>>
>> I can understand, based on your description above of the effort it takes
>> to get a generic installation done, why you would want to be able to be
>> able to just download just the generic XP SAV directly from
>> software.berkeley.edu.
>>
>> Allison and I were talking about this yesterday. My initial thought was
>> that we should provide both customized and non-customized versions so
>> that folks that don't want to send logs to SNS don't have to go through
>> lots of extra steps. Allison pointed out that maintaining several
>> versions of the installer is fairly difficult. We are not strongly
>> opposed to providing multiple versions of the Symantec client security
>> software, but fewer versions are definitely desirable from a support
>> point of view.
>>
>> I would like to better understand objections to having the Symantec
>> software send logs to SNS. I agree that we should have more clearly
>> communicated that the UCB Custom version of the installer configures the
>> software to send logs to SNS. It was not our intent to obscure what we
>> are doing. We are a security service for the campus. If we are doing
>> something that is not helping, then we should stop doing that thing.
>> From my point of view, which is obviously biased, the logs that we get
>> from the client Symantec installations help us identify systems that are
>> not keeping their Symantec software updated so that we can notify the
>> security contact responsible for that machine that we see something that
>> is of concern. Neither Allison or I can think of any reasonable way
>> that SNS could use the UCB Custom version of the Symantec software to
>> gain access to host machines that have it installed.
>>
>> If we are causing support problems by providing only the UCB Custom
>> version, then it is obviously worthwhile to provide multiple versions of
>> the installer on software.berkeley.edu.
>>
>> Michael Green
>> IST, Infrastructure Applications Manager
>> 642-2039
>>
>>
>> -------------------------------------------------------------------------
>> The following was automatically added to this message by the list server:
>>
>> To learn more about Micronet, including how to subscribe to or unsubscribe from its mailing list and how to find out about upcoming meetings, please visit the Micronet Web site:
>>
>> http://micronet.berkeley.edu
>>
>> Messages you send to this mailing list are public and world-viewable, and the list's archives can be browsed and searched on the Internet. This means these messages can be viewed by (among others) your bosses, prospective employers, and people who have known you in the past.
>>
>
>
> -------------------------------------------------------------------------
> The following was automatically added to this message by the list server:
>
> To learn more about Micronet, including how to subscribe to or unsubscribe from its mailing list and how to find out about upcoming meetings, please visit the Micronet Web site:
>
> http://micronet.berkeley.edu
>
> Messages you send to this mailing list are public and world-viewable, and the list's archives can be browsed and searched on the Internet. This means these messages can be viewed by (among others) your bosses, prospective employers, and people who have known you in the past.
>
>

-- 
Jay Bryon
Senior Network Engineer, U.C. Berkeley/IST/IS/NSO 
jay_at_berkeley.edu
2-5636
"Any idiot can be complex, it takes real genius to be simple"
-Al Einstein
[Unless stated explicitly otherwise, all opinions are my own (or Al's) and do not represent official policy of any part of IST, U.C. Berkeley or the U.C. Regents.]  
 
-------------------------------------------------------------------------
The following was automatically added to this message by the list server:
To learn more about Micronet, including how to subscribe to or unsubscribe from its mailing list and how to find out about upcoming meetings, please visit the Micronet Web site:
http://micronet.berkeley.edu
Messages you send to this mailing list are public and world-viewable, and the list's archives can be browsed and searched on the Internet.  This means these messages can be viewed by (among others) your bosses, prospective employers, and people who have known you in the past.