by adrien » Mar 01 10 10:09 pm
Hi
We are aware of increasing issues with the existing KAV for WinGate product, notably increased memory consumption, and more frequent issues downloading updates and scanning files. The scanning engine that we are using is now quite old and no longer supported by Kaspersky Labs, although they will continue to release signature updates for it for a while yet. We have been working with them for quite some time now on a new scanning engine. The new scanning engine works quite differently to the old one, and so it's not a straight-forward matter to port their new engine to our existing KAV for WinGate product. Complicating this issue has been WinGate 7. We have a KAV working for HTTP and SMTP in WinGate 7 based on the new Kaspersky Labs engine, using completely new filtering interfaces for these protocols in WinGate 7.
Our development energies have been focused on getting WinGate 7 out the door, which is long overdue, so we haven't been keen to divert attention from that in order to re-write an old plugin that will soon be redundant, and have been hoping that the issues facing customers have not been too grave.
I realise this is of no help to people running WinGate 6, so I'm wondering what I can offer. There are a couple of options.
1. WinGate 7. This could be an option, depending on what you are using WinGate for. We're running it on our gateway here for SMTP, VPN, HTTP etc. You could then use KAV for WinGate 7 free until the product is released. However it currently only scans SMTP and HTTP, so if you were doing POP3 collection, FTP or POP3 via proxy, and relying on that being scanned, this may not be an option for you.
2. We re-write KAV for WinGate 6. I had been hoping to avoid this, but it depends on how much of a problem it is for how many customers.
Regards
Adrien de Croy