Jump to content

Archived

This topic is now archived and is closed to further replies.

karlmikaeloskar

Change in 10.14.5 kernel extension handling

Recommended Posts

Hello @karlmikaeloskar

we are of course preparing to cope with this new macOS requirement.

In the tracking system I already saw that we have an internal build ready to test the notarization.

Regards, Peter

Share this post


Link to post
Share on other sites

I'm wondering whether Apple's new notarization was implemented starting in 10.14.5 Beta 2. Since installing that version of macOS, ESET Cyber Security Pro 6.7.555.0 has been displaying the message that, "System extensions needed by ESET Cyber Security Pro were blocked by macOS" and that I need to allow apps from ESET in System Preferences. However, when I go to System Preferences/Security & Privacy/General, it doesn't display a message asking to allow apps from ESET.

I didn't have this issue with the same version of ESET Cyber Security Pro under 10.14.5 Beta 1.

Additionally, the Console notes the following each time the ESET warning appears: "esets[273]: error[01110000]: ESET Daemon: Command kextload failed. 'com.eset.kext.esets-pfw' error:0x00". Note that the numbers in brackets vary.

Disabling System Integrity Protection allows ESET Cyber Security Pro to run without a problem under 10.14.5 Beta 2; however, disabling SIP isn't a good idea in terms of system security.

If notarization is the cause of the issue, then access to the internal ESET build that Peter Randziak mentions would be helpful.

-- David

Share this post


Link to post
Share on other sites
On 4/10/2019 at 4:48 PM, Peter Randziak said:

we have an internal build ready to test

Any build available to test?
 

Share this post


Link to post
Share on other sites

Detection engine version: 19221P (20190419) fails to make visible an option to Allow apps from ESET, in System Preferences | Security & Privacy | General.

Share this post


Link to post
Share on other sites

As I mentioned above, ESET Cyber Security Pro 6.7.555.0 (under macOS 10.14.5 beta 2) was always asking me to allow its system extensions access (which was impossible to do, because they had already been granted access and thus there was now no option to allow them in the "Security & Privacy/General" pane). The only workaround had been to turn off System Integrity Protection.

I first tried the steps suggested in ESET's Knowledge Base article 6570, but they didn't resolve the issue.

I found that by uninstalling and reinstalling Cyber Security Pro, it no longer repeatedly requests access, and it runs without requiring SIP to be turned off. This is the case whether using the "Regular update" or "Pre-release update" option.

macOS 10.14.5b2 also caused the same issue with another application that I use that utilizes its own system extension; uninstalling and reinstalling that also resolved the issue with that application. So, any users under 10.14.5b2 experiencing a similar problem with ESET or another application may want to try uninstalling and reinstalling to see if that resolves their issue.

-- David

Share this post


Link to post
Share on other sites

I was about to follow not2sure's suggestion to uninstall, then reinstall, when macOS 10.14.5 Public Beta 3 became available. When this was applied, ESET Cyber Security stopped complaining of its kexts being blocked.

 

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...