Skip to content
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

[notissue] Return back a ripped functionality #9

Closed
VitRom opened this issue Apr 13, 2020 · 4 comments
Closed

[notissue] Return back a ripped functionality #9

VitRom opened this issue Apr 13, 2020 · 4 comments
Labels
ToDo To be done

Comments

@VitRom
Copy link

VitRom commented Apr 13, 2020

Hope this will go into a Project' Task.

At the 3.x epoch there was a very useful functions used to inject dlls like AntiDel and some runtime monitoring. And BSA addon based on these features. Unfortunately these functions were trashed out and we're definitely need them back.

@DavidXanatos
Copy link
Member

That should be doable relatively easy and sounds indeed useful.

@DavidXanatos DavidXanatos added the ToDo To be done label Apr 14, 2020
@DavidBerdik
Copy link

I realize that this does not contribute anything to the progression of the issue, so I apologize in advance, but I'm curious: if this should be easily doable @DavidXanatos, do you have any idea why the development team would have removed it?

@DavidXanatos
Copy link
Member

DavidXanatos commented Jun 2, 2020

BSA is Workign again: https://www.wilderssecurity.com/threads/buster-sandbox-analyzer.428538/page-2#post-2920470

@DavidBerdik
As far as I can tell they did not exactly removed anything just changed something with the hooking mechanism that broke a lot of 3rd party injection dll's.

I can't tell you how they broke it as the old sources are not public, it does not make sense to me to change something from working to broken on purpose, perhaps it was a total rework to Fix some other issue they head and the new code worked for Sandboxie itself, but no longer for other cases.

When fixing LOG_API.dll, aside the SetTimer issue, I ran into CreateProcessW resulting in a crash further down in windows and SetSecurityInfo which just maneuvered itself into an endless loop of calling itself. At that point I decided screw it, and just grabbed a well tested hooking library that does the job properly. Why CreateProcessW failed I have no idea, sbie is not even hooking it, just some internal function that is down the line invoked by it, SetSecurityInfo is a different story Sbie hooks it and without digging into what exactly went wrong there I'd just speculate that the new hooking mechanism from Sbie doesn't properly handle when a function is hooked twice, something along the lines of overwriting the trampoline to the original function with one to the other hooking function....

Now I wonder if its a good idea to use that hooking lib also for sandboxie, might be worth testing that out.

Anyhow since the BSA issue is now fixed I'll close it.

@DavidBerdik
Copy link

@DavidXanatos Interesting! Thank you for the detailed explanation!

DavidXanatos pushed a commit that referenced this issue Jan 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ToDo To be done
Projects
None yet
Development

No branches or pull requests

3 participants