CLEANACCESS Archives

April 2009

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Dany Rochefort (danyr)" <[log in to unmask]>
Reply To:
Cisco Clean Access Users and Administrators <[log in to unmask]>
Date:
Sun, 5 Apr 2009 22:49:28 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (96 lines)
The AVG Virus Database 270.11.41/2040 should now resolve this issue.

Regards,
-dany

On 4/1/09 4:57 PM, "Rob Crockett" <[log in to unmask]> wrote:

> We to are seeing this issue on a handful of PCs.  Disabling resident
> shield, then adding the exception and then re enabling resident shield
> does work.  Anyone have any inside information as to when AVG will be
> fixing their definition file?  The April 1st virus definition files
> appear to continue to detect Clean Access as a Trojan.
> 
> Thanks,
> 
> Rob Crockett
> Network Administrator
> IT Services
> Ouachita Baptist University
> http://www.obu.edu/ITS
> 
> -----Original Message-----
> From: Cisco Clean Access Users and Administrators
> [mailto:[log in to unmask]] On Behalf Of Straw, Steve
> Sent: Tuesday, March 31, 2009 3:03 PM
> To: [log in to unmask]
> Subject: Re: AVG latest sigs misidentify CCAAgentLauncher executable
> 
> Disable resident shield. Restore the file from the virus vault. Create
> an exception for the file. Re-enable resident shield.  OR This can be
> done with the network edition from the AVG admin server console and
> pushed to any clients configured to use it.
> 
> Steve Straw
> Network Services Manager
> Lynchburg College
> 
> 
> -----Original Message-----
> From: Cisco Clean Access Users and Administrators
> [mailto:[log in to unmask]] On Behalf Of Isabelle Graham
> Sent: Tuesday, March 31, 2009 3:53 PM
> To: [log in to unmask]
> Subject: Re: AVG latest sigs misidentify CCAAgentLauncher executable
> 
> We've seen this here as well. Leaving the file in Virus Vault will
> prevent CCA from starting up
> automatically at boot (CCAAgentLauncher.exe is the file called by the
> link in the Startup folder of
> the Start menu), but does not seem to impact running in manually.
> 
> --
> Isabelle Graham
> Information Security
> American University
> 
> Miller, Paul wrote:
>> Yes, we have the same problem here.
>> 
>> 
>> 
>> Paul Miller
>> 
>> Network Administrator
>> 
>> Dominican University
>> 
>> 
>> 
>> From: Cisco Clean Access Users and Administrators
>> [mailto:[log in to unmask]] On Behalf Of Straw, Steve
>> Sent: Tuesday, March 31, 2009 2:30 PM
>> To: [log in to unmask]
>> Subject: AVG latest sigs misidentify CCAAgentLauncher executable
>> 
>> 
>> 
>> Anybody else seeing AVG v8.x and 7.5 misidentifying the file
>> CCAAgentLauncher.exe as a virus? It looks as though today's signature
>> updates to AVG have the Resident Shield program detecting this exe as
> a
>> threat. Restoring it from the virus vault and making an exception for
>> the file seem to be the work around of the moment.
>> 
>> 
>> 
>> Steve Straw
>> 
>> Network Services Manager
>> 
>> Lynchburg College
>> 
>> 
>> 
>> 

ATOM RSS1 RSS2