-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable ProcessStrictHandleCheckPolicy on Windows #3
Comments
What does this do exactly? Microsoft's documentation doesn't specify what 'manipulating a handle that is not valid' entails. Does that mean that calling, say, |
Yes, this is the general idea. In the context of a multithreaded DAW with plugins, I think it is important to ensure that plugins do not have bugs of this form, since misuse of a handle by a plugin could affect the host itself as well as other plugins, resulting in e.g. file data corruption.
I believe Windows enables it by default for all UWP applications. |
On Windows,
ProcessStrictHandleCheckPolicy
can be enabled withSetProcessMitigationPolicy
to check that the plugin does not misuseHANDLE
s in the Win32 API. This is not specific to CLAP, but I think it is a nice-to-have in a plugin validator nonetheless.The text was updated successfully, but these errors were encountered: