Grisoft's response to the AVG/Spywareblaster issue

  • Thread starter Thread starter Alan D
  • Start date Start date
ooops- take a look at wilders security and you will see my post
I spoke to avg about this already
robin
 
as stated in wilders security- you have two choices

disable the active x in ie on spyware blaster

or
since it is only in the warnings tab and not in the spyware or infections
tab just ignore and do not do anything.

right now that is what i am doing.

robin
 
You had me confused there for a minute, Robin - it seemed so unlikely that
you could be 'David28' on the Bleeping Computer forum!!
Sounds like AVG's response to everyone is 'Stop using everything except
AVG'. Makes no sense to me.


"Robinb" wrote
 
if you use ie than you need the active x enabled and just ignore the
warnings in avg
if you use firefox you can disable the active x in ie because firefox will
ask you if you want the active x and then it is your decision to install it
or not
Since i use firefox i have active x disabled
the only time i use ie is when i do the security updates and I know that
website is secure

robin
 
"Robinb" wrote in message
if you use ie than you need the active x enabled and just ignore the
warnings in avg
Click to expand...

I'm still biding my time, Robin. I'm not in any hurry to 'upgrade' to a
version that generates hundreds of false positives (because that's what they
are, surely?) due to the presence of a highly trusted and widely used
program on my system. I've written to AVG about this, asking for their
assurance that their program will provide equivalent alternative protection
as the programs (Spywareblaster and Spybot) they're recommending we remove.
They haven't replied yet.
 
i am hoping javacool talks to avg and sort this out
other than this problem the program has become very stable as long as you do
it as a custom install and uncheck the toolbar option.
as said i just ignore these warnings- they are only warnings- it doesn't
mean there are actual trojans

and Alan if you want i will send you the pdf on how to install it and how to
configure and run it if you want
robin
 
and just so you know, Grisoft is working on a fix which is suppose to be out
sometime in May
robin
 
This is good news, isn't it? I'd been following that thread on Wilders too.

I can't think what AVG have been playing at. After all, I was sent an email
only yesterday (the one I showed you)still pushing the old 'incompatibility'
line, even though it seems clear it was a known ewido-based bug all along.
However, thank goodness they've seen sense at last. If this gets fixed in
May, and with the promised service pack coming up too, it's starting to look
much more promising.
 
if you look at the thread i just posted on wilders (and for those who have
not here it is)

Dear Sir/Madam,


thank you for your email.


We are currently working on solution for this. It will be added into
next major program update of AVG.


We are sorry for this inconvenience. Please ignore the warnings in AVG
tests.


It really is not an infection. Please see our pages:
http://www.avg.com/faq?num=1198


Thank you for cooperation.


I also received an email from another tech at Grisoft asking me if i want to
beta test it and I said yes and they said they would send me a link when it
is ready

I will keep you informed once i get a chance to test it
robin
 
Well, it's good to see that it really is 'official' now. Yes please, Robin -
do keep us informed when you get to try it.

It still troubles me that if they knew about this all along, I don't
understand why they persisted with all the other misleading stuff up to now.
 
this one but they are creating a fix for this on their next major update
version
An "ActiveX Compatibility" registry key is a result of the "Immunize"
function included in some anti-spyware programs (e.g.: "Spybot search &
destroy", "Spyware blaster",...)

The key contains the same registry entries as the actual threats, thus
preventing them from working correctly. Some anti-spyware programs use this
method to prevent launching of the malware. Unfortunately, these parts are
still detected by AVG signatures and that is why AVG marks them as infected.

To assure protection provided by AVG against these threats, it is not
possible to remove such signatures from AVG virus bases.
Because of this, "Immunize" function included in above mentioned softwares
is NOT compatible with AVG products.

Sorry it took me so long to answer but i just got back from a cruise
yesterday and was gone for a week

robin
 
Back
Top