-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
Fix #14510, fix reverse_awk and bind_awk exit behavior #14515
Conversation
Works as described on Kali without reintroducing the issues described in #9750. (Edit: I only tested bind, not reverse) The payload fails to run on Ubuntu 20.04:
However it didn't work prior to this change either, presumably due to shipping
Ubuntu 20.04:
Kali:
|
That makes sense. The TCP stack is a GNU extension. I wonder how much portability we would lose by changing the invocation to |
Thanks @timwr for fixing this! Everything looks good to me. Example output
|
Release NotesFixed an issue with both |
This fixes #14510
Thanks for reporting @egypt !
Verification
use payload/cmd/unix/reverse_awk
generate -f raw
to_handler
sessions -1
id
or something to make sure it's realexit
or ctrl-cExpected behavior
clean exit
Current behavior
If you
exit
, the payload continues to call back. If you ctrl-c, it doesn't call back anymore but the process is still there.