Alikhan

Will there be more features added to v8 or just the 2 mentioned above? I'm sure they'll be improvements.

Great. Downloading now.

I can confirm that I installed the Windows Update stated above and with SSL enabled, Windows would be unable to check for updates. Disabling SSL fixes the issue.

Installed over the top of 7.0.302.26 and have no problems. Was a good smooth upgrade. Nice to see after re-enabling protection, the anti-phishing protection now has the green symbol rather than the red.

When will this module be moved to the Regular updates?

On another note, soon (I don't know when) that module will go to the regular update so you can switch back.

If you go to Advanced Setup > Update It will be stated there but it's very rare that they'll cause any problems.

Fixed already... you need to enable pre-release updates. Read this: https://forum.eset.com/topic/1949-solved-via-pre-release-updates-https-sites-when-ssl-enabled/

I can confirm that this has fixed the issue on Chrome.

Yes, disabling SSL scanning enables me to to go to "https" sites via Chrome. I manually exported the certificate from Eset too into a new re-installed Chrome with no extensions and it still does not work.

The issue started occurring yesterday, before that it had been fine for a few months. I don't think there's been a new version of Chrome out since then and not to forget that annoying Google Updater which will do anything to get it updated to the latest version in the background.

I use it for speed and personal preference. Back to the topic, after resetting IE11 SSL seems to be working fine except on the ESET forum where it gives me an "untrusted" certificate error. I've reset Chrome, uninstall and reinstalled it and even manually imported the certificate and it is still not working.

When I go to google or this site it says with SSL enabled via IE11.. "You are about to view pages over a secure connection. Any information you exchange with this site cannot be viewed by anyone else on the web. It then gives me the option to click ok and load the page... BUT I need to click okay for every SSL page via IE11 and on Chrome (main browser) the site doesn't load at all.

I exported the certificate from SSL > View Certificate > Details > Copy to file (it couldn't transfer the private key) I then imported the certificate into Chrome and it did not work. Is this the way it should be done or have I done it wrong? I closed all browsers and email clients after enabling/re-enabling.

Yes. For example, I can't even visit this forum with SSL enabled or search via the URL bar via Google Chrome.

Recently, I realized that I could not reach any sites with https. I thought it was a random problem and then started to narrow it down. Once I removed Eset, I could visit the site. I then done a clean install using the Eset removal tool and re-installing. Since then, whenever I enable SSL scanning, I can not visit any sites with the https. Any ideas how to fix it? I've already tried disabling and re-enabling it with all browsers and email clients closed.

+1.

I have SSL enabled and am using Google chrome and don't have the issue. I've never seen lsass.exe exceed 25mb for me. hxxp://oi41.tinypic.com/j6ne4o.jpg Can't use here...

There are hundreds of thousands of legitimate applications that are new to LiveGrid so your suggestion would produce a lot of warning to users who wouldn't know whether to allow the application to run or not. Well, what I meant is when a file is downloaded. I know they could be some legitimate files but if you narrow it down to factors such as: - File has a digital signature - The source of the file - How long the file has been created - Amount of users with the file - Where the file has been downloaded from And some other factors it would narrow it down. Most major AVs use the cloud to their advantage so this was just like an idea.

Description: Warn users when opening an unknown file to Eset (using live grid features) Detail: I think users should be warned when an unknown file is being ran since it could be malicious.

Ah, that makes sense. However, wouldn't it better to atleast let the user know if the memory scanner is doing something? Something like a normal detection popup in the corner?

When threats are detected by the memory scanner etc, does it let the user know or just keeps it to itself in the background?

It would be nice to hear something from Eset themselves. Having seen several reviews and videos (I know they don't serve a real life purpose) once something passes the web shield which is amazing, nothing else does anything. I've never seen the exploit blocker or the vulnerability shield do anything... are they enabled by default or reliant on HIPS. It's either that or the exploit blocker and vulnerability shields are doing the work in the "background" without notifying the user which doesn't seem obvious.

Hi all, I'm currently using ESS (trial) version and am considering purchasing. My only question is what zero day protection does Eset have enabled by default. I know the HIPS is there and all that but the rules have to be set up etc. So if I don't choose that option, is it safe to assume that everything which is not detected by the signatures and web shield will be let through? In the next major release... will there be improvements on zero day protection?