Description

We've been running into problem with our "crashpad" backend under epic's easy anti-cheat client protection software.
The solution places some restrictions on the running process, causing the windows version of crashpad to fail
to initialize.

We have consulted with Epic, and they provided us with a diff to "crashpad" which has been employed by other
users. It basically limits the permission of created processes and promotes a process when necessary.

We would have added this directly to our own fork of sentry-native, or provided a PR, but I noticed that "crashpad" is a submodule maintained by you.

Would you be interested in a PR to "getsentry/crashpad" ?

When does the problem happen

• During build
• During run-time
• When capturing a hard crash

Environment

• OS: Windows

Steps To Reproduce

Run an executable under the "Easy Anti Cheat" supervisor, notice how sentry reports that it "failed to launch crashpad handler."