-
Notifications
You must be signed in to change notification settings - Fork 35
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
Executed PE Files do not return output #1
Comments
Same issue |
I ran into the same issue. The behavior stems from the no-consolation BOF and how it tries to redirect output. I was able to hotfix it and opened a ticket here with the details. |
Holy crap - way to go @parzel! Gonna do some testing real quick and if that looks right then I'll build noconsolation with your hotfix and include it here until there's an official fix release. I was losing my mind trying to run this thing down. |
Great. Let me know if it works, I had no issues so far. Here are the argBytes I am using (changed freeing libraries to z as per CNA and do not allocate console):
|
Confirmed this works - I've pushed the fix. Got delayed because I ran into something stupid where I needed to use go to compress the BOF instead of just running Thanks again @parzel! Going to close this issue for now but if anyone has issues with this please comment on it / open a new issue! |
When we reflectively load another PE file, any hooks we've put in place to capture stdout/stderr go right out the window. The compiled executable will work fine, but if you want to make any decisions based off of the output of invoking the embedded PE file beyond return code this will need another solution.
The text was updated successfully, but these errors were encountered: