erratic

I upgraded from El Capitan to Catalina in the meantime, and everything went well. No issues with ESET.

Problem got resolved in 6.10

I got the reply from ESET support that no incompatibility or any other issue has been reported so far. I installed Little Snitch 4.6 on Catalina in the meantime, together with ESET Cyber Security Pro 6.10.460.1. Runs smoothly. Little Snitch triggers just before ESET, which is great because it gives me complementary information I can use in my decisions (I use ESET firewall in interactive mode) Sure, from resources point of view it may seem overkill. And Little Snitch takes up more RAM than ESET, but I find it worth it.

Nobody knows? Or is my question unclear?

Let's say I am connected to my WiFi, and using the "Home" profile, which has a set of rules I have defined based on the interactive firewall. Sometimes I lose my WiFi signal, and ESET will switch to the Public profile, and I will suddenly get a bunch of interactive messages asking me what to do about the new traffic it detects, because of the Public profile which does not have the same rules as Home - on purpose. Even when I'm back on the WiFi and in the Home profile, ESET will continue to propose me the interactive requests about what to do with the traffic in the Public profile - from when I had lost the signal I wish there were a way to either cancel all these in one shot, or anything that would keep me from having to acknowledge or decline all these the dialog boxes. I hope my question is clear. How can I deal with this?

Well, I'll try myself and see how it goes.

Nobody ?

Hello, I would like to investigate the use of Little Snitch, but before doing so I am interesting in learning about possible counter indications. Anyone who can comment on this? Has someone used both together successfully? Is there a good reason not to do it? Will it cause problems with ESET? Thanks

I can confirm something is wrong in 6.9.200. I went back to 6.8.455, my previous version and I got the desired funtionality back regarding Apple signed processes popping up in Interactive mode, something that doesn't work in 6.9.200. Also, when I disable Network Traffic Filtering in 6.8.455, ESET does signal it in the dashboard (see attachment). Also, I see lots of "No usable rule found" in the logs.

Also, I have reset the Zone which had all the rules and started from scratch with the default - in case something was wrong in the rule set. No change.

I was running Cyber Security Pro 6.8 and upgraded to 6.9 (.200). I am on Catalina 10.15.7. I had the Firewall in Interactive mode, and unchecked "Allow software signed by Apple to access the network automatically". This worked well before the upgrade to 6.9; ESET Cyber Secuity Pro told me about all Apple processes trying to go out, such as ocspd, locationd, etc. Since 6.9 I find the firewall very quiet on the Apple front. It still tells me when non-Apple processes try to engage in communication, but nothing for Apple processes - which I find odd. I have the impression something is off with the firewall. Also, and I don't know if that's normal, when I disable "Network Traffic Filtering", the interface does not show a red trianble in the upper right corner, like it does when you disable Real-Time File System Protection. Unless I'm mistaken I thought that normally for disabling Network Traffic filtering would be displayed by ESET as a red issue. In the attached snapshot you can see that Network Traffic Filtering is disabled, yet the Firewall icon shows nothing is wrong, and behind the dropdown menu you an see it is showing "Maximum protection". What could be wrong? Anything I can check?

Last version of ESET Cyber Security 6.9.200 https://download.eset.com/com/eset/apps/home/ess/mac/v6/6.9.200.0/eset_cybersecurity_pro_en.dmg

Thank you Marcos. I'll keep that in mind. Can you please point out where I can download the last 6.9 version of Cyber SecurityPro ? (I believe 6.9.60)

But what about question 1) ? Will ESET 6.8 work after upgrading to Catalina? Also, is there any documentation about the functional differences between 6.9 and 6.10 ? Or is 6.10 only adding Big Sur compatibility?

Hello, I am currently running El Capitan (10.11.6) on my Mac (for reasons), with ESET Cybersecurity Pro 6.8.455. I am perfectly happy with it. I am planning on upgrading to Catalina (10.15.7), and I am wondering 2 things: 1) According to the documentation I can find, ESET should still work after upgrading to Catalina, since I have ESET 6.8. -- Correct? 2) Once on Catalina I would like to upgrade ESET Cybersecurity Pro, but I am wondering if there could be a reason to upgrade to the last 6.9 version instead of 6.10? Is 6.10 built for Big Sur? If I don't want Big Sur (for the time being), is it not better for me to be on 6.9 ? Thanks for your input

A month after installing 6.8.455, and the issue mentioned above still has not manifest itself. Seems to have solved the problem for me.

Hello, I am (was) running Cyber Security Pro 6.8.300 on El Capitan 10.11.6 (by choice), and looks like I'm kind of stuck with it since 6.9.x no longer supports El Capitan. I was having the same issues with esets_proxy, sometimes spiking to above 100%, sometimes 200%, even 300%. The fan kept blowing. At first I thought it was my own fault because I use Chrome with way too many tabs, but that's how it is. But when i'd kill Chrome and any other open app, the fan would quiet down... but esets_proxy would remain fixed at a high number. The impression it gave me was that there was something wrong with the high CPU utilization %. I don't believe the high spikes, I think there is something wrong with these figures, as if they would just accumulate on and on. The only way to get it back to normal was to kill esets_proxy. I have now installed version 6.8.455 mentioned by Marcos higher up. Looking forward to see if the situation improves. Been a day now, and all is still running fine.

Update: SOLVED I just upgraded to the latest version, 6.4.168.0, and I can now confirm my problem is gone.

Hello, I am running ESET Endpoint Antivirus 6.3.85 on OSX 10.11.6 I don't know exactly when it started, but I'm guessing around May 2016, and it persisted across various ESET upgrades prior to 6.3 and OSX upgrades (10.11.4 and 10.11.5). For me, all of a sudden podcasts in iTunes started failing to download. I first tried everything, OS upgrades, iTunes re-installs etc etc, but finally narrowed the problem down to ESET's Web Access Protection. When I disable it, everything works fine. Another, more refined workaround is not to disable it but just to disable "HTTP protocol checking". I am not satisfied with either because I would have to disable protection against all websites, just because of an issue with one. I am also not paying for software that I have to disable.. So I started Wiresharking to see what HTTP flows ESET would break. Turns out there is an issue when a podcast URL redirects (302) to another domain. I'll take an example. A dysfunctional URL in iTunes is the podcast hxxp://rf.proxycast.org/1181578500855832576/14489-02.07.2016-ITEMA_21024836-0.mp3 (1) That URL redirects to hxxp://media.radiofrance-podcast.net/podcast09/14489-02.07.2016-ITEMA_21024836-0.mp3 (2) where the DNS name is a CNAME for a Cloudfront IP. With ESET HTTP Protocol Checking ON: URL (1) actually breaks anywhere; iTunes, Safari, Chrome, Firefox. URL (2) works fine anywhere. I tried excluding the domain *proxycast.org* from the URL scanning list, but that does not solve the problem completely. iTunes still fails to handle correctly the redirect it seems, as does Safari. Chrome and Firefox do play the URL. Right now the only, temporarily acceptable workaround I can find is to go in the General Protection and exclude the IP address of (1) from Web and Email scanning. This will only work of course until that IP changes. I would have preferred that the exclusion of the URL from scanning would have been the most acceptable workaround, but it does not work. Of course, the most preferred solution would be that ESET does not break the HTTP flow with its HTTP protocol checking. I don't know if ESET has already identified this issue? PS: I don't have this issue with those podcasts on other machines, Mac and PC, that do not run ESET.