-
Notifications
You must be signed in to change notification settings - Fork 167
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
dRonine flags #2219
Comments
I wonder if the RunGuard stuff and its shared memory antics is tripping AV scanners. |
The other thing I think it could be is the breakpad handler hooking all the signals. |
Interesting chrome comments on that: https://codereview.chromium.org/1416133003/patch/1160001/1170033 -e- They embed the handler app in chrome.exe and the decision to run it, or the normal chrome exe comes from argv https://codereview.chromium.org/1416133003/patch/1160001/1170017 |
Hmmm that'd be annoying. It's the drgcs.exe resulting that trips everything. I'm gonna look into it tomorrow, uploading a stock build to VirusTotal.com and see if it does the same (or whether I need a Jenkins build), and then replace the sharedmem stuff with a global mutex as barrier on Windows and see if it still happens. Should exclude that possibility. |
Must be some weird ass codegen stuff. A debug build of drgcs.exe of next triggers only one AV out of 67 over on VirusTotal.com, called Cylance, which is supposed to be some AI shit. A release build triggers 15 of them, which is an improvement over Wired, which triggers a whopping 35. Replacing the shared mem stuff with a global mutex still triggers 15 of them. |
Ain't the crash reporting nor the Runguard stuff in general. Excluding them still triggers stuff. Dafuq? |
Maybe they really are just trolling us. |
gonna call this duplicate of #2221 |
Everytime i attempt to download or install dRonin it flags with Google (Chrome), Malwarebytes and Avast. I've attempted several times to contact the vendors to submit an exception but after several months still no luck. Would it be possible to contact the vendors on your end to see if they'll hear your voice?
For the meantime, I've added exclusions for both Malwarebytes and Avast.
The text was updated successfully, but these errors were encountered: