Honorable Quinn,
I have a problem with macOS 11.0 Big Sur RC2.
I did nothing for the file at the time of opening with EndpointSecurity and allowed all of them.
Of course I refer to the source code of the official EndpointSecurity example.
However, a problem arises in the process of using the file lock.
The file lock is unlocked even when the process is alive.
When I check, the problem is not reproduced unless I receive the ESEVENTTYPEAUTHOPEN callback.
If all events are allowed through the esrespondflagsresult() function in the ESEVENTTYPEAUTH_OPEN callback, the file lock may be released.
This issue has a high reproducibility.
Ask for confirmation and advice.
Thank you.
I have a problem with macOS 11.0 Big Sur RC2.
I did nothing for the file at the time of opening with EndpointSecurity and allowed all of them.
Of course I refer to the source code of the official EndpointSecurity example.
However, a problem arises in the process of using the file lock.
The file lock is unlocked even when the process is alive.
When I check, the problem is not reproduced unless I receive the ESEVENTTYPEAUTHOPEN callback.
If all events are allowed through the esrespondflagsresult() function in the ESEVENTTYPEAUTH_OPEN callback, the file lock may be released.
This issue has a high reproducibility.
Ask for confirmation and advice.
Thank you.
