-
Notifications
You must be signed in to change notification settings - Fork 170
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
desock: close the pipes after stdin EOF? #15
Comments
Ah, that's very possible... I'm swamped with a big deadline on Friday, but I'll take a look after that! |
Wow, that's a quick reply! Thanks, I'd love to have this bug fixed. |
So after that amazing quick reply, I finally had a chance to look into this I pushed a partial fix that at least stops the stdin synchronization on On Tue, Nov 10, 2015 at 3:54 AM, Jacek Wielemborek <[email protected]
|
I realize this issue is quite old, but is there a reason not to call |
Consider the following
sock.py
Python file:Now run
ncat -l --sh-exec 'echo 1' -k
and then the file above and observe the behavior. Then try:You will see that while without
dsesock.so
the program would exit, turning it on causes an infinite loop. I believe thatrecvrom
should fail if we hit an EOF. Perhaps somehow exiting the loop or closing the pipe in such case could cause that, letting the fuzzed processes avoid an infinite loop?The text was updated successfully, but these errors were encountered: