You have made me a very happy chappy. This release allows me to have CIS with Pro Avtive on, D+ on safe mode, Firewall on safe, av statefull AND Sandbox enabled and with all these I get 340/340 on the leak test. Thanks for all the huge efforts that everyone has made to make this the best internet security suite available.
Well, at least somebody was able to get the update! Mine says “cmdagent.exe: the file download was aborted abnormally. The file is incomplete.” Oh well! Maybe another case of announcing the update before the servers were ready?
Proactive security, FW=custom policy mode, D+=safe mode,AV-stateful, SB=off gets a score of 340 easily, but i can’t get a decent score with sandbox enabled no matter if virtualization is enabled or not. weird.
NEW! Standalone installers in addition to the web based installer
FIXED! ARP spoofing protection does not protect against certain attacks
FIXED! Automatically sandboxed applications can modify existing protected files under certain conditions
FIXED! Proxy authentication in updater settings does not work
IMPROVED! CIS is now available in 16 languages
Excuse me for for being annoying, but since the old thread was locked
the announcement about 4.0.141842.828 is locked as well
and one of my questions was not answered I may ask again:
Can I assume that the will not be any updates/improvements to the pure Firewall v3.14 any more?
So I can just uncheck auto-update for the firewall on dozens of computers (XP 32bit & Win 7 x64) where just Comodo’s Firewall v3.14.latest is installed & working perfectly now?
I am not going to use v4 with so called Comodo “Sandbox” ever,
so I don’t want to get caught in situation where one of my users will click on update if that may accidentally bring v4 there… God forbid!
Seriously, could you, guys at Comodo, put yellow stickers on your monitors with text ‘I will test GUI apps against 120 DPI display issues’?!
I mean how many times can you make the same mistakes? Practically, every application you develop has some sort of issues with displaying GUI at 120 DPI.
Why those kind of issues aren’t caught with internal testing?