-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
The least strict sandboxing for EasyAntiCheat #1515
Comments
@Dyras That one I tried already, but there are options elsewhere that relax sandboxing even more aren't there? For example, EasyAntiChead doesn't want to run even with just this. |
If you don't care about isolation and you want to analyze any compatibility issue, I would suggest to combine the App Compartment mode with the following configuration: #1461 (comment) If it's not enough, you may add also If you need more information about taking the logs, see also the docs here. And last but not least, you could obtain newer debug options quickly by finding the equal sign in the CHANGELOG.md file with your browser in order to highlight them. |
@isaak654 Exactly, I want to debug compatibility, so I basically want to run every protection off. Tested, no change. EasyAntiCheat still complains. What else can be turned off? |
This is basically what is between starting anti cheat and reporting bug:
|
#1192 I have that already.
|
I can definitely wait for a new version of EAC, but this question is more about, how to debug this issue and what is really EAC doing. |
To the NoSecurityIsolation=y what you could also try is to disable various DLL hooks, but disabling many of them can actually worsen the compatibility. DllSkipHook=user32.dll you may also try to open COM access but than a lot of stuff will escape the isolation like the MSI installer and install to the host |
So far, no go. Interestingly:
These to prevents the internal service to run. Otherwise, Steam Client seems to work fine without any other Dll hooks.
Causes steam not to start at all.
Cause steam not work after log in (no main window appears). |
@exander77 Please refer to the main issue if you have further news to share about EasyAntiCheat: #1192 |
This is more of a question. Is there a config available for the least strict sandboxing? Basically, allow everything that is possible?
It would be a great start for debugging issues.
The text was updated successfully, but these errors were encountered: