Endpoint Security Extension incorrect behavior after Monterey upgrade

Question

Created Nov ’21

Replies 2

Boosts 0

Participants 2

Hi, I have a ES Sysex working properly in BigSur. I run upgrade to Monterey. I check the behavior of the sysex in Monterey and I notice that is receiving events from processes that I have muted with "es_mute_path_prefix".

It is as if the system upgrade process has affected the Sysex startup and some configurations, forced on start by calling "es_mute_path_prefix" are not taking into account.

Should I take some special steps on SO upgrade scenarios, like reinforcing restart of my sysex ? Stop it before SO upgrade and restart it after upgrade ?

Any known best practices on SO upgrades in general ?

Thanks.

Boost

Answer 1

ZenoElea OP

Nov ’21

I forgot to mention that rebooting after the upgrade, the sysex does behaving as expected by muting the processes set with es_mute_path_prefix. It seems one time issue in the first startup after upgrade.

0

Answer 2

DTS Engineer OP

Apple

Nov ’21

It seems one time issue in the first startup after upgrade.

Well, that’s weird. And it seems eminently bugworthy. I’d appreciate you filing a bug about this, and posting your bug number here, just for the record.

Ideally your bug report would include:

A tiny ES client project that demonstrates the issue.
A sysdiagnose log taken immediately after first seeing the problem with that ES client (that is, once you boot up after the upgrade and confirm that the problem has happened).
A sysdiagnose log taken immediately after clearing the problem (that is, once you restart a second time).

However, I recognise that this is a lot of work. If you don’t have time for the above, you should still file a bug describing how to reproduce the problem with your released software.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0