Nate Simpson

Anyone know how to stop the patch management and vuln mgmt from flagging as a red alert when it's not on if we aren't using it anyway?

Joining this post. 
version 11.0.15.0 - on Ubuntu 24.04 it works on some linux machine and on others the realtime protection is non-functional, pointing to missing rto files and such. (according to lslog) 
Also worth pointing out. 
the automated tasks to reinstall EEA to the version specified doesn't work and will always install the latest 11.0.15.0 no matter what version I chose. 
No idea why that happens either, I had to manually download and install eea while stopping the agent service temporarily

How do I get Eset to stop flagging our PCs with a red alert because we aren't using this feature? I need these red alert statuses to be because of something serious. Not a feature I'm not using that isn't turned on.

Wait, so is it in 'upcoming weeks' or 'probably 24Q3'? 🤔 
If the latter, that's shockingly slow! Do ESET devs just start to work on this when the Ubuntu LTS version is released?

I see that almost a month ago you @Marcos said that ESET for Ubuntu 24.04 was coming soon: 
As we are trying to plan our company-wide upgrades to Ubuntu 24.04, do you have any update on the ETA for the new ESET version?

It's not a matter of distro, it's a matter of kernel. You can use the current Ubuntu or, for that matter, any other recently updated distro like Fedora, CentOS Stream etc, as long as you stick with kernel 6.3.13. Any kernel newer than that won't work. For instance, I'm on Fedora 39, but I version locked the kernel to 6.3.13 and ESET Endpoint runs fine. I also recommend sticking with version 9.x of the antivirus given that version 10 introduces web protection which is completely broken and would block all your internet traffic, as already reported by multiple people on this forum.

Description: use DKMS (Dynamic Kernel Module Support) for Eset Kernel Modules on Linux
Detail: The forum is full of problem reports due to signing of eset kernel modules on Linux with activated secure boot. The standard solution for the problem is the DKMS framework, which takes care of automatic module signing on kernel update or eset update. Please drop the custom made signing script in favor of a DKMS based solution. It makes the whole update and signing process soooo much more reliable and predictable - which is why NVIDIA, VMware and most other Vendors use it to ship their kernel modules.
We even had to hire a software developer, just to automate the eset signing for our fleet of Linux devices 🤦‍♂️. But it is still unreliable and we have to work around all the race conditions that would not even exist with DKMS.

As I understand from one of my colleagues this is because it is locked to an extended hardware support module 
"linux-headers-generic-hwe-22.04 " is required which is an LTS specific package not needed in the rolling releases. Enabling support/use of "linux-headers-generic" would seem to at least partly resolve the issue - even if this was only available as an alpha/unsupported config

As I understand from one of my colleagues this is because it is locked to an extended hardware support module 
"linux-headers-generic-hwe-22.04 " is required which is an LTS specific package not needed in the rolling releases. Enabling support/use of "linux-headers-generic" would seem to at least partly resolve the issue - even if this was only available as an alpha/unsupported config

Hi,
is there already a plan to support current versions of Ubuntu? Currently ESET Endpoint Antivirus for Linux does not work for Ubuntu 23.04.