Glaucus

Hi @Nick M - just talking as just another enterprise user here, but there's no way for ESET or other developers to avoid these prompts asking for Full Disk Access, if this access is needed by the application, due to the new Privacy Preferences Policy Control (PPPC) system that Apple has included in Mojave. The only way for an enterprise to avoid these notifications is using a PPPC configuration profile deployed via an approved MDM solution which whitelists specific permissions for ESET and other applications. Rich Trouton has a good introduction to these new permissions and the requirements around them here: https://derflounder.wordpress.com/2018/08/31/creating-privacy-preferences-policy-control-profiles-for-macos/ What version 6.7.600.0 of ESET Endpoint Antivirus resolves is the application honoring these PPPC config profiles when present on the system. Version 6.7. 500.0 prompted for Full Disk Access, even when the appropriate permission was granted by one of these profiles. This newer version, at least in our environment using JAMF Pro as our MDM, now launches correctly without the prompt for Full Disk Access.

We've recently deployed Endpoint Antivirus for Mac, version 6.7.500.0, to hundreds of endpoints via JAMF Pro, using the default real-time protection settings. Now, we have a number of users reporting issues with web browsing, immediately after the installation. For example, a user could not open cnn.com or speedtest.net in a browser, among many other websites. A Google search would load and show search results, but not every link would work. On this specific system, ESET was installed at approximately 9:02 AM, local time, and then errors begin appearing in the ESET Events Log less than 30 minutes later: 10:15:26 AM Protoscan Proxy Agent Cannot accept connection: Too many open files root 10:15:26 AM Protoscan Proxy Agent Cannot accept connection: Too many open files root 10:15:26 AM Protoscan Proxy Agent Cannot accept connection: Too many open files root 10:15:26 AM Protoscan Proxy Agent Cannot accept connection: Too many open files root 9:29:41 AM ESET Daemon Child process proxy[2085] did not handle signal 11, restart in 0 seconds root The "Proxy Agent Cannot accept connection: Too many open files" error then repeats more than once a second afterward. Disabling real-time protection appeared to fix the issue, but we obviously do not want to disable real-time protection on our endpoints. Has anyone else observed this behavior, or have advice for troubleshooting this?

Hello @TomasP and @Peter Randziak - we, too, are running into the same issue with ESET's interaction with the TCC profiles at our institution. Would you be able to forward the beta client to me, as well? Thanks.