I have had an open issue on this with Kaspersky for months now. Two
weeks ago I was promised a fix last week. But, I then received an email
from them stating that they haven't yet pinpointed the offending piece
of their application that is causing it. They have a login to my app
and can easily reproduce the problem, and then, when they disable
Kaspersky, they can see that it works. I'll send them another message
and get a status update.
-Jim
Florent Aide wrote:
> On Wed, Nov 12, 2008 at 11:51 PM, Pezzi <[EMAIL PROTECTED]> wrote:
>
>> I wish I had checked back here earlier. The only (of several)
>> turbogears instances it works on is one that serves the pages via an
>> Apache proxy as SSL (and thus Kapersky can't get its fingers on it).
>> Now a pattern emerges ! Any idea what it is that bothers Kapersky ?
>>
>
> Geeee! This sounds like a horrible "security center" that does not
> recognise a proper web server from a nasty virus and tries to act like
> it knows what it does :)
> If you're a current customer of Kaspersky please report the false
> positive to them so they don't hinder other tg users! I stopped being
> a client of theirs a few years back so I can't do it myself.
>
> Florent.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
